Observed topology

AS6620 AS-6620

Residential ARIN

Upstreams 8 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6620: 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
AS6461	Zayo Bandwidth	Transit	IPv4	2,433
AS174	Cogent Communications, LLC	Transit	IPv4	809
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4	636
AS7029	Windstream Communications LLC	Residential	IPv4	576
AS7018	AT&T Enterprises, LLC	Residential	IPv4	482
AS1299	Arelion Sweden AB	Transit	IPv4	470
AS13876	FiberLight, LLC	Unclassified	IPv4	450
AS701	Verizon Business	Residential	IPv4	45

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS397037	City of Amarillo	Unclassified	IPv4	77

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6461	Zayo Bandwidth	Transit	IPv4	2,507
AS174	Cogent Communications, LLC	Transit	IPv4	809
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4	636
AS7029	Windstream Communications LLC	Residential	IPv4	577
AS7018	AT&T Enterprises, LLC	Residential	IPv4	484
AS1299	Arelion Sweden AB	Transit	IPv4	470
AS13876	FiberLight, LLC	Unclassified	IPv4	450
AS397037	City of Amarillo	Unclassified	IPv4	77
AS701	Verizon Business	Residential	IPv4	45

Provenance

Where this comes from

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