Observed topology

AS22513 CHARTER-22513-WA-OR-C3

Unclassified ARIN

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22513: 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
AS20115	Charter Communications LLC	Residential	IPv4 IPv6	194

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS11336	BlackRock Financial Management, Inc.	Unclassified	IPv4	92
AS11741	BENTON REA POWERNET	Unclassified	IPv4	63
AS53962	2140 Networks LLC	Unclassified	IPv4	59
AS13866	Computer Country	Unclassified	IPv4	50

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS20115	Charter Communications LLC	Residential	IPv4 IPv6	458
AS11336	BlackRock Financial Management, Inc.	Unclassified	IPv4	92
AS11741	BENTON REA POWERNET	Unclassified	IPv4	63
AS53962	2140 Networks LLC	Unclassified	IPv4	59
AS13866	Computer Country	Unclassified	IPv4	50

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.