asn.dev

Observed topology

AS62597 NSONE

Unclassified ARIN

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

Transit

Upstream networks

All 32

Networks observed carrying traffic for AS62597: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6929
AS3356Level 3 Parent, LLCTransitIPv4 IPv6575
AS2914NTT America, Inc.TransitIPv4 IPv6427
AS174Cogent Communications, LLCTransitIPv4 IPv6279
AS6939Hurricane Electric LLCTransitIPv4 IPv6241
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv696
AS36236NetActuate, IncHostingIPv4 IPv672
AS37100SEACOM LimitedUnclassifiedIPv4 IPv643
AS1221Telstra LimitedMobileIPv4 IPv638
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv638

All 32 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 32

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6929
AS3356Level 3 Parent, LLCTransitIPv4 IPv6575
AS2914NTT America, Inc.TransitIPv4 IPv6427
AS174Cogent Communications, LLCTransitIPv4 IPv6279
AS6939Hurricane Electric LLCTransitIPv4 IPv6241
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv696
AS36236NetActuate, IncHostingIPv4 IPv672
AS37100SEACOM LimitedUnclassifiedIPv4 IPv643
AS1221Telstra LimitedMobileIPv4 IPv638
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv638

All 32 adjacent →

Provenance

Where this comes from

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