Azure Outage History

Azure reported a broad degradation across a wide set of services and regions beginning at 7:53 PM UTC. The status page showed many components in a degraded state, including compute, networking, and data services such as Virtual Machine Scale Sets, App Service, Azure Front Door, Event Hubs, Service Bus, and related services. Users likely experienced intermittent access, slow responses, or partial outages across affected areas as the incident unfolded.

The incident progressed with several updates from Azure, moving affected services toward recovery over the next hour. By 9:23 PM UTC the majority of services had returned to normal, marking a roughly 1 hour and 30 minute window of degraded performance. The provider issued multiple official updates during the event as services recovered and transitioned back to fully available.

Azure East US 2 experienced degraded performance impacting Virtual Machines and Virtual Machine Scale Sets. The incident started at 5:03 AM UTC when East US 2 / Virtual Machines entered a degraded state, with East US 2 / Virtual Machine Scale Sets following at 5:08 AM UTC. The service was degraded for about 1 hour 40 minutes and was fully restored by 6:43 AM UTC. Users in this region may have observed slower VM operations or intermittent provisioning issues. The Azure status page documented the progression with three status updates during the incident.

Azure's East US2 region experienced partial degradation across multiple services due to a regional networking issue. The impact affected compute, containers, databases, and analytics, with users reporting intermittent connectivity, provisioning failures, and degraded performance. Official updates noted partial service impact starting as early as Jan 8, 2025 10:00 PM UTC and expanding to additional components over the next hours. The issue affected dozens of East US2 services, including Virtual Machines, Azure Databricks, Azure Synapse Analytics, AKS, Container Apps, Functions, App Service, Container Instances, PostgreSQL flexible servers, and more. Azure posted numerous updates and implemented mitigation steps such as traffic rerouting as they investigated the root cause.

Restoration progressed over the next days, with the Network Infrastructure component returning to normal around Jan 11, 2025 6:13 AM UTC and other services gradually coming back online. The incident lasted roughly three days in East US2, with widespread but region-limited impact across many services in the region. User reports from multiple locations (including the United States, Brazil, Norway, Albania, and Malaysia) described container provisioning delays, connectivity issues, and slower access to Azure analytics and data services in East US2. Azure's status page posted ongoing updates documenting mitigation efforts and service recoveries throughout the incident.