Azure outage history

Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services in the Sweden Central region experienced intermittent request failures and increased latency. Users attempting to submit requests faced intermittent errors and slower responses for several hours. The disruption began around 10:03 AM UTC and subsided around 3:58 PM UTC, according to Azure status updates. A backend service used to retrieve service information contributed to the issue, and a broad set of networking components including ExpressRoute Gateways and VPN Gateways entered degraded states during the incident.

Azure's Sweden Central region experienced a regional outage that disrupted the Azure OpenAI Service, Foundry Agent Service, and related Azure AI services and Foundry Models. Users attempting to run AI workloads or access deployments reported errors and degraded performance, with slow inferences and access failures focused in Sweden Central and nearby Europe. The disruption appears regional, with many reports from Sweden and neighboring countries while some global traffic observed slower responses as workloads rerouted.

Status updates show the issue being flagged as a warning at Sep 29, 2026 1:41 PM UTC for the Sweden Central components, roughly 40 minutes after StatusGator first detected the issue at Sep 29, 2026 1:01 PM UTC. The incident then escalated to a full outage at Sep 29, 2026 2:58 PM UTC and began recovering by Sep 29, 2026 6:58 PM UTC, with impacted components returning to up. The early warning signal ended at Sep 29, 2026 3:38 PM UTC. A noticeable volume of user reports during the afternoon UTC corroborated the extent of impact, signaling broad reach within the region.

Azure West US experienced a broad connectivity outage that disrupted networking, application delivery, database, and analytics services. West US users reported inability to reach resources, timeouts in portals and APIs, and degraded productivity across workloads. Core components affected included Application Gateway, ExpressRoute Gateways, VPN Gateway, Virtual WAN, API Management, AKS, and Azure Database for PostgreSQL, among others.

StatusGator's Early Warning Signal indicated the issue began before Azure acknowledged it, roughly 85 minutes earlier. The problem was first observable as DNS and gateway timeouts at 3:06 PM UTC (ending 5:51 PM UTC). Azure acknowledged the problem at 4:31 PM UTC. By 5:38 PM UTC a broad set of West US components were listed as down, marking the onset of a major outage affecting a wide swath of Azure services. Recovery progressed through the evening, with many key services returning to normal production状态 by 8:18 PM UTC.

User reports surged as the incident unfolded, describing timeouts, connectivity issues, and difficulty reaching resources across the West US region. Azure published follow-up status updates detailing restoration steps as individual services came back online, and the regional impact gradually receded with most critical services restored by the stated recovery time.

Azure experienced a broad degradation across many West US services beginning 3:43 PM UTC. The incident affected a wide range of components, including compute, storage, networking, databases, AI and related services, with many items listed as degraded on the Azure status page. The geographic impact was concentrated in the West US region, and users experienced widespread service disruption and degraded performance during the event.

Azure issued a series of official status updates as they investigated and mitigated the issue. The incident involved dozens of components and progressed through multiple status changes before recovery. In total, the provider issued 10 status updates over the course of the outage. The affected services gradually returned to normal, and by 5:53 AM UTC many were back to up, marking the likely end of the incident. The outage lasted roughly 14 hours and 10 minutes.

Azure West US experienced a brief degradation starting at 3:23 PM UTC, with many West US components entering a degraded state. The issue affected dozens of services across compute, networking, and data platforms, including AKS, App Gateway, Virtual Network, SQL Database, and DNS Private Zones, potentially causing slower responses and intermittent errors for regional users. The degradation was resolved after about 3:38 PM UTC with services returning to normal. The provider issued 2 status updates during the incident. User reports were limited, suggesting the impact did not affect a broad base of customers in practice. The incident was regional to West US and did not indicate a global outage.

The Azure status page indicated a degraded state beginning at 1:53 PM UTC in the West US region, with a broad set of services listed as degraded. The incident affected numerous components across compute, networking, databases, and platform services in West US, resulting in outages or degraded performance for affected workloads. Customer-reported symptoms included Astea app access issues observed in Carlisle, PA, illustrating real-world impact. The outage persisted for about 1 hour 15 minutes and the components recovered by 3:08 PM UTC. The West US region appears to be the primary geographic impact, with no evidence of global disruption. The provider issued a status transition from up to warn and back to up as services recovered.

The Azure West US region experienced a brief outage beginning at 9:28 AM UTC and resolved by 9:38 AM UTC. Seven components were affected: West US / Azure OpenAI Service, Azure Container Apps, Azure Kubernetes Service (AKS), West US / Azure Resource Manager, West US / Cosmos DB, West US / Service Bus, and West US / Storage Accounts. Users in the region may have experienced outages or degraded functionality across apps relying on these services. The Azure status page published two updates during the incident, at 9:28 AM UTC and 9:38 AM UTC, indicating the initial outage and later restoration. The incident was regional to West US.

Azure experienced a broad disruption starting on Feb 2, 2026 9:43 PM UTC that led to degraded performance and partial outages across numerous regions and services. The impact spanned compute, database, caching, AI, and management layers, with reported symptoms including failure to start Azure Virtual Desktop resources, DNS resolution issues, and blocked deployments. Affected components included East US Container Apps and AKS, Azure Database for PostgreSQL flexible servers, Azure Cache for Redis, API Management, Azure Synapse Analytics, Azure Service Fabric, and many other Azure services across regions worldwide, with reports coming from the United States, Brazil, India, Europe, and Asia, indicating a broad, multi-service disruption rather than a single service outage.

Azure issued multiple status updates to communicate degraded performance, partial outages, and subsequent recovery. The outage persisted for roughly 11 hours and 10 minutes, with full recovery across most services by around Feb 3, 2026 8:53 AM UTC, though some components began returning earlier and continued to roll back to up status over time.

Azure OpenAI Service in the Sweden Central region went offline at Jan 27, 2026 1:23 PM UTC and was restored by Jan 27, 2026 5:23 PM UTC, lasting about 4 hours. The outage blocked API access to OpenAI models, with users reporting HTTP 500 errors, timeouts, and degraded performance. While Azure’s status page listed the Sweden Central / Azure OpenAI Service as the affected component, user reports indicated broader symptoms including latency and failures reported from multiple regions. The incident began generating user reports around 12:15 PM UTC and saw activity ramping up into the early afternoon.

An outage in Azure West US 2 began at 18:53 UTC, affecting a broad set of services in the region, including Storage Accounts, Cosmos DB, Virtual Machines, and Service Bus, with Azure Database for PostgreSQL flexible servers also impacted. A subsequent status update noted Azure SQL Database was affected, and later updates indicated issues with the Network Infrastructure, Virtual Machine Scale Sets, and SQL Managed Instance. The outage disrupted storage, databases, and compute resources for roughly two hours, starting at 18:53 UTC and largely resolving by 21:03 UTC.

Azure’s status page published five updates during the incident, detailing the progression from degradation to recovery. User reports were submitted during the event, including a report from Kolkata, India, indicating some cross-regional visibility of the issue. By 21:03 UTC most services in the West US 2 region were restored and monitoring continued to ensure full stabilization.