Observed topology

AS150363 THIN-NET SoftEther Corporation

Residential RIPE

Upstreams 6 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 6

Upstream graph Who carries AS150363, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS150363 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS150363: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

AS	Network	Type	Families	Paths seen
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4	108
AS7530	BroadBand Tower, Inc.	Hosting	IPv4	33
AS6939	Hurricane Electric LLC	Transit	IPv4	25
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	3
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	3
AS24482	SG.GS	Hosting	IPv4	3

Transit

Downstream networks

inferred

Networks for which AS150363 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS38074	SDCC Japan-West Area	Unclassified	IPv4 IPv6	215
AS63802	Nippon Telegraph and Telephone East Corporation	Unclassified	IPv4	141

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS150363 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS38074	SDCC Japan-West Area	Unclassified	IPv4 IPv6	1,328
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	1,020
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4 IPv6	497
AS63802	Nippon Telegraph and Telephone East Corporation	Unclassified	IPv4	141
AS7530	BroadBand Tower, Inc.	Hosting	IPv4	44
AS24482	SG.GS	Hosting	IPv4 IPv6	36
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4 IPv6	33
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	11
AS9002	RETN Limited	Unclassified	IPv6	3

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.