Rewindex

RewindexOutage eventsJun 21, 2022

Cloudflare outage, Jun 21, 2022

30 vendors posted 29 incidents between 06:00 and 08:00 UTC, against about 3 incidents from 3 vendors in the same hours on an ordinary week. 5 vendors named Cloudflare in 5 incidents (5 of them blamed it). Vendors reported a Cloudflare outage; Cloudflare’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 Cloudflare.

  1. first vendor named Cloudflare 06:33
Named CloudflareNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named Cloudflare, grouped by when they posted, and vendors that blamed one of the vendors Cloudflare took down. Solid lines: the vendor named the other. Dashed: same window, not named.

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour5 vendors, 5 blamed CloudflareDoppler, LiveKit, Lattice, Mattermost +1
Cloudflareown incident not archivedWithin an hour5 vendors, 5 blamed CloudflareDoppler, LiveKit, Lattice,Mattermost +1
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["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 5 blamed Cloudflare<br/>Doppler, LiveKit, Lattice, Mattermost +1"]:::blames
  root --> h1

Vendors that named Cloudflare

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

5 vendors

Same window, did not name anyone

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

Show all 24

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