RewindexOutage eventsJan 25, 2023
Azure outage, Jan 25, 2023
14 vendors posted 13 incidents between 07:00 and 10:00 UTC, against about 2 incidents from 2 vendors in the same hours on an ordinary week. 4 vendors named Azure in 4 incidents (3 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 07:00
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/>1 vendor, 1 blamed Azure<br/>MongoDB Atlas"]:::blames
root --> h1
h4["1 to 4 hours later<br/>3 vendors, 2 blamed Azure<br/>Grafana Cloud, Retool, InfluxData (InfluxDB Cloud)"]:::blames
root --> h4Vendors that named Azure
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Within an hour
1 vendor
- Incident, no impact listed
+0 min
Blames Azure
MongoDB AtlasMongoDB Atlas: Clusters hosted in Microsoft Azure may have experienced networking issues
…MongoDB Atlas: Clusters hosted in Microsoft Azure may have experienced networking issues Starting approximately 07:05 UTC on 25 January 2023 and running to approximately 09:45 that same day, Microsoft…
1 to 4 hours later
3 vendors
- Minor incident
+1 h 27 min
Names Azure
Grafana CloudSynthetic Monitoring significant degradation in the EU-West and US-central Azure
…Synthetic Monitoring significant degradation in the EU-West and US-central Azure This incident has been resolved.…
- Major incident
+1 h 44 min
Blames Azure
RetoolSome Retool services affected by Azure outage
…Some Retool services affected by Azure outage This incident has been resolved.…
- Major incident
+2 h 31 min
Blames Azure
InfluxData (InfluxDB Cloud)Azure networking issues Multiple regions affected
…Azure networking issues Multiple regions affected Incident has been resolved for any more info please check out https://status.azure.com/en-gb/status…
Same window, did not name anyone
9 incidents started during the event without naming Azure or another vendor. Some are part of it, some are a normal day’s background (about 2 in these hours).
Show all 9
- +1 h 2 minMinor incident
- +1 h 16 minMinor incident
- +1 h 21 minMinor incident
- +1 h 34 minMinor incident
- +1 h 34 minCritical incident
- +2 h 11 minMinor incident
- +2 h 14 minMinor incident
- +2 h 21 minMajor incident
- +2 h 40 minCritical incident
Detected automatically from 7 status pages opening incidents in the peak hour (normally at most 5). 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.