bgpreport

Network · data from 2026-11-12

AS62715 CrashPlan Group LLC

Registry name: CRASHPLAN - CrashPlan, US · PeeringDB

17IPv4 routes 94.1% RPKI valid · 88.2% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS62715, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62715, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

149.5.7.0/24 No ROA Other IRR onlyALTDB 673 100% 67
162.222.47.0/24 Valid None 671 100% 68
162.222.43.0/24 Valid Nonecovered by 162.222.40.0/22 208 31% 58
216.9.198.0/24 Valid Other IRR onlyRADB 673 100% 67
216.9.197.0/24 Valid Other IRR onlyRADB 672 100% 66
68.65.192.0/24 Valid RIR databaseARIN 673 100% 67
162.222.44.0/24 Valid RIR databaseARIN 673 100% 67
67.222.252.0/24 Valid RIR databaseARIN 671 100% 69
67.222.255.0/24 Valid RIR databaseARIN 671 100% 69
68.65.193.0/24 Valid RIR databaseARIN 671 100% 68
68.65.194.0/24 Valid RIR databaseARIN 671 100% 68
68.65.196.0/24 Valid RIR databaseARIN 671 100% 69
68.65.197.0/24 Valid RIR databaseARIN 671 100% 69
68.65.198.0/24 Valid RIR databaseARIN 671 100% 69
162.222.40.0/22 Valid RIR databaseARIN 671 100% 68
162.222.45.0/24 Valid RIR databaseARIN 671 100% 69
162.222.46.0/24 Valid RIR databaseARIN 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS62715: AS-CRASHPLAN RS-CRASHPLAN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS62715 isn't in the set, or no route object for AS62715 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS62715 in itNot covered
AS-CRASHPLAN ARIN 1120 Yes 1
RS-CRASHPLAN A route-set, not an AS-SET; route-sets aren't expanded.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 11 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none149.5.7.0/24No ROA covers it. Add a ROA for AS62715, maxLength 24.673 of 673
Route object: RIR149.5.7.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
Route object: none162.222.47.0/24No route object for it. Add a route object with origin AS62715 in the RIR database for the space.671 of 673
Route object: none162.222.43.0/24No route object for it. A route object for 162.222.40.0/22 with origin AS62715 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62715 in the RIR database for the space.208 of 673
Route object: RIR216.9.198.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.9.197.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS62715 whose prefix no peer sees AS62715 announce. Many are kept on purpose (backup routes, space announced only in some places).

59.100.118.112/29RADBNo ROA
68.65.192.0/21RADBValid
68.65.199.0/24ARINValid
103.8.239.0/24ARIN, RADBValid
216.223.38.0/24NTTCOM, RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.