asn.dev

Observed topology

AS399331 CONNECT2FIRST-LLC - Connect 2 First Internet, LLC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS399331: 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 IPv6712
AS400146DIAMOND STATE NETWORKS, LLCHostingIPv4 IPv6268
AS23404Ritter CommunicationsUnclassifiedIPv4267
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv614
AS971PureVoltage Hosting Inc.UnclassifiedIPv413
AS29838Atlantic Metro Communications II, Inc.HostingIPv44
AS32097WholeSale Internet, Inc.HostingIPv41
AS35280F5 Networks SARLHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS401288C&L Broadband Connect, LLCUnclassifiedIPv4190

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6838
AS400146DIAMOND STATE NETWORKS, LLCHostingIPv4 IPv6322
AS23404Ritter CommunicationsUnclassifiedIPv4277
AS401288C&L Broadband Connect, LLCUnclassifiedIPv4190
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv614
AS971PureVoltage Hosting Inc.UnclassifiedIPv413
AS29838Atlantic Metro Communications II, Inc.HostingIPv44
AS32097WholeSale Internet, Inc.HostingIPv41
AS35280F5 Networks SARLHostingIPv41

Provenance

Where this comes from

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