Druva Phoenix incident

Degraded performance with Phoenix Cloud me-central-1

Druva Phoenix is currently experiencing a major incident affecting Phoenix Cloud and Phoenix Cloud (UAE (me-central-1)), which began 108d ago. The vendor's full update timeline is below.

Started
Mar 01, 2026, 04:08 PM UTC
Resolved
Ongoing
Duration
● 108d 10h
Detected by Pingoru
Mar 01, 2026, 04:08 PM UTC

Affected components

Phoenix CloudPhoenix Cloud (UAE (me-central-1))

Update timeline

  1. identified Mar 01, 2026, 04:08 PM UTC

    We have identified degraded performance with the Backup and Restore services of Phoenix Cloud due to an ongoing service outage reported by AWS in the ME-CENTRAL-1 region. As a result of this AWS platform issue, there may be a potential impact on Backup and Restore operations. Teams are actively working on a priority to mitigate the outage. We are closely monitoring the situation and will keep you updated on the progress. Please feel free to contact the Druva Support team at https://support.druva.com for any assistance. Druva Support

  2. identified Mar 02, 2026, 07:25 AM UTC

    AWS services in the ME-CENTRAL-1 region are recovering; however, due to this outage, you may experience intermittent Backup and Restore failures. We are actively monitoring the situation and will continue to provide updates until full stability is confirmed. Please feel free to contact the Druva support team at https://support.druva.com. Druva Support

  3. identified Mar 03, 2026, 05:52 AM UTC

    Update: Backup-Restore jobs are impacted for me-central-1 AWS Region. We are actively monitoring the situation and will continue to provide updates until full stability is confirmed. Please feel free to contact the Druva support team at https://support.druva.com. Druva Support

  4. identified Mar 06, 2026, 09:03 PM UTC

    We are continuing to address the impact on Backup-Restore jobs within the me-central-1 AWS region. Our engineering team is collaborating with AWS to achieve a complete recovery of the affected regional services. We are observing preliminary signs of stabilization, however we are taking a cautious approach to ensure data integrity and a full restoration. Druva Support

  5. identified Mar 09, 2026, 08:32 PM UTC

    We are continuing to address the impact on Backup-Restore jobs within the me-central-1 AWS region. Our engineering team is collaborating with AWS to achieve a complete recovery of the affected regional services. We are observing preliminary signs of stabilization, however we are taking a cautious approach to ensure data integrity and a full restoration. We remain committed to transparency and will provide further updates as soon as actionable information becomes available from AWS. Please feel free to contact the Druva support team at support.druva.com. Druva Support

  6. identified May 25, 2026, 04:44 PM UTC

    While this situation continues, you must reconfigure your backups to a different region. To provision a new storage location and reconfigure your backups, reach out to the Support team. Our team will provide any additional assistance needed during the temporary relocation. Please feel free to contact the Druva support team at support.druva.com. Druva Support