asn.dev

Observed topology

AS62904 AS62904 - Eonix Corporation

Hosting DROP-listed space ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62904: 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 IPv617,628
AS6939Hurricane Electric LLCTransitIPv4 IPv611,490
AS23033Wowrack.comHostingIPv4 IPv66,812
AS1299Arelion Sweden ABTransitIPv4 IPv64,838
AS11403NYIHostingIPv4 IPv6586
AS53767iCastCenterHostingIPv4127

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12586GHOSTnet GmbHHostingIPv4131

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv617,641
AS6939Hurricane Electric LLCTransitIPv4 IPv611,608
AS23033Wowrack.comHostingIPv4 IPv66,812
AS1299Arelion Sweden ABTransitIPv4 IPv64,838
AS11403NYIHostingIPv4 IPv6586
AS12586GHOSTnet GmbHHostingIPv4131
AS53767iCastCenterHostingIPv4127

Provenance

Where this comes from

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