Observed topology

AS22191 WILKES-COMM

Unclassified ARIN Cable/DSL/ISP

Upstreams 9 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22191: 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
AS32425	Pixel Factory	Hosting	IPv4 IPv6	1,365
AS3257	GTT Communications Inc.	Transit	IPv4	547
AS19108	Optimum	Unclassified	IPv4	345
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	182
AS27446	ERC Broadband	Unclassified	IPv4	142
AS64213	ERC Broadband	Unclassified	IPv4	136
AS32505	Conterra	Unclassified	IPv4	65
AS174	Cogent Communications, LLC	Transit	IPv4	40
AS22773	Cox Communications Inc.	Residential	IPv4	16

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS46347	Carolina West Wireless	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS32425	Pixel Factory	Hosting	IPv4 IPv6	1,365
AS3257	GTT Communications Inc.	Transit	IPv4	586
AS19108	Optimum	Unclassified	IPv4	345
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	182
AS27446	ERC Broadband	Unclassified	IPv4	152
AS64213	ERC Broadband	Unclassified	IPv4	146
AS32505	Conterra	Unclassified	IPv4	65
AS46347	Carolina West Wireless	Unclassified	IPv4	59
AS174	Cogent Communications, LLC	Transit	IPv4	40
AS22773	Cox Communications Inc.	Residential	IPv4	16

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-26 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.