asn.dev

Observed topology

AS22258 COMCAST-22258

Unclassified ARIN Cable/DSL/ISP

Upstreams 1 carry this network
Downstreams 14 this network carries
Adjacent (IPv4) 15
Adjacent (IPv6) 3
Upstream graph Who carries AS22258, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS22258 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22258: 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.

ASNetworkTypeFamiliesPaths seen
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv6760

Transit

Downstream networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS54113Fastly, Inc.HostingIPv4 IPv6121
AS26735Memphis Light, Gas & WaterUnclassifiedIPv4117
AS14303City of MemphisUnclassifiedIPv480
AS32032Orgill, Inc.UnclassifiedIPv479
AS36040Google LLCHostingIPv459
AS394824Christian Brothers UniversityUnclassifiedIPv458
AS13335Cloudflare, Inc.HostingIPv4 IPv612
AS23386Crye Leike RealtorsUnclassifiedIPv410
AS23509Inventory Locator Service, LLCUnclassifiedIPv410
AS36862Green Mountain Technology, LLCUnclassifiedIPv410

All 14 downstreams →

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv61,341
AS54113Fastly, Inc.HostingIPv4 IPv6121
AS26735Memphis Light, Gas & WaterUnclassifiedIPv4117
AS14303City of MemphisUnclassifiedIPv480
AS32032Orgill, Inc.UnclassifiedIPv479
AS36040Google LLCHostingIPv459
AS394824Christian Brothers UniversityUnclassifiedIPv458
AS13335Cloudflare, Inc.HostingIPv4 IPv612
AS23386Crye Leike RealtorsUnclassifiedIPv410
AS23509Inventory Locator Service, LLCUnclassifiedIPv410

All 15 adjacent →

Provenance

Where this comes from

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