Observed topology

AS22062 GEOSTAR

Unclassified ARIN Cable/DSL/ISP

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22062: 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	293
AS11696	Fusion, LLC	Unclassified	IPv4	108
AS174	Cogent Communications, LLC	Transit	IPv4	102
AS1299	Arelion Sweden AB	Transit	IPv4	69
AS19009	OneCleveland	Unclassified	IPv4	43
AS20205	Amplex Electric, Inc.	Residential	IPv4	9

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS396279	WASHINGTON ELECTRIC COOPERATIVE, INC.	Unclassified	IPv4 IPv6	84

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	353
AS174	Cogent Communications, LLC	Transit	IPv4	124
AS11696	Fusion, LLC	Unclassified	IPv4	108
AS396279	WASHINGTON ELECTRIC COOPERATIVE, INC.	Unclassified	IPv4 IPv6	84
AS1299	Arelion Sweden AB	Transit	IPv4	69
AS19009	OneCleveland	Unclassified	IPv4	43
AS20205	Amplex Electric, Inc.	Residential	IPv4	11

Provenance

Where this comes from

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