Skip to main content

AS62715

CRASHPLAN

CrashPlan

Registry

Authoritative registration data

AS number
62715
Name
CRASHPLAN
Organisation
CrashPlan
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

17

IPv6 prefixes

0

Total announced

17

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS62715
162.222.40.0/22 IPv4 /22 not checked
149.5.7.0/24 IPv4 /24 not checked
162.222.42.0/24 IPv4 /24 not checked
162.222.43.0/24 IPv4 /24 not checked
162.222.44.0/24 IPv4 /24 not checked
162.222.45.0/24 IPv4 /24 not checked
162.222.46.0/24 IPv4 /24 not checked
216.9.197.0/24 IPv4 /24 not checked
216.9.198.0/24 IPv4 /24 not checked
67.222.252.0/24 IPv4 /24 not checked
67.222.255.0/24 IPv4 /24 not checked
68.65.192.0/24 IPv4 /24 not checked
68.65.193.0/24 IPv4 /24 not checked
68.65.194.0/24 IPv4 /24 not checked
68.65.196.0/24 IPv4 /24 not checked
68.65.197.0/24 IPv4 /24 not checked
68.65.198.0/24 IPv4 /24 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS62715
Address families
AMS-IX 10,000 Mbps IPv4 · IPv6
Equinix Ashburn 10,000 Mbps IPv4 · IPv6
Equinix Singapore 10,000 Mbps IPv4 · IPv6
Equinix Sydney 10,000 Mbps IPv4 · IPv6
SIX Seattle (Jumbo): MTU 9000 20,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 20,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS62715 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

52 networks seen before AS62715 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS62715 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

56 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.