RewindexOutage eventsApr 1, 2021
Azure outage, Apr 1, 2021
13 vendors posted 11 incidents between 21:00 and 23:00 UTC, against about 4 incidents from 4 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 21:30
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, 3 blamed Azure<br/>LaunchDarkly, InfluxData (InfluxDB Cloud), Confluent, JFrog"]:::blames
root --> h1Vendors 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
- Minor incident
+0 min
Blames Azure
LaunchDarklyData Export delayed to Azure Events Hub
…Data Export delayed to Azure Events Hub Microsoft Azure DNS experienced an issue earlier today, which resulted in a delay in Data Export publishing events to Azure Events Hub. Microsoft has mitigated…
- Major incident
+16 min
Blames Azure
InfluxData (InfluxDB Cloud)Azure -- DNS instability
…Azure -- DNS instability This incident has been resolved.…
- Incident, no impact listed
+45 min
Blames Azure
ConfluentWidespread Azure Instability and Unavailability
…Widespread Azure Instability and Unavailability We continue to see Confluent Cloud Clusters operating nominally. Should you find any continuing issues out of this DNS outage, please contact our Custom…
- Critical incident
+45 min
Names Azure
JFrogOutage in Azure USE Region
…Outage in Azure USE Region This incident has been resolved.…
Same window, did not name anyone
7 incidents started during the event without naming Azure or another vendor. Some are part of it, some are a normal day’s background (about 4 in these hours).
Show all 7
- −11 minMinor incident
- +0 minMajor incident
- +6 minMinor incident
- +10 minMinor incident
- +17 minMajor incident
- +20 minMajor incident
- +20 minCritical incident
Detected automatically from 11 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.