Clumio Outage History

Clumio is up right now

Clumio had 8 outages in the last 2 years totaling 91h 45m of downtime — averaging 0.3 incidents per month.

There were 8 Clumio outages since May 29, 2024 totaling 91h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.clumio.com

Minor January 9, 2026

RDS backup failures

Detected by Pingoru
Jan 09, 2026, 12:30 PM UTC
Resolved
Jan 09, 2026, 05:57 PM UTC
Duration
5h 26m
Affected: AWS RDSAWS RDSAWS RDS
Timeline · 6 updates
  1. investigating Jan 09, 2026, 02:17 PM UTC

    We are investigating an issue where backups for the RDS resources are failing. Our team is treating this with high priority and will provide updates as more information becomes available. The impact is limited to RDS resources; backups for other data sources are functioning normally.

  2. identified Jan 09, 2026, 02:22 PM UTC

    We have identified the issue and are actively working to implement a fix.

  3. identified Jan 09, 2026, 02:57 PM UTC

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

  4. monitoring Jan 09, 2026, 03:23 PM UTC

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

  5. monitoring Jan 09, 2026, 05:39 PM UTC

    We are seeing recovery across the RDS backups. We will continue to update the status

  6. resolved Jan 09, 2026, 05:57 PM UTC

    The issue was fully resolved by 16:30 UTC, and RDS backups are now functioning normally. A detailed Root Cause Analysis (RCA) will be shared through the appropriate channels once finalized.

Read the full incident report →

Major October 20, 2025

Service Provider (AWS) Outage in US-EAST-1 region impacting backups and restores across all datasources in that region

Detected by Pingoru
Oct 20, 2025, 10:01 AM UTC
Resolved
Oct 20, 2025, 11:01 PM UTC
Duration
13h
Affected: AWS EC2AWS EC2AWS EBSAWS EBSAWS S3AWS S3AWS RDSAWS RDSAWS DynamoDBAWS DynamoDBAWS MS SQL on EC2AWS MS SQL on EC2M365 ExchangeM365 ExchangeM365 OneDriveM365 OneDriveM365 SharePointM365 SharePoint
Timeline · 6 updates
  1. investigating Oct 20, 2025, 10:01 AM UTC

    Since October 20th at 12:11 AM PDT, our service provider, AWS, has been experiencing an outage in the us-east-1 region. As a result, backup and restore operations for all data sources located in this region are currently impacted. Our team is actively investigating the backup failures observed across these data sources, which appear to be caused by the underlying service provider issue. We are closely monitoring the situation and will provide updates as more information becomes available or once services are restored.

  2. investigating Oct 20, 2025, 10:05 AM UTC

    We are continuing to investigate this issue.

  3. identified Oct 20, 2025, 10:09 AM UTC

    The issue has been identified at the service provider end.

  4. monitoring Oct 20, 2025, 12:25 PM UTC

    The service provider has mitigated the core issue affecting the us-east-1 region. However, a few services are still experiencing residual impact. We are actively monitoring backup tasks on our end and have observed encouraging signs of recovery. Our team continues to closely track the status of these tasks.

  5. monitoring Oct 20, 2025, 09:06 PM UTC

    We are tracking the backup tasks and we see signs towards full recovery. We estimate the backup tasks should fully recover by 22:00 UTC

  6. resolved Oct 20, 2025, 11:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 1, 2025

US1 (portal.clumio.com) Stuck backups due to degraded performance

Detected by Pingoru
Aug 01, 2025, 08:02 PM UTC
Resolved
Aug 02, 2025, 04:11 PM UTC
Duration
20h 8m
Affected: M365 ExchangeM365 ExchangeM365 OneDriveM365 OneDriveM365 SharePointM365 SharePoint
Timeline · 4 updates
  1. investigating Aug 01, 2025, 08:02 PM UTC

    We are currently investigating the issue. Customer Impact : Microsoft 365 backups are in a queued state and not completing in the platform

  2. identified Aug 01, 2025, 09:57 PM UTC

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

  3. monitoring Aug 02, 2025, 01:22 AM UTC

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

  4. resolved Aug 02, 2025, 04:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 6, 2025

US1 (portal.clumio.com) Backup and Restore failures due to degraded performance

