asn.dev

Observed topology

AS393424 AS-TORIX-SVC

Unclassified ARIN Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS393424: 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
AS21949Beanfield Technologies Inc.UnclassifiedIPv4 IPv665
AS2914NTT America, Inc.TransitIPv4 IPv663
AS1403EBOXResidentialIPv66
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv65
AS22652Videotron LteeResidentialIPv4 IPv65
AS852TELUS Communications Inc.ResidentialIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv64
AS20473The Constant Company, LLCHostingIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS400803Toronto Internet Exchange CommunityUnclassifiedIPv460

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS21949Beanfield Technologies Inc.UnclassifiedIPv4 IPv691
AS2914NTT America, Inc.TransitIPv4 IPv682
AS400803Toronto Internet Exchange CommunityUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv48
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv67
AS22652Videotron LteeResidentialIPv4 IPv67
AS1403EBOXResidentialIPv66
AS852TELUS Communications Inc.ResidentialIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65

All 11 adjacent →

Provenance

Where this comes from

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