Observed topology
AS27064 DNIC-ASBLK-27032-27159
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS27064: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS721 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 56,962 |
Transit
Downstream networks
Networks for which AS27064 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1540 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 87,083 |
| AS5972 | United States Department of Defense (DoD) | Unclassified | IPv4 | 74,405 |
| AS5852 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 54,889 |
| AS56 | United States Department of Defense (DoD) | Unclassified | IPv4 | 53,006 |
| AS27046 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 30,153 |
| AS637 | United States Department of Defense (DoD) | Unclassified | IPv4 | 24,879 |
| AS367 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 17,149 |
| AS5371 | United States Department of Defense (DoD) | Unclassified | IPv4 | 15,182 |
| AS1602 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 8,260 |
| AS27138 | United States Department of Defense (DoD) | Unclassified | IPv4 | 8,033 |
Adjacency
Adjacent networks
Every AS seen directly next to AS27064 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS721 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 605,158 |
| AS1540 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 173,004 |
| AS5972 | United States Department of Defense (DoD) | Unclassified | IPv4 | 74,405 |
| AS5852 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 55,159 |
| AS56 | United States Department of Defense (DoD) | Unclassified | IPv4 | 53,006 |
| AS367 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 33,640 |
| AS27046 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 30,153 |
| AS745 | Air Force Systems Networking | Unclassified | IPv4 | 27,457 |
| AS637 | United States Department of Defense (DoD) | Unclassified | IPv4 | 24,879 |
| AS5371 | United States Department of Defense (DoD) | Unclassified | IPv4 | 15,182 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.