Detected by Pingoru
Jun 06, 2025, 12:00 PM UTC
Resolved
Jun 07, 2025, 06:38 AM UTC
Duration
18h 38m
Affected: AWS EC2AWS EBSAWS S3AWS RDSAWS DynamoDBAWS MS SQL on EC2M365 ExchangeM365 OneDriveM365 SharePoint
Timeline · 6 updates
  1. investigating Jun 06, 2025, 12:00 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 06, 2025, 12:41 PM UTC

    The issue has been identified, and we are currently working on a fix.

  3. identified Jun 06, 2025, 04:38 PM UTC

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

  4. monitoring Jun 06, 2025, 05:53 PM UTC

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

  5. monitoring Jun 06, 2025, 09:14 PM UTC

    We are still in the process of recovering from the recent issue and are working diligently to stabilize services and ensure operations are fully restored.

  6. resolved Jun 07, 2025, 06:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 12, 2024

US1 (portal.clumio.com) Backup failures due to degraded performance

Detected by Pingoru
Sep 12, 2024, 09:58 PM UTC
Resolved
Sep 13, 2024, 03:41 PM UTC
Duration
17h 42m
Affected: AWS EC2AWS EBSAWS S3AWS RDSAWS DynamoDBAWS MS SQL on EC2M365 ExchangeM365 SharePoint
Timeline · 4 updates
  1. investigating Sep 12, 2024, 09:58 PM UTC

    We are currently investigating this issue.

  2. identified Sep 12, 2024, 10:11 PM UTC

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

  3. monitoring Sep 12, 2024, 11:57 PM UTC

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

  4. resolved Sep 13, 2024, 03:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 29, 2024

Backup failures across data sources due to underlying Service Provider issues

Detected by Pingoru
Aug 29, 2024, 09:28 AM UTC
Resolved
Aug 29, 2024, 11:09 AM UTC
Duration
1h 40m
Affected: AWS EC2AWS EBSAWS S3AWS RDSAWS DynamoDBAWS MS SQL on EC2M365 ExchangeM365 OneDriveM365 SharePoint
Timeline · 4 updates
  1. investigating Aug 29, 2024, 09:28 AM UTC

    We are currently investigating backup failures observed across data sources due to an underlying service provider issue.

  2. identified Aug 29, 2024, 10:06 AM UTC

    The issue has been identified at the service provider end.

  3. monitoring Aug 29, 2024, 10:33 AM UTC

    The underlying service provider issue is now resolved. We are currently monitoring the status of the tasks.

  4. resolved Aug 29, 2024, 11:09 AM UTC

    The incident is now resolved and backup tasks are completing successfully.

Read the full incident report →

Minor July 24, 2024

Performance degradation in MSSQL on EC2 Database Backups

Detected by Pingoru
Jul 24, 2024, 02:11 AM UTC
Resolved
Jul 24, 2024, 09:19 AM UTC
Duration
7h 7m
Affected: AWS MS SQL on EC2AWS MS SQL on EC2
Timeline · 4 updates
  1. investigating Jul 24, 2024, 02:11 AM UTC

    Currently investigating a performance degradation specific to MSSQL on EC2 Database backups. Log backups and restore operations are not impacted at this time.

  2. identified Jul 24, 2024, 06:45 AM UTC

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

  3. monitoring Jul 24, 2024, 08:13 AM UTC

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

  4. resolved Jul 24, 2024, 09:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 29, 2024

Investigating Performance degradation in RDS Backups

Detected by Pingoru
Jun 29, 2024, 12:48 AM UTC
Resolved
Jun 29, 2024, 08:49 AM UTC
Duration
8h 1m
Affected: AWS RDSAWS RDS
Timeline · 5 updates
  1. investigating Jun 29, 2024, 12:48 AM UTC

    We are currently investigating this issue.

  2. identified Jun 29, 2024, 01:50 AM UTC

    Performance degradation has been identified and we are working on resolving the issue.

  3. monitoring Jun 29, 2024, 04:24 AM UTC

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

  4. monitoring Jun 29, 2024, 06:54 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 29, 2024, 08:49 AM UTC

    This incident has been resolved.

Read the full incident report →