asn.dev

Observed topology

AS62715 CRASHPLAN - CrashPlan

Hosting ARIN

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

Transit

Upstream networks

All 32

Networks observed carrying traffic for AS62715: 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 LLCTransitIPv4341
AS174Cogent Communications, LLCTransitIPv4267
AS2914NTT America, Inc.TransitIPv4133
AS3356Level 3 Parent, LLCTransitIPv4125
AS11537Internet2UnclassifiedIPv436
AS24247PacketFabric (Hong Kong) LimitedUnclassifiedIPv426
AS2764AAPT LimitedUnclassifiedIPv422
AS9002RETN LimitedUnclassifiedIPv413
AS24482SG.GSHostingIPv49
AS7575Australian Academic and Research Network (AARNet)EducationIPv47

All 32 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 32

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4341
AS174Cogent Communications, LLCTransitIPv4267
AS2914NTT America, Inc.TransitIPv4133
AS3356Level 3 Parent, LLCTransitIPv4125
AS11537Internet2UnclassifiedIPv436
AS24247PacketFabric (Hong Kong) LimitedUnclassifiedIPv426
AS2764AAPT LimitedUnclassifiedIPv422
AS9002RETN LimitedUnclassifiedIPv413
AS24482SG.GSHostingIPv49
AS7575Australian Academic and Research Network (AARNet)EducationIPv47

All 32 adjacent →

Provenance

Where this comes from

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