asn.dev

Observed topology

AS399122 AS-VPSHOUSE

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS399122: 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
AS397423Tier.Net Technologies LLCHostingIPv4 IPv61,305
AS397373H4Y Technologies LLCHostingIPv4 IPv6912
AS55286B2 Net Solutions Inc.HostingIPv4 IPv6656
AS174Cogent Communications, LLCTransitIPv4 IPv6500
AS6206Netrouting B.V.HostingIPv4 IPv6476
AS19318Interserver, IncHostingIPv4 IPv6184
AS40676Psychz NetworksHostingIPv4 IPv6182
AS36352HostPapaHostingIPv4 IPv6148
AS29802HIVELOCITY, Inc.HostingIPv4 IPv6101

Transit

Downstream networks

inferred

Networks for which AS399122 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS397423Tier.Net Technologies LLCHostingIPv4 IPv61,305
AS397373H4Y Technologies LLCHostingIPv4 IPv6912
AS55286B2 Net Solutions Inc.HostingIPv4 IPv6656
AS174Cogent Communications, LLCTransitIPv4 IPv6500
AS6206Netrouting B.V.HostingIPv4 IPv6476
AS19318Interserver, IncHostingIPv4 IPv6184
AS40676Psychz NetworksHostingIPv4 IPv6182
AS36352HostPapaHostingIPv4 IPv6148
AS29802HIVELOCITY, Inc.HostingIPv4 IPv6101

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.