asn.dev

Observed topology

AS30600 AS-CMN - Metronet

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30600: 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 IPv67,000
AS2914NTT America, Inc.TransitIPv4 IPv62,810
AS174Cogent Communications, LLCTransitIPv4 IPv62,196

Transit

Downstream networks

All 61

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

ASNetworkTypeFamiliesPaths seen
AS15011Jaguar CommunicationsUnclassifiedIPv43,021
AS21918MetronetUnclassifiedIPv41,564
AS63242MetronetUnclassifiedIPv4969
AS16410The Reynolds and Reynolds CompanyHostingIPv4773
AS3801Mikrotec Internet ServicesHostingIPv4 IPv6655
AS393737CpuonsiteUnclassifiedIPv4 IPv6379
AS10846Deere & CompanyUnclassifiedIPv4 IPv6206
AS33507Vexus FiberUnclassifiedIPv4174
AS63001Vexus FiberUnclassifiedIPv4174
AS35924Vexus FiberUnclassifiedIPv4171

Adjacency

Adjacent networks

All 64

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv612,337
AS2914NTT America, Inc.TransitIPv4 IPv66,203
AS174Cogent Communications, LLCTransitIPv4 IPv64,855
AS15011Jaguar CommunicationsUnclassifiedIPv43,422
AS21918MetronetUnclassifiedIPv41,564
AS63242MetronetUnclassifiedIPv41,042
AS16410The Reynolds and Reynolds CompanyHostingIPv4773
AS3801Mikrotec Internet ServicesHostingIPv4 IPv6750
AS393737CpuonsiteUnclassifiedIPv4 IPv6379
AS10846Deere & CompanyUnclassifiedIPv4 IPv6206

Provenance

Where this comes from

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