Rewindex

RewindexOutage eventsDec 16, 2021

Cloudflare outage, Dec 16, 2021

10 vendors posted 9 incidents between 20:00 and 21:00 UTC, against about 3 incidents from 3 vendors in the same hours on an ordinary week. 2 vendors named Cloudflare in 2 incidents (2 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.

    3. first vendor named Cloudflare 20:36
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 hour2 vendors, 2 blamed CloudflareHubSpot, Optimizely
Cloudflareown incident not archivedWithin an hour2 vendors, 2 blamed CloudflareHubSpot, Optimizely
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/>2 vendors, 2 blamed Cloudflare<br/>HubSpot, Optimizely"]:::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

2 vendors

  • +0 min

    Blames Cloudflare

    Minor incident

    HubSpotSome tools are slow to load or timing out

    …loading or timeout issues in HubSpot due to an outage on our third-party cloud platform, Cloudflare. Cloudflare has resolved the root cause of the issue, and all tools in HubSpot should now load prop…

  • +14 min

    Blames Cloudflare

    Incident, no impact listed

    OptimizelyCloudflare latency

    …Cloudflare latency This incident has been resolved.…

Same window, did not name anyone

7 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 7

Detected automatically from 12 status pages opening incidents in the peak hour (normally at most 6). 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.