asn.dev

Observed topology

AS396993 SORAXUS

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396993: 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 IPv6386
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv6162
AS22652Videotron LteeResidentialIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS219469PrivateByte LtdUnclassifiedIPv4116
AS19415Paul Bunyan Technologies, LLCHostingIPv4 IPv660
AS206479AceRDP LtdUnclassifiedIPv458
AS400890AMTECH BUSINESS SOLUTIONS.UnclassifiedIPv457
AS401170HBG Inc.UnclassifiedIPv4 IPv641
AS208812Ondrya LLCUnclassifiedIPv632
AS50224Ryan SoUnclassifiedIPv416

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6766
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv6162
AS219469PrivateByte LtdUnclassifiedIPv4116
AS19415Paul Bunyan Technologies, LLCHostingIPv4 IPv660
AS206479AceRDP LtdUnclassifiedIPv458
AS400890AMTECH BUSINESS SOLUTIONS.UnclassifiedIPv457
AS401170HBG Inc.UnclassifiedIPv4 IPv641
AS208812Ondrya LLCUnclassifiedIPv632
AS50224Ryan SoUnclassifiedIPv416
AS22652Videotron LteeResidentialIPv4 IPv65

Provenance

Where this comes from

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