Microsoft outage history and live incidents
Showing 2 of 2 incidents on Public
Resolved
Sep 30, 2026, 12:00 PM EDT
What Happened: Between 20:30 UTC on 30 September 2026 and 02:15 UTC on 01 October 2026, a subset of customers using gateway services in multiple regions experienced degraded or interrupted network connectivity.
Impact: ed region(s) within a previous communication has been corrected.
How Did We Respond: 20:30 UTC on 30 September 2026 – Customer
Impact: ed region(s) within a previous communication has been corrected.
How Did We Respond: 20:30 UTC on 30 September 2026 – Customer
AzureAzure
Incident community checkThis incident
Resolved
Sep 29, 2026, 12:00 PM EDT
What Happened: Between 10:03 UTC and 15:58 UTC on 29 September 2026, a platform issue resulted in
Impact: to Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services in the Sweden Central region.
What Went Wrong: d them to become unhealthy and restart repeatedly. An automated health check then triggered additional restarts, further reducing the number of healthy instances available to process requests. As a result, requests that depended on this service were delayed or failed intermittently. We have identified that an internal system process generated an increase in the overall amount of requests for the backend service which reached thresholds when calling the aforementioned database and caching layer.
How Did We Respond: 10:03 UTC on 29 September 2026 – Initial
Impact: to Azure OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services in the Sweden Central region.
What Went Wrong: d them to become unhealthy and restart repeatedly. An automated health check then triggered additional restarts, further reducing the number of healthy instances available to process requests. As a result, requests that depended on this service were delayed or failed intermittently. We have identified that an internal system process generated an increase in the overall amount of requests for the backend service which reached thresholds when calling the aforementioned database and caching layer.
How Did We Respond: 10:03 UTC on 29 September 2026 – Initial
AzureAzure
Incident community checkThis incident
2 incidents visible (ongoing and monitoring). A free account unlocks resolved history and filters.