Rewindex

RewindexOutage eventsJul 18, 2024

Azure central us outage, Jul 18, 2024

9 vendors posted 8 incidents between 22:00 on Jul 18 and 08:00 on Jul 19 UTC, against about 10 incidents from 5 vendors in the same hours on an ordinary week. 6 vendors named Azure in 5 incidents (1 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.

    21. first vendor named Azure 22:00
Named AzureNamed another vendorDid not name anyoneEach column is 30 minutes

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.

Azure central usown incident not archivedWithin an hour5 vendors, 1 blamed AzureMongoDB Atlas, Confluent, GitHub, GitHub Copilot +1Later1 vendorContentstack
Azure central usown incident not archivedWithin an hour5 vendors, 1 blamed AzureMongoDB Atlas, Confluent,GitHub, GitHub Copilot +1Later1 vendorContentstack
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
flowchart LR
  root["Azure central us<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 1 blamed Azure<br/>MongoDB Atlas, Confluent, GitHub, GitHub Copilot +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor<br/>Contentstack"]:::names
  root --> later

Vendors 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

Later

1 vendor

Same window, did not name anyone

3 incidents started during the event without naming Azure or another vendor. Some are part of it, some are a normal day’s background (about 10 in these hours).

Show all 3

Detected automatically from 8 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.