Observed topology
AS27065 DNIC-ASBLK-27032-27159
Unclassified ARIN
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS721 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 3,661 |
Transit
Downstream networks
Networks for which AS27065 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 | 28,790 |
| AS5972 | United States Department of Defense (DoD) | Unclassified | IPv4 | 4,675 |
| AS367 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 4,151 |
| AS5839 | United States Department of Defense (DoD) | Unclassified | IPv4 | 2,928 |
| AS637 | United States Department of Defense (DoD) | Unclassified | IPv4 | 2,091 |
| AS56 | United States Department of Defense (DoD) | Unclassified | IPv4 | 2,082 |
| AS27046 | United States Department of Defense (DoD) | Unclassified | IPv4 | 1,416 |
| AS636 | United States Department of Defense (DoD) | Unclassified | IPv4 | 1,121 |
| AS149 | United States Department of Defense (DoD) | Unclassified | IPv4 | 892 |
| AS634 | United States Department of Defense (DoD) | Unclassified | IPv4 | 780 |
Adjacency
Adjacent networks
Every AS seen directly next to AS27065 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS721 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 76,059 |
| AS1540 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 40,337 |
| AS1733 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 7,519 |
| AS367 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 5,150 |
| AS5972 | United States Department of Defense (DoD) | Unclassified | IPv4 | 4,675 |
| AS5839 | United States Department of Defense (DoD) | Unclassified | IPv4 | 2,928 |
| AS637 | United States Department of Defense (DoD) | Unclassified | IPv4 | 2,091 |
| AS56 | United States Department of Defense (DoD) | Unclassified | IPv4 | 2,082 |
| AS27046 | United States Department of Defense (DoD) | Unclassified | IPv4 | 1,416 |
| AS5231 | United States Department of Defense (DoD) | Unclassified | IPv4 | 1,138 |
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.