asn.dev

Observed topology

AS395839 HOSTKEY-USA - HOSTKEY

Unclassified ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS395839: 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 IPv61,707
AS174Cogent Communications, LLCTransitIPv4 IPv61,058
AS3257GTT Communications Inc.TransitIPv4 IPv6545

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26383Baxet Group Inc.UnclassifiedIPv4 IPv6692
AS204154FIRST SERVER LIMITEDUnclassifiedIPv4 IPv6366
AS207461HOSTING INDUSTRY LIMITEDUnclassifiedIPv4 IPv6263
AS48729ServerKing B.V.UnclassifiedIPv4116
AS200313IT WEB LTDUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,450
AS174Cogent Communications, LLCTransitIPv4 IPv61,539
AS3257GTT Communications Inc.TransitIPv4 IPv6823
AS26383Baxet Group Inc.UnclassifiedIPv4 IPv6692
AS204154FIRST SERVER LIMITEDUnclassifiedIPv4 IPv6366
AS207461HOSTING INDUSTRY LIMITEDUnclassifiedIPv4 IPv6263
AS48729ServerKing B.V.UnclassifiedIPv4116
AS200313IT WEB LTDUnclassifiedIPv465

Provenance

Where this comes from

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