asn.dev

Observed topology

AS32281 CCT-LLC

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32281: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,325
AS3257GTT Communications Inc.TransitIPv4 IPv61,006
AS6939Hurricane Electric LLCTransitIPv4 IPv6703

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS16608Kentec Communications, Inc.UnclassifiedIPv4128
AS398230Roggen Enterprises BroadBand, LLCUnclassifiedIPv4 IPv661
AS26747Phillips County Telephone CompanyUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,382
AS3257GTT Communications Inc.TransitIPv4 IPv61,090
AS6939Hurricane Electric LLCTransitIPv4 IPv6755
AS16608Kentec Communications, Inc.UnclassifiedIPv4128
AS398230Roggen Enterprises BroadBand, LLCUnclassifiedIPv4 IPv661
AS26747Phillips County Telephone CompanyUnclassifiedIPv44

Provenance

Where this comes from

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