asn.dev

Observed topology

AS401665 HOSTBILBY

Hosting ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS401665: 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
AS835GoCodeIT IncUnclassifiedIPv4 IPv6118
AS400304Redoubt NetworksHostingIPv4 IPv690
AS1299Arelion Sweden ABTransitIPv4 IPv678
AS6939Hurricane Electric LLCTransitIPv420
AS3257GTT Communications Inc.TransitIPv4 IPv613
AS22652Videotron LteeResidentialIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv63
AS1403EBOXResidentialIPv62
AS394256Tech Futures Interactive Inc.UnclassifiedIPv42
AS20473The Constant Company, LLCHostingIPv61

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152586KuroitUnclassifiedIPv4 IPv6362
AS402356GridpriseUnclassifiedIPv4 IPv691
AS40776TaoNetHostingIPv636

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS152586KuroitUnclassifiedIPv4 IPv6362
AS1299Arelion Sweden ABTransitIPv4 IPv6291
AS835GoCodeIT IncUnclassifiedIPv4 IPv6282
AS402356GridpriseUnclassifiedIPv4 IPv691
AS400304Redoubt NetworksHostingIPv4 IPv690
AS3257GTT Communications Inc.TransitIPv4 IPv668
AS6939Hurricane Electric LLCTransitIPv4 IPv651
AS40776TaoNetHostingIPv636
AS22652Videotron LteeResidentialIPv4 IPv612
AS1403EBOXResidentialIPv68

All 14 adjacent →

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.