Observed topology

AS20220 INDIAN-WELLS - Indian Wells Valley ISP

Unclassified ARIN

Upstreams 3 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20220: 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
AS53828	NETWORK INNOVATIONS, LLC	Unclassified	IPv4 IPv6	153
AS30041	Race Tech, LLC	Unclassified	IPv4	33
AS5650	Frontier Communications of America, Inc.	Residential	IPv4	27

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS399032	Cosner-Neipp Corporation	Unclassified	IPv4 IPv6	42

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS53828	NETWORK INNOVATIONS, LLC	Unclassified	IPv4 IPv6	190
AS399032	Cosner-Neipp Corporation	Unclassified	IPv4 IPv6	42
AS30041	Race Tech, LLC	Unclassified	IPv4	34
AS5650	Frontier Communications of America, Inc.	Residential	IPv4	31

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.