asn.dev

Observed topology

AS7201 AS-NETWORKEDGE

Unclassified ARIN NSP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS7201: 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
AS174Cogent Communications, LLCTransitIPv4294
AS6939Hurricane Electric LLCTransitIPv4 IPv681
AS9002RETN LimitedUnclassifiedIPv410
AS293ESnetUnclassifiedIPv47
AS3130RGnet OUUnclassifiedIPv47
AS7575Australian Academic and Research Network (AARNet)EducationIPv47
AS24482SG.GSHostingIPv47
AS52025ParadoxNetworks LimitedUnclassifiedIPv47
AS394256Tech Futures Interactive Inc.UnclassifiedIPv47
AS20205Amplex Electric, Inc.ResidentialIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS13737Interconnecx, LLCUnclassifiedIPv4773
AS401130SaturnDotDevUnclassifiedIPv451

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv41,012
AS13737Interconnecx, LLCUnclassifiedIPv4847
AS6939Hurricane Electric LLCTransitIPv4 IPv685
AS9002RETN LimitedUnclassifiedIPv457
AS401130SaturnDotDevUnclassifiedIPv451
AS3130RGnet OUUnclassifiedIPv448
AS7575Australian Academic and Research Network (AARNet)EducationIPv448
AS24482SG.GSHostingIPv448
AS293ESnetUnclassifiedIPv48
AS394256Tech Futures Interactive Inc.UnclassifiedIPv48

Provenance

Where this comes from

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