asn.dev

Observed topology

AS399646 DARTNODE

Unclassified ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS399646: 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,445
AS174Cogent Communications, LLCTransitIPv4 IPv6915
AS32097WholeSale Internet, Inc.HostingIPv4 IPv6214
AS35847Ezee FiberResidentialIPv4 IPv6126

Transit

Downstream networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1050Onvox LLCUnclassifiedIPv4 IPv6170
AS40776TaoNetHostingIPv4 IPv698
AS212532XIAO YANG WEN RUIUnclassifiedIPv4 IPv673
AS63127TheMaple Inc.UnclassifiedIPv466
AS205563Marc GomezUnclassifiedIPv664
AS200790BYTEFIZZ LLCUnclassifiedIPv636
AS204871Shihabudheen P KUnclassifiedIPv634
AS55223BGP Networks LLCUnclassifiedIPv632
AS200329Monil ChhedaUnclassifiedIPv632
AS206042Suhail HarisUnclassifiedIPv632

All 11 downstreams →

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,661
AS174Cogent Communications, LLCTransitIPv4 IPv61,306
AS32097WholeSale Internet, Inc.HostingIPv4 IPv6214
AS1050Onvox LLCUnclassifiedIPv4 IPv6170
AS35847Ezee FiberResidentialIPv4 IPv6164
AS40776TaoNetHostingIPv4 IPv698
AS212532XIAO YANG WEN RUIUnclassifiedIPv4 IPv673
AS63127TheMaple Inc.UnclassifiedIPv466
AS205563Marc GomezUnclassifiedIPv664
AS200790BYTEFIZZ LLCUnclassifiedIPv636

All 15 adjacent →

Provenance

Where this comes from

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