asn.dev

Observed topology

AS33654 CMCS

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33654: 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, LLCResidentialIPv6512

Transit

Downstream networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS394037RIO CITIESUnclassifiedIPv4 IPv6136
AS54113Fastly, Inc.HostingIPv4 IPv691
AS62621SUMMITELECUnclassifiedIPv4 IPv690
AS400445NUSENDA FEDERAL CREDIT UNIONUnclassifiedIPv467
AS401002Bridgers & Paxton Consulting Engineers, Inc.UnclassifiedIPv459
AS36424Home Security Systems, LLCUnclassifiedIPv458
AS30331St. Vincent HospitalUnclassifiedIPv448
AS394997Nexum, Inc.UnclassifiedIPv416
AS397167Presbyterian Healthcare ServicesUnclassifiedIPv411
AS3388University of New MexicoEducationIPv410

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv61,126
AS394037RIO CITIESUnclassifiedIPv4 IPv6136
AS54113Fastly, Inc.HostingIPv4 IPv691
AS62621SUMMITELECUnclassifiedIPv4 IPv690
AS400445NUSENDA FEDERAL CREDIT UNIONUnclassifiedIPv467
AS401002Bridgers & Paxton Consulting Engineers, Inc.UnclassifiedIPv459
AS36424Home Security Systems, LLCUnclassifiedIPv458
AS30331St. Vincent HospitalUnclassifiedIPv448
AS394997Nexum, Inc.UnclassifiedIPv416
AS397167Presbyterian Healthcare ServicesUnclassifiedIPv411

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.