asn.dev

Observed topology

AS399898 CONEXON-CONNECT

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS399898: 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
AS1299Arelion Sweden ABTransitIPv4 IPv62,949
AS6939Hurricane Electric LLCTransitIPv4 IPv61,682
AS174Cogent Communications, LLCTransitIPv4 IPv6995
AS34927iFog GmbHHostingIPv611

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS400136Volt BroadbandUnclassifiedIPv4 IPv61,129
AS401350Conexon ConnectUnclassifiedIPv4 IPv692
AS400337NH Broadband, LLCUnclassifiedIPv4 IPv662
AS394675Litten Communications LLCUnclassifiedIPv456
AS36077Mitchell Electric Membership CorporationHostingIPv4 IPv637

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv63,691
AS6939Hurricane Electric LLCTransitIPv4 IPv62,027
AS174Cogent Communications, LLCTransitIPv4 IPv61,283
AS400136Volt BroadbandUnclassifiedIPv4 IPv61,129
AS401350Conexon ConnectUnclassifiedIPv4 IPv692
AS400337NH Broadband, LLCUnclassifiedIPv4 IPv662
AS394675Litten Communications LLCUnclassifiedIPv456
AS36077Mitchell Electric Membership CorporationHostingIPv4 IPv637
AS34927iFog GmbHHostingIPv612

Provenance

Where this comes from

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