Azure Outage History

Azure West Europe experienced a degraded state affecting eight components in the region, including Azure Kubernetes Service (AKS), Storage Accounts, Virtual Machines, VM Scale Sets, Azure Database for MySQL, Azure Database for PostgreSQL, Service Bus, and Azure Databricks. Users likely faced intermittent access or performance issues across affected resources during the incident.

The outage began at Nov 5, 2025 8:03 PM UTC and was resolved by Nov 6, 2025 2:43 AM UTC, lasting roughly 6 hours and 40 minutes. The provider issued 2 status updates during the incident, outlining the degradation and recovery.

Azure Australia East experienced a brief degraded performance across multiple services, including Azure Databricks, Virtual Machines, Storage Accounts, Azure Backup, and Azure Synapse Analytics. The issue began at 7:13 PM UTC and was resolved by 8:48 PM UTC, lasting about 1 hour and 35 minutes. The provider posted two status updates during the incident, noting the degraded state and later restoration of full service. The impact was regional to Australia East, with affected components spanning five services; no indication of global disruption was reported.

The Azure outage began at 2025-10-29T16:38:00Z, impacting Network Infrastructure across a wide range of regions and Azure Front Door. Users worldwide experienced widespread connectivity issues, including failed API requests, sign-in problems, and degraded or unavailable web apps. A large volume of user reports indicated broad impact to deployments, APIs, and dashboards. The incident lasted about 7 hours and 55 minutes, with components gradually returning to service as recovery progressed. The provider issued six official status updates detailing the progression of restoration and component reactivation.

Azure experienced a global degradation affecting the Azure Portal and identity/authentication services such as Entra ID and Intune. Users from multiple regions reported sign-in failures, portal load issues, and error messages, indicating broad impact on access and management of resources. The outage began at Oct 9, 2025 9:13 PM UTC and was resolved by Oct 10, 2025 12:43 AM UTC, lasting about 3 hours and 30 minutes. The Azure status page issued two updates during the incident, first noting a degraded state and later confirming recovery as services returned to normal.

The incident began at 2025-10-09T10:03:00Z when Azure Front Door and the accompanying Network Infrastructure entered a degraded state. The disruption affected a wide range of regions and caused slow routing, intermittent connectivity, and authentication problems for users trying to access applications and provision resources. Reports from Europe, North America, Asia-Pacific, the Middle East, and Africa indicated widespread symptoms such as slow responses, timeouts, and errors, with the impact lasting for several hours as mitigations were applied and services were gradually brought back online. The outage persisted for roughly 6 hours and 55 minutes, until most affected components recovered.

Azure published multiple status updates throughout the incident, documenting the progression from degraded performance to partial recovery. By around 2025-10-09T16:58:00Z, the majority of regions and services had returned to normal, though recovery in some areas occurred in a phased manner. User reports reflected broad impact across many geographies, including authentication failures, connectivity issues, and difficulties withFront Door-related traffic and resource provisioning.

Azure Switzerland North experienced broad service degradation beginning at 1:08 AM UTC, with a wide range of services entering degraded states. Affected components included Cosmos DB, Azure Database for PostgreSQL flexible servers, Azure Databricks, App Service, Azure Data Explorer, Virtual Machine Scale Sets, AKS, Storage Accounts, and Virtual Machines, among others. The incident impacted customers relying on these services in the region, causing slower performance and intermittent access in affected workloads.

Azure's Switzerland North status page posted phased updates as services moved through degrade (warn) and began recovery. By 5:03 AM UTC several key services had returned to normal, and full restoration across the listed components was reported by 9:13 AM UTC.

The outage lasted roughly 8 hours and 5 minutes, with all listed components restored by 9:13 AM UTC.

Azure East US 2 experienced a brief degraded state starting at Sep 10, 2025 5:18 PM UTC, with seven East US 2 components listed as degraded: VM Scale Sets, Virtual Machines, Azure Databricks, Azure Synapse Analytics, Azure Data Factory, Azure Backup, and Azure Kubernetes Service. The degradation affected users in the East US 2 region, with a report noting Azure Virtual Desktop issues in East US 2 around 6:37 PM UTC. The incident concluded when these components returned to the normal state by Sep 10, 2025 7:53 PM UTC, lasting roughly 2 hours and 35 minutes. Azure issued four status updates during the incident to communicate progression.

Azure reported degraded networking across dozens of regions beginning at 7:28 PM UTC, with Network Infrastructure components shown as degraded in multiple regions. End users may have experienced intermittent connectivity and degraded performance across Azure services relying on network connectivity. The degraded state lasted about 3 hours and 10 minutes and was resolved by 10:38 PM UTC. The incident affected dozens of regional Network Infrastructure components across Europe, Asia, the Middle East, and the Americas, indicating a global networking issue. Azure issued 3 status updates during the incident, detailing affected regions and remediation progress as connectivity was restored.

Azure's East US Network Infrastructure experienced an outage beginning at 1:08 AM UTC. The incident progressed to a degraded state at 2:08 AM UTC and was fully recovered by 7:13 AM UTC, for a total duration of about 6 hours and 5 minutes. Azure issued three status updates during the incident to communicate progression.

Impact was regional to the East US, with connectivity and performance issues likely affecting services relying on that region. No root cause details were published in the updates.

Two Azure regions, Canada East and Canada Central, experienced a regional network infrastructure degradation starting at 6:58 PM UTC. Canada Central services began recovering by 8:03 PM UTC and Canada East by 8:08 PM UTC, with full restoration by the end of the window. The outage lasted about 1 hour and 10 minutes and affected workloads relying on those networks.

Azure published 3 status updates during the incident to communicate progression and recovery. User reports from the affected regions described connectivity issues consistent with a regional outage, while other regions remained unaffected.