asn.dev

Observed topology

AS32035 CCDT-AS

Unclassified RIPE Cable/DSL/ISP

Upstreams 35 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 34
Adjacent (IPv6) 24
Upstream graph Who carries AS32035, and who carries them, drawn as a map up to the transit-free core. 16 exchanges Where AS32035 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 35

Networks observed carrying traffic for AS32035: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6615
AS174Cogent Communications, LLCTransitIPv4 IPv6468
AS2914NTT America, Inc.TransitIPv4 IPv6436
AS3356Level 3 Parent, LLCTransitIPv4 IPv6396
AS6939Hurricane Electric LLCTransitIPv4 IPv6382
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv664
AS22652Videotron LteeResidentialIPv4 IPv644
AS24482SG.GSHostingIPv4 IPv635
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv626
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv624

All 35 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26967Sangoma US Inc.UnclassifiedIPv4 IPv61,019
AS15092Sangoma US Inc.HostingIPv4 IPv6243

Adjacency

Adjacent networks

All 37

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

ASNetworkTypeFamiliesPaths seen
AS26967Sangoma US Inc.UnclassifiedIPv4 IPv61,019
AS1299Arelion Sweden ABTransitIPv4 IPv6822
AS174Cogent Communications, LLCTransitIPv4 IPv6647
AS3356Level 3 Parent, LLCTransitIPv4 IPv6584
AS2914NTT America, Inc.TransitIPv4 IPv6536
AS6939Hurricane Electric LLCTransitIPv4 IPv6522
AS15092Sangoma US Inc.HostingIPv4 IPv6243
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6126
AS22652Videotron LteeResidentialIPv4 IPv686
AS24482SG.GSHostingIPv4 IPv658

All 37 adjacent →

Provenance

Where this comes from

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