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.
- first vendor named Cloudflare 06:33
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.
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 --> h1Vendors 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
- Critical incident
+0 min
Blames Cloudflare
DopplerServices responding with 500 Internal Server Error
…onitoring the results. This incident has been resolved. This issue is due to a widespread Cloudflare outage. https://www.cloudflarestatus.com/incidents/xvs51y9qs9dj We are continuing to monitor for an…
- Critical incident
+24 min
Blames Cloudflare
…Cloudflare outage This incident has been resolved.…
- Incident, no impact listed
+27 min
Blames Cloudflare
LatticeService Disruption with Upstream Provider
…Service Disruption with Upstream Provider Our upstream provider, Cloudflare, is currently experiencing an issue affecting site availability. We will resolve this incident once we have received confirm…
- Incident, no impact listed
+29 min
Blames Cloudflare
MattermostPartial outage affecting new and existing installations due to Cloudflare outage in some regions.
…Partial outage affecting new and existing installations due to Cloudflare outage in some regions. Incident has been resolved, but we are continuing to monitor. Incident has been resolved, but we are c…
- Minor incident
+37 min
Blames Cloudflare
HarnessHarness Impacted due to ongoing Cloudflare Incident
…Harness Impacted due to ongoing Cloudflare Incident We can confirm normal operation. Get Ship Done! We will continue to monitor and ensure stability.…
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
- −13 minCritical incident
- −12 minMinor incident
- −3 minMajor incident
- +2 minCritical incident
- +13 minMajor incident
- +13 minMajor incident
- +19 minMajor incident
- +19 minMinor incident
- +23 minMajor incident
- +24 minMajor incident
- +26 minMajor incident
- +30 minMajor incident
- +31 minMinor incident
- +33 minCritical incident
- +34 minMinor incident
- +35 minCritical incident
- +37 minMinor incident
- +38 minMajor incident
- +44 minCritical incident
- +45 minMinor incident
- +46 minMajor incident
- +48 minMajor incident
- +54 minMinor incident
- +54 minMinor incident
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.