Observed topology

AS6614 USCC-ASN

Mobile ARIN Cable/DSL/ISP

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6614: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	1,365
AS2914	NTT America, Inc.	Transit	IPv4	1,051
AS6939	Hurricane Electric LLC	Transit	IPv4	450
AS7018	AT&T Enterprises, LLC	Residential	IPv4	100
AS852	TELUS Communications Inc.	Residential	IPv4	48
AS24482	SG.GS	Hosting	IPv4	48
AS37721	Virtual Technologies & Solutions	Residential	IPv4	48

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS18933	T-Mobile USA, Inc.	Unclassified	IPv4	746

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	1,655
AS2914	NTT America, Inc.	Transit	IPv4	1,282
AS18933	T-Mobile USA, Inc.	Unclassified	IPv4	746
AS6939	Hurricane Electric LLC	Transit	IPv4	569
AS7018	AT&T Enterprises, LLC	Residential	IPv4	171
AS852	TELUS Communications Inc.	Residential	IPv4	61
AS24482	SG.GS	Hosting	IPv4	59
AS37721	Virtual Technologies & Solutions	Residential	IPv4	59

Provenance

Where this comes from

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