asn.dev

Observed topology

AS397315 REGION10-LEAP

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS397315: 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
AS6461Zayo BandwidthTransitIPv4158
AS14041University Corporation for Atmospheric ResearchEducationIPv425

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS54081City of Grand JunctionUnclassifiedIPv4342
AS30436Elite Broadband LLCUnclassifiedIPv4293
AS393657Colorado Mesa UniversityUnclassifiedIPv475
AS17015Western Colorado UniversityUnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4886
AS54081City of Grand JunctionUnclassifiedIPv4342
AS30436Elite Broadband LLCUnclassifiedIPv4293
AS393657Colorado Mesa UniversityUnclassifiedIPv475
AS14041University Corporation for Atmospheric ResearchEducationIPv470
AS17015Western Colorado UniversityUnclassifiedIPv463

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.