asn.dev

Observed topology

AS33570 CLOUDPATH - Cloudpath

Unclassified ARIN NSP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS33570: 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
AS6939Hurricane Electric LLCTransitIPv4539
AS3356Level 3 Parent, LLCTransitIPv4201
AS174Cogent Communications, LLCTransitIPv4126
AS22652Videotron LteeResidentialIPv434
AS34549meerfarbig GmbH & Co. KGHostingIPv433
AS54004Cablevision Lightpath LLCUnclassifiedIPv423
AS24482SG.GSHostingIPv417
AS37721Virtual Technologies & SolutionsResidentialIPv417
AS33891Core-Backbone GmbHHostingIPv49
AS293ESnetUnclassifiedIPv48

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6343Omega Systems Consultants, LLCUnclassifiedIPv446

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4585
AS3356Level 3 Parent, LLCTransitIPv4201
AS174Cogent Communications, LLCTransitIPv4126
AS6343Omega Systems Consultants, LLCUnclassifiedIPv446
AS22652Videotron LteeResidentialIPv434
AS34549meerfarbig GmbH & Co. KGHostingIPv433
AS54004Cablevision Lightpath LLCUnclassifiedIPv423
AS24482SG.GSHostingIPv417
AS37721Virtual Technologies & SolutionsResidentialIPv417
AS33891Core-Backbone GmbHHostingIPv49

All 16 adjacent →

Provenance

Where this comes from

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