Druva Phoenix incident

Partial disruption with Phoenix Cloud for Azure workloads

Druva Phoenix experienced a minor incident on April 24, 2026 affecting Phoenix Cloud and Phoenix Cloud (East US (eastus)) and 1 more component, lasting 9d 23h. The incident has been resolved; the full update timeline is below.

Started: Apr 24, 2026, 04:04 PM UTC
Resolved: May 04, 2026, 03:07 PM UTC
Duration: 9d 23h
Detected by Pingoru: Apr 24, 2026, 04:04 PM UTC

Affected components

Phoenix CloudPhoenix Cloud (East US (eastus))Phoenix Cloud (West US (westus))Phoenix Cloud (UK South (uksouth))Phoenix Cloud (Germany West Central (germanywestcentral))Phoenix Cloud (Australia East (australiaeast))Phoenix Cloud (Northern Virginia (us-east-1))Phoenix Cloud (Northern California (us-west-1))Phoenix Cloud (Oregon (us-west-2))Phoenix Cloud (Sao Paulo (sa-east-1))

Update timeline

identified Apr 24, 2026, 04:04 PM UTC

We have identified a partial disruption affecting the onboarding of new Azure subscriptions for Phoenix Cloud due to ongoing API service slowness reported by Microsoft Azure. This issue may impact the onboarding of new Azure subscriptions. There is no impact to existing subscriptions, and backup and restore operations continue to function as expected. Our teams are actively working with high priority to mitigate this. We are closely monitoring the situation and will keep you updated on further progress. Please feel free to contact the Druva Support team at https://support.druva.com for any assistance. Druva Support.