asn.dev

Observed topology

AS10004 AS-PHOENIX-J Phoenix Communications Inc.

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10004: 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
AS4637Telstra GlobalUnclassifiedIPv4 IPv6328
AS2519ARTERIA Networks CorporationUnclassifiedIPv4126
AS6939Hurricane Electric LLCTransitIPv493
AS17961mitene internet co., ltd.UnclassifiedIPv482
AS9002RETN LimitedUnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv612
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS131948FORNEXT Inc.UnclassifiedIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24229IX-layers, Inc.UnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4637Telstra GlobalUnclassifiedIPv4 IPv6340
AS2519ARTERIA Networks CorporationUnclassifiedIPv4128
AS6939Hurricane Electric LLCTransitIPv493
AS17961mitene internet co., ltd.UnclassifiedIPv482
AS24229IX-layers, Inc.UnclassifiedIPv414
AS9002RETN LimitedUnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv612
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS131948FORNEXT Inc.UnclassifiedIPv410

Provenance

Where this comes from

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