Observed topology
AS668 DNIC-AS-00668
Business ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS668: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 10,589 |
| AS701 | Verizon Business | Residential | IPv4 IPv6 | 956 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 582 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 IPv6 | 377 |
| AS2153 | CENIC | Unclassified | IPv4 | 191 |
| AS11537 | Internet2 | Unclassified | IPv4 | 191 |
| AS293 | ESnet | Unclassified | IPv4 | 185 |
| AS35889 | University of Hawaii | Unclassified | IPv4 | 6 |
| AS6360 | University of Hawaii | Education | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS668 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS37 | Navy Network Information Center (NNIC) | Unclassified | IPv4 IPv6 | 1,176 |
| AS518 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 1,079 |
| AS13 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 506 |
| AS289 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 439 |
| AS89 | Navy Network Information Center (NNIC) | Unclassified | IPv4 IPv6 | 434 |
| AS22 | Navy Network Information Center (NNIC) | Unclassified | IPv4 IPv6 | 409 |
| AS121 | United States Department of Defense (DoD) | Unclassified | IPv4 | 402 |
| AS84 | Navy Network Information Center (NNIC) | Unclassified | IPv4 IPv6 | 372 |
| AS252 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 370 |
| AS687 | United States Department of Defense (DoD) | Unclassified | IPv4 | 335 |
Adjacency
Adjacent networks
Every AS seen directly next to AS668 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 16,519 |
| AS701 | Verizon Business | Residential | IPv4 IPv6 | 1,666 |
| AS37 | Navy Network Information Center (NNIC) | Unclassified | IPv4 IPv6 | 1,176 |
| AS518 | United States Department of Defense (DoD) | Unclassified | IPv4 IPv6 | 1,079 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 904 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 IPv6 | 595 |
| AS13 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 506 |
| AS289 | Headquarters, USAISC | Unclassified | IPv4 IPv6 | 439 |
| AS89 | Navy Network Information Center (NNIC) | Unclassified | IPv4 IPv6 | 434 |
| AS22 | Navy Network Information Center (NNIC) | Unclassified | IPv4 IPv6 | 409 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.