Active – Multi Service degradation in West US 2

Update timeline

1. monitoring May 29, 2026, 04:27 AM UTC

   Impact Statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss to our West US 2 datacenter facilities, resulting in a multi-service outage. Impact is currently region-wide, and we have not yet confirmed isolation to specific scale units or availability zones and are treating this as full-region impact until physical inspections confirm otherwise. Customers are experiencing service connectivity failures, timeouts, and elevated error rates across affected services. This includes an inability to deploy new resources or scale existing workloads, intermittent availability where some requests may succeed while others fail depending on which infrastructure nodes have recovered, and both data plane and control plane impact for services not yet restored. Affected Azure services include, but are not limited to:Azure Functions, Azure Database for MySQL Flexible Servers, Azure Database for PostgreSQL Flexible Server, Azure Databricks, Redis, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Storage, Application Insights, Azure Data Factory, Azure Monitor, and Azure Log Analytics Current Status: Severe thunderstorms resulted to a complete utility power loss to multiple datacenter buildings simultaneously. Our backup generators activated but were unable to fully compensate. The generator transfer switchover was only partially successful, with some generator sets failing to synchronize under the sudden full facility load and others experiencing thermal protection shutdowns as ambient temperatures rose due to simultaneous cooling system failures. This cascading combination of power instability and cooling loss exceeded our designed N+1 redundancy for this failure mode. We are still determining the full extent of mechanical vs. electrical failures in the generator systems. HVAC systems are being restarted in sequence; ambient temperatures are returning to safe ranges but have not fully normalized, so we are staged-powering equipment to avoid thermal re-trips. Network devices and storage arrays are being power-cycled and validated in sequence, with storage dependencies as the primary remaining bottleneck due to required manual intervention and data integrity verification. Where possible, traffic is being redirected to healthy nodes, and on-site teams are conducting physical hardware inspections to identify components requiring replacement. The following services have been confirmed restored and are operating normally:Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse Customer Guidance: • If you have resources in paired or alternate regions, consider failing over traffic away from West US 2 until we confirm full recovery. • Single-region workloads will recover automatically as infrastructure is restored — no customer action is required. • We recommend pausing new deployments to West US 2 until this incident is resolved; use alternate regions if urgent. • Monitor Azure Status (status.azure.com) and Service Health in the portal for real-time updates specific to your subscriptions. Next update: We will provide our next status update within 1 hour, or sooner, if events warrant.