Is Microsoft Azure down?

Impact Statement: Starting at 09:39 UTC on 29 May 2026, you have been identified as a subset of customers using Azure OpenAI service in multiple regions who may experience degraded request success where some requests returned errors or failed to complete. Current Status: We identified this issue through internal automated service monitoring after detecting a drop in call success rates. Our investigation indicates that the issue is linked to elevated server-side errors within a backend service layer in the affected region. We are actively investigating and working to determine the full scope and mitigation steps. The next update will be provided within 60 minutes, or sooner if there are significant developments.

Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region. Engineers are actively investigating the issue and working to restore network stability. Some requests may succeed upon retry as connectivity intermittently recovers. We are sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.

Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region, due to a power event. We are in process of recovering power and working to restore infrastructure in the region. We started seeing partial recovery and will be sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.

Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility in the region, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Current Status: We identified this issue through our automated monitoring after detecting elevated alerts related to network and infrastructure health in the West US 2 region. The issue was triggered by a power event in the datacenter, which impacted underlying infrastructure and led to increased latency and intermittent connectivity for select resources. We are aware of the impact and are actively investigating. Mitigation efforts are underway to restore affected network components across dependent services, including Storage and Compute. Customers may begin to see signs of recovery as these actions progress. The next update will be provided within 60 minutes, or sooner if there are significant developments.

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.

Impact statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss across multiple West US 2 datacenter facilities, resulting in impact to multiple Azure services. Datacenter power has been fully restored, and the majority of network and storage infrastructure has recovered. Infrastructure in Availability Zone 2 has recovered and is operating normally. Residual impact is now concentrated on a subset of infrastructure within Availability Zones 1 and 3, where two storage stamps are undergoing final recovery and validation. Customers with resources deployed exclusively in Availability Zone 2 should not be affected by the remaining recovery activities; however, those with dependencies in Availability Zones 1 or 3 may continue to experience intermittent connectivity, elevated latency, or resource unavailability. Currently affected Azure services include, but may not be limited to (recovery validation underway):Azure Functions, Azure Database for MySQL Flexible Server, Azure Database for PostgreSQL Flexible Server, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Azure Storage, Application Insights, Azure Monitor, and Azure Log Analytics.The following services have recovered and are operating normally:Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Azure Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Azure Cache for Redis, and Azure Synapse Analytics. Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. Because these events occurred across multiple facilities within the same timeframe, the resulting conditions exceeded the resiliency designed for this particular failure scenario. Datacenter utility power has been fully restored. HVAC systems have normalized, ambient temperatures have returned to expected operating ranges, and the majority of network and storage infrastructure has recovered successfully. While most services have returned to normal operation, a small subset of storage clusters and network devices did not recover cleanly and continue to limit full-service restoration. Some storage clusters remain partially unavailable or dependent on ongoing network recovery activities, and a limited number of network devices connecting compute resources to storage infrastructure remain impaired. As a result, some virtual machines are currently unable to access their underlying storage dependencies and may remain unavailable. Recovery efforts have transitioned from broad infrastructure restoration to targeted remediation of specific network devices, storage clusters, and isolated compute nodes. As these components are restored, validated, and returned to service, dependent workloads are recovering incrementally. Two storage stamps are currently completing final recovery and integrity validation activities, and services dependent on those stamps are expected to recover as this work is completed. Estimated Time to Resolution: With datacenter power restored and the majority of network and storage infrastructure recovered, remaining work is focused on two storage stamps completing final recovery and data integrity validation activities. Based on current progress, we estimate full-service restoration within approximately 2-3 hours. Individual services dependent on these stamps will recover progressively as validation activities are completed. Customer Guidance:Single-region workloads will recover automatically as infrastructure restoration activities are completed; no customer action is required.We recommend postponing new deployments into West US 2 until this incident is resolved and using alternate regions for urgent deployment needs.Logical availability zones assigned to customer subscriptions may map to different physical availability zones. Customers can use the Locations API to understand this mapping: https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations?HTTP#availabilityzonemappings. Next Update: We will provide our next status update within 60 minutes, or sooner if significant progress is made.