asn.dev

Observed topology

AS396422 3DS-AS01

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396422: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6704
AS174Cogent Communications, LLCTransitIPv4 IPv6325
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv69
AS293ESnetUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS401514Kern Valley Wireless, IncUnclassifiedIPv4 IPv6464
AS361863ds Communications LLCHostingIPv4 IPv6102
AS399694BRIGHTON BROADBAND INC.UnclassifiedIPv4 IPv691
AS401574Wifires Communications, LLCUnclassifiedIPv670
AS36521H.O.P. Communications DBA airHOPUnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,325
AS401514Kern Valley Wireless, IncUnclassifiedIPv4 IPv6464
AS174Cogent Communications, LLCTransitIPv4 IPv6424
AS361863ds Communications LLCHostingIPv4 IPv6102
AS399694BRIGHTON BROADBAND INC.UnclassifiedIPv4 IPv691
AS401574Wifires Communications, LLCUnclassifiedIPv670
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv618
AS293ESnetUnclassifiedIPv47
AS36521H.O.P. Communications DBA airHOPUnclassifiedIPv43

Provenance

Where this comes from

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