Is Commvault down?

Last checked 3m ago
Current status
Commvault is up

No incidents right now.

Official status page: https://m3-status.metallic.io · Polled every 5 minutes · 34 components tracked

Commvault is operational right now. Last checked 3m ago; the most recent incident resolved 6h ago.

Real-time Commvault status, recent outages, and incident history — pulled directly from Commvault's official status page at https://m3-status.metallic.io every 5 minutes. Pingoru tracks 34 Commvault services and has captured 16 incidents in the last 90 days (99.36% uptime). Get email, Slack, Discord, or webhook alerts the moment Commvault reports a new incident — free for 5 monitors, no credit card.

Users who monitor Commvault also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
Commvault uptime 99.36% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Active incident 1

  1. Ongoing ● 37d 2h
    Started Jun 22, 2026, 12:38 PM UTC
    Timeline · 1 update
    • identified · Jun 22, 2026, 12:38 PM UTC

      Description: 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

    Latest: Description: 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…

Recent outages & incidents

Past 90 days
  1. Resolved 5d 1h
    Started Jul 09, 2026, 01:43 PM UTC · Resolved Jul 14, 2026, 03:40 PM UTC
    Canada CentralEast US2East USFrance CentralWest USCanada CentralNorth Central USEast US2France Central
    Timeline · 2 updates
    • investigating · Jul 09, 2026, 01:43 PM UTC

      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.

    • resolved · Jul 14, 2026, 03:40 PM UTC

      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.

    Latest: 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 wi…

  2. Resolved 21d 22h
    Started Jun 17, 2026, 02:54 PM UTC · Resolved Jul 09, 2026, 01:24 PM UTC
    East US2
    Timeline · 2 updates
    • identified · Jun 17, 2026, 02:54 PM UTC

      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.

    • resolved · Jul 09, 2026, 01:24 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 6d 18h
    Started Jun 11, 2026, 01:33 PM UTC · Resolved Jun 18, 2026, 08:25 AM UTC
    Timeline · 3 updates
    • identified · Jun 11, 2026, 01:33 PM UTC

      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.

    • monitoring · Jun 12, 2026, 03:43 AM UTC

      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.

    • resolved · Jun 18, 2026, 08:25 AM UTC

      Issue has been mitigated.

    Latest: Issue has been mitigated.

See the full Commvault outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Commvault outage history →

Or sign up free to get alerts when Commvault breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 4 incidents View full outage history →