asn.dev

Observed topology

AS25668 CIPHERKEY

Unclassified ARIN

Upstreams 11 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 13
Adjacent (IPv6) 6
Upstream graph Who carries AS25668, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS25668 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS25668: 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
AS6461Zayo BandwidthTransitIPv4982
AS2914NTT America, Inc.TransitIPv4 IPv6796
AS174Cogent Communications, LLCTransitIPv4 IPv6543
AS6939Hurricane Electric LLCTransitIPv4 IPv6451
AS9002RETN LimitedUnclassifiedIPv4 IPv6353
AS22652Videotron LteeResidentialIPv4 IPv6117
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv659
AS7575Australian Academic and Research Network (AARNet)EducationIPv458
AS3130RGnet OUUnclassifiedIPv457
AS24482SG.GSHostingIPv457

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27232OOMA ENTERPRISE - Ooma, Inc.UnclassifiedIPv434
AS398872Big WifiUnclassifiedIPv415

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv41,010
AS2914NTT America, Inc.TransitIPv4 IPv6808
AS174Cogent Communications, LLCTransitIPv4 IPv6546
AS6939Hurricane Electric LLCTransitIPv4 IPv6451
AS9002RETN LimitedUnclassifiedIPv4 IPv6353
AS22652Videotron LteeResidentialIPv4 IPv6123
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv659
AS7575Australian Academic and Research Network (AARNet)EducationIPv458
AS3130RGnet OUUnclassifiedIPv457
AS24482SG.GSHostingIPv457

All 13 adjacent →

Provenance

Where this comes from

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