asn.dev

Observed topology

AS668 DNIC-AS-00668 - United States Department of Defense (DoD)

Business ARIN Educational/Research

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

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv610,331
AS701Verizon BusinessResidentialIPv4 IPv61,079
AS2914NTT America, Inc.TransitIPv4565
AS7575Australian Academic and Research Network (AARNet)EducationIPv4 IPv6365
AS2153CENICUnclassifiedIPv4184
AS11537Internet2UnclassifiedIPv4184
AS293ESnetUnclassifiedIPv4178
AS35889University of HawaiiUnclassifiedIPv46
AS6360University of HawaiiEducationIPv42

Transit

Downstream networks

All 27

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

ASNetworkTypeFamiliesPaths seen
AS37Navy Network Information Center (NNIC)UnclassifiedIPv4 IPv61,210
AS518United States Department of Defense (DoD)UnclassifiedIPv4 IPv61,109
AS289Headquarters, USAISCUnclassifiedIPv4 IPv6759
AS13Headquarters, USAISCUnclassifiedIPv4 IPv6520
AS89Navy Network Information Center (NNIC)UnclassifiedIPv4 IPv6446
AS22Navy Network Information Center (NNIC)UnclassifiedIPv4 IPv6419
AS121United States Department of Defense (DoD)UnclassifiedIPv4414
AS84Navy Network Information Center (NNIC)UnclassifiedIPv4 IPv6382
AS252Headquarters, USAISCUnclassifiedIPv4 IPv6380
AS687United States Department of Defense (DoD)UnclassifiedIPv4345

Adjacency

Adjacent networks

All 36

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv616,561
AS701Verizon BusinessResidentialIPv4 IPv61,936
AS37Navy Network Information Center (NNIC)UnclassifiedIPv4 IPv61,210
AS518United States Department of Defense (DoD)UnclassifiedIPv4 IPv61,109
AS2914NTT America, Inc.TransitIPv4 IPv6918
AS289Headquarters, USAISCUnclassifiedIPv4 IPv6759
AS7575Australian Academic and Research Network (AARNet)EducationIPv4 IPv6592
AS13Headquarters, USAISCUnclassifiedIPv4 IPv6520
AS89Navy Network Information Center (NNIC)UnclassifiedIPv4 IPv6446
AS22Navy Network Information Center (NNIC)UnclassifiedIPv4 IPv6419

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M 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.