Rewindex

RewindexOutage eventsOct 30, 2023

Cloudflare outage, Oct 30, 2023

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

blamed Auth0Cloudflareown incident not archivedWithin an hour4 vendors, 3 blamed CloudflareCensus, Rootly, Optimizely, VantaAuth0own incident not archivedSvix, Dremio+9 min to +39 min
blamed Auth0Cloudflareown incident not archivedWithin an hour4 vendors, 3 blamed CloudflareCensus, Rootly, Optimizely,VantaAuth0own incident not archivedSvix, Dremio+9 min to +39 min
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/>4 vendors, 3 blamed Cloudflare<br/>Census, Rootly, Optimizely, Vanta"]:::blames
  root --> h1
  p0["Auth0<br/>own incident not archived"]:::inferred
  root -.-> p0
  k0["Svix, Dremio<br/>+9 min to +39 min"]:::hop2
  p0 -->|"blamed Auth0"| k0

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

4 vendors

  • +0 min

    Blames Cloudflare

    Major incident

    CensusUnable to Authenticate

    …Unable to Authenticate Incident is resolved. The underlying cause was an outage at Cloudflare impacting our authentication service. We'll be monitoring for any changes to this status.…

  • +2 min

    Blames Cloudflare

    Incident, no impact listed

    RootlyDelays on Slack and Web Platform

    …king as normal, including incident creation in Slack. We had an upstream hiccup caused by Cloudflare. Looks like everything is working as normal, including incident creation in Slack. We had an upstre…

  • +24 min

    Blames Cloudflare

    Major incident

    OptimizelyCloudflare outage causing service disruption

    …Cloudflare outage causing service disruption This incident has been resolved…

  • +28 min

    Names Cloudflare

    Minor incident

    VantaSome US tests have been marked as "Upcoming" in error since 10/24.

    …been resolved, and the impacted tests should be functioning as expected: zone-level-rules-cloudflare (v1.0) bitbucket-author-is-different-from-reviewer (v1.0) bitbucket-organization-invitations-are-no…

Second hop: vendors that named another vendor

These incidents name a vendor other than Cloudflare, for example a messaging or CDN provider that was itself affected.

Same window, did not name anyone

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

Show all 17

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