azureAzure incident history
A full searchable archive of Azure Service Health events and resolved outages.
Sourced live from the official Azure status page. How we verify.
Active now
0
Tracked incidents
21
Services affected
7
Avg resolution
6h 39m
Showing 1-10 of 21 incidents
Active - Multiple services experiencing connectivity issues in multiple regions
Starting at 20:30 UTC on 30 September 2026, customers using gateway services may be experiencing degraded or interrupted network connectivity. Customers may see gateways failing to load in the Azure Portal, and may also be experiencing failures or delays with network management operations across the following impacted services: ExpressRoute Gateways Azure Firewall Application Gateways / Web Application Firewall VPN Gateways Azure VMWare Solution (AVS) Current status: The vast majority of previously-impacted regions are showing signs of recovery, we are working to apply configuration changes that were successful in other regions to the remaining five regions: France Central, North Europe, Southeast Asia, UK South, and UK West. Our investigation has identified a correlation between the timing of this incident and infrastructure operating system servicing activity, which has since been paused. The underlying failure mechanism has not yet been confirmed, and we continue to investigate why network service instances became unhealthy and why recovery behavior differed across services. We continue to validate recovery - region by region, and service by service. We will provide additional information within the next 60 minutes, or sooner if events warrant.
Active - Multiple services experiencing connectivity issues in multiple regions
Starting at 20:30 UTC on 30 September 2026, customers using gateway services may be experiencing degraded or interrupted network connectivity. Customers may see gateways failing to load in the Azure Portal, and may also be experiencing failures or delays with network management operations across the following impacted services: ExpressRoute Gateways Azure Firewall Application Gateways / Web Application Firewall VPN Gateways Azure VMWare Solution (AVS) Current status: The vast majority of previously-impacted regions are showing signs of recovery, we are working to apply configuration changes that were successful in other regions to the remaining five regions: France Central, North Europe, Southeast Asia, UK South, and UK West. Our investigation has identified a correlation between the timing of this incident and infrastructure operating system servicing activity, which has since been paused. The underlying failure mechanism has not yet been confirmed, and we continue to investigate why network service instances became unhealthy and why recovery behavior differed across services. We continue to validate recovery - region by region, and service by service. We will provide additional information within the next 60 minutes, or sooner if events warrant.
Active - Azure ExpressRoute Gateway service impacting event in multiple Azure Regions
We are investigating an alert for Azure ExpressRoute Gateway in multiple Azure regions, also affecting dependent services. We will provide more information as it becomes available.
Active - Multiple services experiencing connectivity issues in multiple regions
Starting at 20:30 UTC on 30 September 2026, customers using gateway services may be experiencing degraded or interrupted network connectivity. Customers may see gateways failing to load in the Azure Portal, and may also be experiencing failures or delays with network management operations across the following impacted services: ExpressRoute Gateways Azure Firewall Application Gateways / Web Application Firewall VPN Gateways Azure VMWare Solution (AVS) Current status: The vast majority of previously-impacted regions are showing signs of recovery, we are working to apply configuration changes that were successful in other regions to the remaining five regions: France Central, North Europe, Southeast Asia, UK South, and UK West. Our investigation has identified a correlation between the timing of this incident and infrastructure operating system servicing activity, which has since been paused. The underlying failure mechanism has not yet been confirmed, and we continue to investigate why network service instances became unhealthy and why recovery behavior differed across services. We continue to validate recovery - region by region, and service by service. We will provide additional information within the next 60 minutes, or sooner if events warrant.
Multiple services experiencing connectivity issues in multiple regions
Multiple services experiencing connectivity issues in multiple regions. Resolved - see the official Azure Post Incident Review (Tracking ID 7Q30-010).
Intermittent request failures and increased latency across Azure OpenAI, Azure AI Foundry, and Cognitive Services
Impact Statement: Starting at 10:00 UTC on 29 September 2026, a subset of customers using OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services, in Sweden Central may experience intermittent request failures, increased latency, and HTTP 5XX error codes when submitting requests to affected models and APIs hosted in this region. Current Status: Currently we are monitoring improvements in the overall experience. Our investigation is focused on observed instability and dependency connectivity timeouts for backend services that are relied on. Multiple mitigation workstreams are underway, and we are closely monitoring service health to assess their effectiveness and determine the most effective path toward full recovery. The next update will be provided within 60 minutes, or sooner if significant developments occur.
Observing improvements - Intermittent request failures and increased latency across Azure OpenAI, Azure AI Foundry, and Cognitive Services
Impact Statement: Starting at 10:00 UTC on 29 September 2026, a subset of customers using OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services, in Sweden Central may experience intermittent request failures, increased latency, and HTTP 5XX error codes when submitting requests to affected models and APIs hosted in this region. Current Status: Currently we are monitoring improvements in the overall experience. Initial findings indicate that a backend service which is relied on to retrieve metadata information when managing requests for this region, was experiencing timeouts when reading from dependent database and caching layers. Additionally, some instances for this backend service became unhealthy and experienced restarts. As a result, requests that depend on these processes were delayed or failed intermittently. We have taken steps to further scale instances for the backend service, and reconfigured system processes as mitigation steps. Queued requests have been processed for a period of time to confirm improvements to overall service health. We are continuing to investigate the health of supporting platform infrastructure and system processes that may have impacted these requests and the backend service. The next update will be provided within 60 minutes, or as events warrant.
Azure OpenAI and Foundry agent Service intermittent request failures and increased latency
We are investigating an issue affecting Azure OpenAI and Foundry agent services in the Sweden Central region. Impacted customers may experience intermittent errors when making service requests. We are investigating the underlying issue and exploring mitigation options to restore normal service performance. Our analysis remains ongoing, and we are closely monitoring service health while continuing our investigation. We will provide additional information as it becomes available.
Observing improvements - Intermittent request failures and increased latency across Azure OpenAI, Azure AI Foundry, and Cognitive Services
Impact Statement: Starting at 10:00 UTC on 29 September 2026, a subset of customers using OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services, in Sweden Central may experience intermittent request failures, increased latency, and HTTP 5XX error codes when submitting requests to affected models and APIs hosted in this region. Current Status: Currently we are monitoring improvements in the overall experience. Initial findings indicate that a backend service which is relied on to retrieve metadata information when managing requests for this region, was experiencing timeouts when reading from dependent database and caching layers. Additionally, some instances for this backend service became unhealthy and experienced restarts. As a result, requests that depend on these processes were delayed or failed intermittently. We have taken steps to further scale instances for the backend service, and reconfigured system processes as mitigation steps. Queued requests have been processed for a period of time to confirm improvements to overall service health. We are continuing to investigate the health of supporting platform infrastructure and system processes that may have impacted these requests and the backend service. The next update will be provided within 60 minutes, or as events warrant.
Azure OpenAI and Foundry agent Service intermittent request failures and increased latency
We are investigating an issue affecting Azure OpenAI and Foundry agent services in the Sweden Central region. Impacted customers may experience intermittent errors when making service requests. We are investigating the underlying issue and exploring mitigation options to restore normal service performance. Our analysis remains ongoing, and we are closely monitoring service health while continuing our investigation. We will provide additional information as it becomes available.
Page 1 of 3