asn.dev

Observed topology

AS5009 EATEL

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5009: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6431
AS3257GTT Communications Inc.TransitIPv4 IPv6355
AS6939Hurricane Electric LLCTransitIPv4 IPv6199
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv618
AS293ESnetUnclassifiedIPv417

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27294Reserve Long Distance Company, IncUnclassifiedIPv4292
AS36372REVUnclassifiedIPv4 IPv6148
AS36730Transformyx, Inc.ResidentialIPv485
AS395236Star CommunicationsUnclassifiedIPv4 IPv641
AS33496ISC CONSTRUCTORS, LLCUnclassifiedIPv637
AS20355REVUnclassifiedIPv4 IPv636
AS397103REVUnclassifiedIPv424
AS18855AWC Inc.UnclassifiedIPv44
AS19779St. George Fire DepartmentUnclassifiedIPv44

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6700
AS3257GTT Communications Inc.TransitIPv4 IPv6657
AS6939Hurricane Electric LLCTransitIPv4 IPv6519
AS27294Reserve Long Distance Company, IncUnclassifiedIPv4292
AS36372REVUnclassifiedIPv4 IPv6258
AS20355REVUnclassifiedIPv4 IPv6147
AS36730Transformyx, Inc.ResidentialIPv485
AS395236Star CommunicationsUnclassifiedIPv4 IPv641
AS33496ISC CONSTRUCTORS, LLCUnclassifiedIPv637
AS397103REVUnclassifiedIPv424

Provenance

Where this comes from

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