RewindexOutage eventsOct 29, 2025
Azure outage, Oct 29, 2025
23 vendors posted 22 incidents between 16:00 and 22:00 UTC, against about 21 incidents from 17 vendors in the same hours on an ordinary week. 5 vendors named Azure in 5 incidents (5 of them blamed it). Vendors reported an Azure outage; Azure’s own incident for this date is not in the archive.
Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.
Times are UTC; lags are from when the first vendor named Azure.
- first vendor named Azure 16:25
How it spread
Vendors that named Azure, grouped by when they posted, and vendors that blamed one of the vendors Azure took down. Solid lines: the vendor named the other. Dashed: same window, not named.
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Azure<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>4 vendors, 4 blamed Azure<br/>Devin (Cognition), Smartsheet, Sigma Computing, Elastic Cloud"]:::blames
root --> h1
later["Later<br/>1 vendor, 1 blamed Azure<br/>Speechmatics"]:::blames
root --> laterVendors that named Azure
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Within an hour
4 vendors
- Critical incident
+0 min
Blames Azure
Devin (Cognition)Devins failing to start
…Devins failing to start The Microsoft Azure issue has been resolved, and Devins should be operating normally.…
- Major incident
+31 min
Blames Azure
SmartsheetInvestigating errors using Login with Microsoft
…Login with Microsoft Beginning on October 29th, 2025, from 8:41AM PDT, users experienced Azure/Microsoft login issues. The issue occurred due to a 3rd party authentication service provider. This was…
- Minor incident
+33 min
Blames Azure
Sigma ComputingService disruption affecting Azure-hosted customers
…Service disruption affecting Azure-hosted customers This incident has been resolved. This incident has been resolved. We are currently investigating a partial service disruption affecting Azure-hosted…
- Major incident
+34 min
Blames Azure
Elastic CloudAzure degradation impacting some services
…Azure degradation impacting some services We are currently investigating an issue with Azure impacting some of our services, specifically Managed OTLP and MIS.…
Later
1 vendor
- Critical incident
+4 h 55 min
Blames Azure
SpeechmaticsOutage affecting Portal, Batch SaaS API and Management Platform API
…to our Batch/Portal/MP APIs. Portal and Usage Reporting are still experiencing an outage. Azure indicates expected recovery to happen by 23:20 UTC (see https://azure.status.microsoft/en-us/status). We…
Same window, did not name anyone
17 incidents started during the event without naming Azure or another vendor. Some are part of it, some are a normal day’s background (about 21 in these hours).
Show all 17
- −15 minMinor incident
- −13 minMajor incident
- −10 minMajor incident
- −8 minMajor incident
- −4 minMinor incident
- +0 minMinor incident
- +1 minMinor incident
- +12 minMajor incident
- +16 minMinor incident
- +30 minMajor incident
- +1 h 16 minMajor incident
- +1 h 28 minMinor incident
- +1 h 34 minMinor incident
- +1 h 40 minMinor incident
- +1 h 52 minMinor incident
- +1 h 56 minMinor incident
- +2 h 2 minMajor incident
Detected automatically from 14 status pages opening incidents in the peak hour (normally at most 8). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.