CrashPlan Outage History

CrashPlan is up right now

CrashPlan had 5 outages in the last 2 years totaling 38h 22m of downtime — averaging 0.2 incidents per month.

There were 5 CrashPlan outages since July 1, 2025 totaling 38h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.crashplan.com

Minor April 15, 2026

CrashPlan Console Access Issue

Detected by Pingoru
Apr 15, 2026, 01:42 PM UTC
Resolved
Apr 16, 2026, 12:04 AM UTC
Duration
10h 22m
Affected: console.us1.crashplan.comconsole.us2.crashplan.comconsole.eu5.cpg.crashplan.comconsole.us2.crashplanpro.com (Small Business)
Timeline · 5 updates
  1. investigating Apr 15, 2026, 01:42 PM UTC

    We have detected an issue that is causing problems accessing the CrashPlan console and are investigating.

  2. identified Apr 15, 2026, 02:14 PM UTC

    The issue has been identified and a fix is being implemented. Further, on-device backups and restores are not affected.

  3. identified Apr 15, 2026, 07:58 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Apr 15, 2026, 09:11 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Apr 16, 2026, 12:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2026

US2 CrashPlan Cloud Storage Issue: dbc-sea

Detected by Pingoru
Feb 24, 2026, 11:18 PM UTC
Resolved
Feb 25, 2026, 04:49 PM UTC
Duration
17h 30m
Affected: console.us2.crashplan.com
Timeline · 3 updates
  1. identified Feb 24, 2026, 11:18 PM UTC

    We have identified an issue with storage server dbc-sea in our PROe Cloud, US destination that is affecting backup and restore for a small subset of users. We will update this incident periodically as we progress in its resolution.

  2. monitoring Feb 25, 2026, 02:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 25, 2026, 04:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 21, 2026

CrashPlan Console Unreachable

Detected by Pingoru
Jan 21, 2026, 09:18 PM UTC
Resolved
Jan 22, 2026, 12:47 AM UTC
Duration
3h 28m
Affected: console.us1.crashplan.comconsole.us2.crashplan.comconsole.eu5.cpg.crashplan.com
Timeline · 3 updates
  1. investigating Jan 21, 2026, 09:18 PM UTC

    We are experiencing with the CrashPlan Cloud Console being unreachable. We are investigating the issue and will provide an update shortly.

  2. identified Jan 21, 2026, 10:21 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jan 22, 2026, 12:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 17, 2025

CrashPlan Cloud Console is Down

Detected by Pingoru
Nov 17, 2025, 07:53 PM UTC
Resolved
Nov 17, 2025, 08:48 PM UTC
Duration
55m
Affected: console.us1.crashplan.comconsole.us2.crashplan.comconsole.eu5.cpg.crashplan.comconsole.us2.crashplanpro.com (Small Business)
Timeline · 5 updates
  1. investigating Nov 17, 2025, 07:53 PM UTC

    We are experiencing with the CrashPlan Cloud Console being Down. We are investigating the issue and will provide an update shortly.

  2. investigating Nov 17, 2025, 07:57 PM UTC

    We are continuing to investigate this issue.

  3. identified Nov 17, 2025, 08:24 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Nov 17, 2025, 08:47 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Nov 17, 2025, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 15, 2025

CrashPlan Cloud Storage Issue, USA East

Detected by Pingoru
Oct 15, 2025, 02:36 PM UTC
Resolved
Oct 15, 2025, 08:41 PM UTC
Duration
6h 5m
Affected: console.us1.crashplan.comconsole.us2.crashplan.comconsole.eu5.cpg.crashplan.com
Timeline · 5 updates
  1. investigating Oct 15, 2025, 02:36 PM UTC

    We are investigating an issue with storage nodes *db-iad, *eb-iad located in our USA East destination that is affecting backup and restore for a small subset of users. We will update this incident periodically as we progress in its resolution.

  2. identified Oct 15, 2025, 02:36 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Oct 15, 2025, 05:09 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Oct 15, 2025, 06:23 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Oct 15, 2025, 08:41 PM UTC

    This incident has been resolved.

Read the full incident report →