asn.dev

Observed topology

AS22909 COMCAST-22909

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22909: 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 IPv61,876

Transit

Downstream networks

All 42

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

ASNetworkTypeFamiliesPaths seen
AS19685CSI Telecom Group, IncUnclassifiedIPv41,380
AS17123Team Health, Inc.UnclassifiedIPv4240
AS11086Pitney Bowes IncorporatedUnclassifiedIPv4179
AS4374CKE Restaurants Holdings, Inc.UnclassifiedIPv4175
AS62958ADT LLCUnclassifiedIPv4101
AS54113Fastly, Inc.HostingIPv4 IPv692
AS25712Computer Services IncUnclassifiedIPv490
AS11297Lipscomb UniversityEducationIPv4 IPv680
AS27016United States Nuclear Regulatory CommissionUnclassifiedIPv4 IPv674
AS26335Middle Tennessee State UniversityUnclassifiedIPv469

Adjacency

Adjacent networks

All 44

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

ASNetworkTypeFamiliesPaths seen
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv64,278
AS19685CSI Telecom Group, IncUnclassifiedIPv41,380
AS3356Level 3 Parent, LLCTransitIPv41,030
AS17123Team Health, Inc.UnclassifiedIPv4240
AS11086Pitney Bowes IncorporatedUnclassifiedIPv4179
AS4374CKE Restaurants Holdings, Inc.UnclassifiedIPv4175
AS62958ADT LLCUnclassifiedIPv4101
AS54113Fastly, Inc.HostingIPv4 IPv692
AS25712Computer Services IncUnclassifiedIPv490
AS11297Lipscomb UniversityEducationIPv4 IPv680

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.