asn.dev

Observed topology

AS393559 WEBBING-USA

Unclassified ARIN

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS393559: 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
AS1299Arelion Sweden ABTransitIPv4 IPv64,947
AS6461Zayo BandwidthTransitIPv41,423
AS4637Telstra GlobalUnclassifiedIPv4 IPv6617
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6595
AS174Cogent Communications, LLCTransitIPv4 IPv6594
AS5511Orange S.A.TransitIPv4 IPv6337
AS6939Hurricane Electric LLCTransitIPv4 IPv6331
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4118
AS24516Virtutel Pty LtdUnclassifiedIPv4 IPv6112
AS3356Level 3 Parent, LLCTransitIPv4 IPv677

All 12 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv64,947
AS6461Zayo BandwidthTransitIPv41,423
AS4637Telstra GlobalUnclassifiedIPv4 IPv6617
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6595
AS174Cogent Communications, LLCTransitIPv4 IPv6594
AS5511Orange S.A.TransitIPv4 IPv6337
AS6939Hurricane Electric LLCTransitIPv4 IPv6331
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4118
AS24516Virtutel Pty LtdUnclassifiedIPv4 IPv6112
AS3356Level 3 Parent, LLCTransitIPv4 IPv677

All 12 adjacent →

Provenance

Where this comes from

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