asn.dev

Observed topology

AS26666 INTERSERVER-LAX

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26666: 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
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv61,401
AS3257GTT Communications Inc.TransitIPv4 IPv6852
AS6461Zayo BandwidthTransitIPv4 IPv6535
AS7381BroadbandONE, LLCHostingIPv4 IPv6118

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214693Fusiora OUResidentialIPv4 IPv6154
AS64245DigitalFyre Internet Solutions, LLC.UnclassifiedIPv4 IPv695
AS153040YouStableUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv61,470
AS3257GTT Communications Inc.TransitIPv4 IPv6938
AS6461Zayo BandwidthTransitIPv4 IPv6669
AS214693Fusiora OUResidentialIPv4 IPv6154
AS7381BroadbandONE, LLCHostingIPv4 IPv6139
AS64245DigitalFyre Internet Solutions, LLC.UnclassifiedIPv4 IPv695
AS153040YouStableUnclassifiedIPv461

Provenance

Where this comes from

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