Rewindex

RewindexOutage eventsJul 2, 2019

Cloudflare outage, Jul 2, 2019

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

    9. first vendor named Cloudflare 12:43
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 hour1 vendor, 1 blamed CloudflareWise1 to 4 hours later3 vendors, 3 blamed CloudflareOptimizely, Discord, Pendo
Cloudflareown incident not archivedWithin an hour1 vendor, 1 blamed CloudflareWise1 to 4 hours later3 vendors, 3 blamed CloudflareOptimizely, Discord, Pendo
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/>1 vendor, 1 blamed Cloudflare<br/>Wise"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>3 vendors, 3 blamed Cloudflare<br/>Optimizely, Discord, Pendo"]:::blames
  root --> h4

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

1 vendor

  • +0 min

    Blames Cloudflare

    Incident, no impact listed

    WiseCloudflare issues

    …Cloudflare issues Due to Cloudflare network performance issues, the TransferWise API, website and app were not available (partially operating with degraded performance) for 28 minutes. Cloudflare is n…

1 to 4 hours later

3 vendors

  • +1 h 15 min

    Blames Cloudflare

    Major incident

    OptimizelyNetwork Performance Issues With Cloudflare

    …Network Performance Issues With Cloudflare The incident has been resolved by Cloudflare.…

  • +1 h 34 min

    Blames Cloudflare

    Major incident

    DiscordCloudflare Outage

    …Cloudflare Outage Service is fully recovered as of 7:20 AM PDT. The impact of this outage was entirely due to an upstream issue that started at 6:42 AM, and lasted until 7:10 AM PDT. Following that, w…

  • +1 h 44 min

    Blames Cloudflare

    Minor incident

    PendoMarketing site outage

    …an outage with our marketing site (https://www.pendo.io/). This was due to a now-resolved Cloudflare outage (https://www.cloudflarestatus.com/). The Pendo application, guide serving, and data collecti…

Same window, did not name anyone

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

Show all 12

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