Observed topology

AS16700 CNSNEXT - CNSNext

Residential ARIN Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

Upstream graph Who carries AS16700, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS16700 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16700: 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	537
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	242
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	36

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS397613	Network Technology Solutions, LLC	Unclassified	IPv4	130
AS31784	City of Bainbridge	Unclassified	IPv4 IPv6	42
AS54485	Philadelphia College of Osteopathic Medicine	Unclassified	IPv4	40

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	709
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	242
AS397613	Network Technology Solutions, LLC	Unclassified	IPv4	130
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	76
AS31784	City of Bainbridge	Unclassified	IPv4 IPv6	42
AS54485	Philadelphia College of Osteopathic Medicine	Unclassified	IPv4	40

Provenance

Where this comes from

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