asn.dev

Observed topology

AS306 DNIC-ASBLK-00306-00371

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS306: 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
AS1540Headquarters, USAISCUnclassifiedIPv4 IPv618,003
AS367United States Department of Defense (DoD)UnclassifiedIPv4 IPv6282
AS27066United States Department of Defense (DoD)UnclassifiedIPv460

Transit

Downstream networks

All 55

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

ASNetworkTypeFamiliesPaths seen
AS335United States Department of Defense (DoD)UnclassifiedIPv4 IPv613,891
AS344United States Department of Defense (DoD)UnclassifiedIPv4 IPv610,701
AS370United States Department of Defense (DoD)UnclassifiedIPv4 IPv68,247
AS325United States Department of Defense (DoD)UnclassifiedIPv4 IPv66,966
AS337United States Department of Defense (DoD)UnclassifiedIPv4 IPv63,750
AS362United States Department of Defense (DoD)UnclassifiedIPv4 IPv63,572
AS334United States Department of Defense (DoD)UnclassifiedIPv4 IPv62,793
AS356United States Department of Defense (DoD)UnclassifiedIPv42,564
AS348United States Department of Defense (DoD)UnclassifiedIPv4 IPv62,254
AS369United States Department of Defense (DoD)UnclassifiedIPv4 IPv62,217

All 55 downstreams →

Adjacency

Adjacent networks

All 58

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

ASNetworkTypeFamiliesPaths seen
AS1540Headquarters, USAISCUnclassifiedIPv4 IPv698,511
AS335United States Department of Defense (DoD)UnclassifiedIPv4 IPv613,891
AS344United States Department of Defense (DoD)UnclassifiedIPv4 IPv610,701
AS370United States Department of Defense (DoD)UnclassifiedIPv4 IPv68,247
AS325United States Department of Defense (DoD)UnclassifiedIPv4 IPv66,966
AS348United States Department of Defense (DoD)UnclassifiedIPv4 IPv65,615
AS337United States Department of Defense (DoD)UnclassifiedIPv4 IPv63,750
AS362United States Department of Defense (DoD)UnclassifiedIPv4 IPv63,572
AS334United States Department of Defense (DoD)UnclassifiedIPv4 IPv62,793
AS356United States Department of Defense (DoD)UnclassifiedIPv42,564

All 58 adjacent →

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.