Commvault had 15 outages in the last 2 years totaling 4115h 0m of downtime — averaging 0.6 incidents per month.
There were 15 Commvault outages since October 3, 2025 totaling 4115h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating a reported issue affecting authentication through Okta login. Our team is actively working to determine the scope and cause of the issue. We will provide additional updates as more information becomes available.
This incident has been resolved.
We are aware of an issue affecting Microsoft OneDrive backup operations, resulting in an increased number of failed backup items for some customers. Our engineering team is actively investigating the issue and working to determine the root cause. We will continue to provide updates as we learn more.
This incident has been resolved.
We are investigating an issue affecting Command Center login. Some customers may experience slower-than-normal login times when accessing the service. Our team is actively working to identify the cause and restore normal performance. We will provide an update as more information becomes available.
We have identified the cause of the Command Center performance issues and are actively working to implement corrective measures. Customers may continue to experience intermittent slowness while remediation efforts are underway. We will provide additional updates as progress is made toward full service restoration.
This incident has been resolved.
We have identified the issue affecting backup job processing and implemented corrective actions. Backup jobs are now processing as expected, and we are actively monitoring the environment to confirm continued stability. Some customers may still observe delayed completion for jobs that were previously queued. We will provide a final update once we have confirmed full recovery.
This incident has been resolved.
We have identified and resolved an issue that caused certain backup jobs relying on customer network gateways to enter a pending or failed state due to incorrect network rule configurations. The necessary network rule updates have been applied, and affected backup jobs should now resume normal operation and complete successfully. Our Site Reliability Engineering (SRE) team is actively monitoring all impacted backup activity to ensure continued stability and successful job completion. At this time, service has been restored, and we will continue to closely observe the environment. We appreciate your patience and understanding as we work to ensure a reliable backup experience.
This incident has been resolved.
We are currently experiencing degraded backup performance affecting a subset of backup jobs. As a result, some backups may take longer than normal to complete. Our team is actively working with engineering to identify the root cause and restore normal performance as quickly as possible. We will provide another update as soon as more information becomes available. We apologize for any inconvenience and appreciate your patience.
Backup performance has returned to normal, and services are operating as expected. The issue affecting a subset of backup jobs has been resolved. Backup processing is performing within expected parameters, and previously delayed jobs have completed or are progressing normally. We will continue to monitor the environment closely.
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.
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.