asn.dev

Observed topology

AS211392 SOFTBANK

Hosting RIPE NSP

Upstreams 4 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 0
Upstream graph Who carries AS211392, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS211392 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211392: 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.

ASNetworkTypeFamiliesPaths seen
AS23764CTGNetUnclassifiedIPv4311
AS58453China Mobile International LimitedUnclassifiedIPv4123
AS139076EnjoyVC Japan CorporationUnclassifiedIPv4118
AS135074DREAM CLOUD INNOVATION PTE. LTD.UnclassifiedIPv415

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS401160World W3B LLCUnclassifiedIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23764CTGNetUnclassifiedIPv4311
AS58453China Mobile International LimitedUnclassifiedIPv4123
AS139076EnjoyVC Japan CorporationUnclassifiedIPv4118
AS135074DREAM CLOUD INNOVATION PTE. LTD.UnclassifiedIPv415
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv413
AS401160World W3B LLCUnclassifiedIPv413

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.