Rubrik incident

Microsoft 365 Protection Experiencing Degraded Availability

Major Resolved View vendor source →

Rubrik experienced a major incident on January 31, 2023, lasting 5d 4h. The incident has been resolved; the full update timeline is below.

Started
Jan 31, 2023, 03:03 PM UTC
Resolved
Feb 05, 2023, 08:00 PM UTC
Duration
5d 4h
Detected by Pingoru
Jan 31, 2023, 03:03 PM UTC

Update timeline

  1. investigating Jan 31, 2023, 03:03 PM UTC

    We are noticing an issue with Polaris Microsoft 365 protection in US-2 and EU-1 regions Symptoms: Some backups might fail and objects may briefly be out of compliance for M365 Incident Start Time: 01/31/2023 06:30 AM UTC Workaround: None at this time. Engineering is actively investigating to resolve this issue.

  2. identified Jan 31, 2023, 08:13 PM UTC

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

  3. monitoring Feb 01, 2023, 01:58 PM UTC

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

  4. monitoring Feb 02, 2023, 08:17 AM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Feb 02, 2023, 05:47 PM UTC

    A fix has been implemented and we are monitoring the results M365 backups are progressing now It may take a while to complete the pending backups

  6. investigating Feb 02, 2023, 06:18 PM UTC

    We are observing M365 Exchange backups are taking longer than usual which might continue to cause a drop in compliance for Exchange. Compliance for M365 OneDrive, SharePoint and Teams was briefly impacted on 2023/01/31 and should have recovered as of today. We are working on further mitigation to bring the service back to a normal operating state.

  7. monitoring Feb 03, 2023, 09:46 AM UTC

    A fix has been implemented for long-running exchange backups/compliance issues and we are monitoring the results It may take a while to achieve the expected compliance levels for M365 Exchange backups Compliance for M365 OneDrive, SharePoint and Teams was briefly impacted on 2023/01/31 and should have recovered as of today.

  8. resolved Feb 05, 2023, 08:00 PM UTC

    This incident has been resolved.