Commvault had 15 outages in the last 2 years totaling 3710h 7m of downtime — averaging 0.6 incidents per month.
There were 15 Commvault outages since July 30, 2025 totaling 3710h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have identified a performance degradation impacting Command Center logins. Our engineering teams are actively engaged and working to determine the underlying cause. We will continue to monitor the situation closely and will provide updates as more information becomes available.
This incident has been resolved.
We are currently addressing an issue affecting some AWS VM backup jobs. Impacted jobs may fail during processing due to a signature validation error encountered while accessing data through the AWS API. We have identified the root cause and are actively deploying a fix to the affected systems. We will provide another update once the deployment is complete and service has been fully restored. We apologize for any inconvenience and appreciate your patience as we work to resolve this issue.
Commvault Engineering worked closely with AWS Support to resolve this issue and restore normal backup operations. AWS identified the root cause and confirmed that the requirement change responsible for the errors has been rolled back. Backups are now completing successfully, and we are closely monitoring backup jobs to ensure continued stability and successful execution.
Issue has been mitigated.
Some customers may be experiencing degraded backup performance, which could impact backup SLAs. Our engineering team is actively investigating and taking steps to restore full performance.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are tracking reports of "Forbidden" errors during Office 365 backups caused by a recent Microsoft Exchange Online behavior change. This affects specific tenants and mailboxes using EWS. Exchange Online jobs may show User Mailboxes reporting a Mailbox Status of: Throttling from Exchange, Failed to process mailbox due to [The request failed. Forbidden] Resolution: Additional information and steps to resolve this can be found here, https://support.commvault.com/Article/Details/KA-191556
Issue has been mitigated.
We are currently experiencing intermittent issues originating from Microsoft’s side that are impacting certain Exchange mailboxes. Affected users may encounter the following error message in their mailbox status: “No valid Azure app found. Please run check readiness.” Our team is actively engaging with Microsoft to investigate and resolve the matter. We will provide the next update as soon as additional information becomes available. We appreciate your understanding and cooperation during this time.
This incident has been resolved.
We are currently experiencing intermittent disruptions with our AWS dataplane, which may affect backup performance. Our team is actively working with AWS to resolve the issue as quickly as possible. We’ll continue to monitor the situation and share updates as soon as they are available. Thank you for your patience and understanding.
This incident has been resolved.
We are currently experiencing an outage impacting several of our services. This is due to a widespread Amazon Web Services (AWS) infrastructure issue in the US-East-1 region. Status: We are actively monitoring the AWS status and will provide an update as soon as the upstream issue is resolved or we have an estimated time of recovery. Thank you for your patience.
This incident has been resolved.
We have identified an issue impacting Office 365 Exchange clients that are configured for archive mailbox only backups. The issue is not present if primary and mailboxes are backed up together in a single client. A fix is being deployed, and we expect service to be fully restored soon.
We are aware of Command Center login issues, where customers are unable to access the command center. We are working on this actively to fix the issue. Inconvenience caused is regretted.
The issue has been resolved and CC logins are now working as expected.
This incident has been resolved
We are currently experiencing an issue with the display of the usage summary for subscriptions. Our team is actively investigating the root cause and working towards a resolution as quickly as possible. We appreciate your patience and will provide updates as soon as more information becomes available.
Issue has been resolved
This incident has been resolved.
We are currently experiencing delays in VM Management service operations due to a current issue on Microsoft’s Azure infrastructure. This impacts key operations which affects our backup infrastructure auto-scaling used for Office 365 backups. As a result, performance for Office 365 backups may be degraded. We are actively working with Microsoft and will share updates as they become available. Thank you for your patience and understanding.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently performing maintenance on our systems. During this time, you may notice that Office 365 backups are temporarily paused or delayed. This is a temporary measure, and all services are expected to return to normal operation shortly. We will update this page once the maintenance is complete and backups have resumed. Thank you for your patience.
This incident has been resolved.
We are currently investigating an issue impacting a subset of Azure File agent backup jobs. Specifically, this affects agents configured with multiple Azure subscriptions. Our engineering team has identified the root cause and is actively working on deploying a corrective fix. We will update as soon as the fix is in place and confirm when normal operations have resumed. We appreciate your patience and apologize for any inconvenience this may cause.
A fix has been implemented and the jobs are running fine. We are continuing to monitor them.
This incident has been resolved.
We’re currently investigating an issue affecting scheduled reports. Real-time reporting remains fully operational, and you can continue to generate reports using current data without interruption. We’ll provide updates as soon as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating a performance degradation that may be impacting Exchange backup operations. Our operations team is actively working to restore optimal performance. We will provide updates as more information becomes available.
This incident has been resolved.