asn.dev

Observed topology

AS27065 DNIC-ASBLK-27032-27159

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27065: 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
AS721United States Department of Defense (DoD)UnclassifiedIPv4 IPv64,233

Transit

Downstream networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS1540Headquarters, USAISCUnclassifiedIPv4 IPv628,835
AS5972United States Department of Defense (DoD)UnclassifiedIPv44,726
AS367United States Department of Defense (DoD)UnclassifiedIPv4 IPv64,034
AS5839United States Department of Defense (DoD)UnclassifiedIPv43,926
AS637United States Department of Defense (DoD)UnclassifiedIPv42,153
AS56United States Department of Defense (DoD)UnclassifiedIPv42,096
AS27046United States Department of Defense (DoD)UnclassifiedIPv41,416
AS636United States Department of Defense (DoD)UnclassifiedIPv41,116
AS149United States Department of Defense (DoD)UnclassifiedIPv4889
AS634United States Department of Defense (DoD)UnclassifiedIPv4780

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS721United States Department of Defense (DoD)UnclassifiedIPv4 IPv677,448
AS1540Headquarters, USAISCUnclassifiedIPv4 IPv640,221
AS1733United States Department of Defense (DoD)UnclassifiedIPv4 IPv67,392
AS367United States Department of Defense (DoD)UnclassifiedIPv4 IPv64,973
AS5972United States Department of Defense (DoD)UnclassifiedIPv44,726
AS5839United States Department of Defense (DoD)UnclassifiedIPv43,926
AS637United States Department of Defense (DoD)UnclassifiedIPv42,153
AS56United States Department of Defense (DoD)UnclassifiedIPv42,096
AS27046United States Department of Defense (DoD)UnclassifiedIPv41,416
AS5231United States Department of Defense (DoD)UnclassifiedIPv41,138

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.