asn.dev

Observed topology

AS397700 LXXIX-PROJECT-LAB-01

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS397700: 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 IPv6183
AS3356Level 3 Parent, LLCTransitIPv4 IPv669
AS27552TowardEX Technologies International, Inc.UnclassifiedIPv4 IPv653
AS6939Hurricane Electric LLCTransitIPv4 IPv631
AS395748NetSpeed LLCUnclassifiedIPv424
AS174Cogent Communications, LLCTransitIPv4 IPv620
AS293ESnetUnclassifiedIPv43

Transit

Downstream networks

inferred

Networks for which AS397700 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6183
AS3356Level 3 Parent, LLCTransitIPv4 IPv669
AS27552TowardEX Technologies International, Inc.UnclassifiedIPv4 IPv653
AS6939Hurricane Electric LLCTransitIPv4 IPv631
AS395748NetSpeed LLCUnclassifiedIPv424
AS174Cogent Communications, LLCTransitIPv4 IPv620
AS293ESnetUnclassifiedIPv43

Provenance

Where this comes from

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