Observed topology
AS27066 DNIC-ASBLK-27032-27159 - United States Department of Defense (DoD)
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS27066: 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 | 6,903 |
Transit
Downstream networks
Networks for which AS27066 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS647 | United States Department of Defense (DoD) | Unclassified | IPv4 | 22,818 |
| AS1600 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 10,504 |
| AS5972 | United States Department of Defense (DoD) | Unclassified | IPv4 | 9,211 |
| AS1637 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 6,883 |
| AS637 | United States Department of Defense (DoD) | Unclassified | IPv4 | 4,490 |
| AS27046 | United States Department of Defense (DoD) | Unclassified | IPv4 | 3,897 |
| AS1649 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 3,752 |
| AS1516 | Headquarters, USAISC | Unclassified | IPv4 | 3,356 |
| AS747 | Headquarters, USAISC | Unclassified | IPv4 | 2,259 |
| AS27137 | United States Department of Defense (DoD) | Unclassified | IPv4 | 1,341 |
Adjacency
Adjacent networks
Every AS seen directly next to AS27066 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS721 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 80,748 |
| AS647 | United States Department of Defense (DoD) | Unclassified | IPv4 | 22,818 |
| AS1600 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 10,504 |
| AS5972 | United States Department of Defense (DoD) | Unclassified | IPv4 | 9,211 |
| AS1637 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 6,883 |
| AS637 | United States Department of Defense (DoD) | Unclassified | IPv4 | 4,490 |
| AS27046 | United States Department of Defense (DoD) | Unclassified | IPv4 | 3,897 |
| AS1649 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 3,752 |
| AS1516 | Headquarters, USAISC | Unclassified | IPv4 | 3,356 |
| AS747 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 3,319 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.