Rewindex

RewindexOutage eventsJul 17, 2020

Cloudflare outage, Jul 17, 2020

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

    5. first vendor named Cloudflare 21:00
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 hour6 vendors, 6 blamed CloudflareSigma Computing, WorkOS, Doppler, Linode (Akamai) +21 to 4 hours later1 vendor, 1 blamed CloudflareHotjar
Cloudflareown incident not archivedWithin an hour6 vendors, 6 blamed CloudflareSigma Computing, WorkOS,Doppler, Linode (Akamai) +21 to 4 hours later1 vendor, 1 blamed CloudflareHotjar
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/>6 vendors, 6 blamed Cloudflare<br/>Sigma Computing, WorkOS, Doppler, Linode (Akamai) +2"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Hotjar"]:::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

6 vendors

  • +0 min

    Blames Cloudflare

    Incident, no impact listed

    Sigma ComputingCloudflare Outage

    …Cloudflare Outage Cloudflare had a 27 minute outage in certain data centers due to a routing issue. This has affected Sigma's application and dns resolution. For more information please reference the…

  • +16 min

    Blames Cloudflare

    Major incident

    WorkOSCloudflare Service Outage

    …Cloudflare Service Outage The WorkOS Audit Trail, SSO, and Directory Sync services are now operating normally. The upstream internet service provider has addressed the root cause of the issue and syst…

  • +20 min

    Blames Cloudflare

    Critical incident

    DopplerDNS resolution failure

    …hub and status page but did not result in any data loss. ## What Happened? Doppler uses [Cloudflare](https://cloudflare.com) as our DNS provider which provides a suite of powerful features including…

  • +24 min

    Blames Cloudflare

    Critical incident

    Linode (Akamai)Connectivity issues - Linode Manager, Linode.com

    …Connectivity issues - Linode Manager, Linode.com Connectivity within Cloudflare's network has stabilized. Linode.com and the Linode Manager have also remained stable, so we are considering this incide…

  • +31 min

    Blames Cloudflare

    Critical incident

    DiscordCloudflare outage

    …Cloudflare outage This incident has been resolved.…

  • +49 min

    Blames Cloudflare

    Incident, no impact listed

    SentryPotential loss in ability to submit events due to CloudFlare Outage.

    …Potential loss in ability to submit events due to CloudFlare Outage. We believe CloudFlare has addressed their instability.…

1 to 4 hours later

1 vendor

  • +1 h 16 min

    Blames Cloudflare

    Incident, no impact listed

    HotjarData loss for Cloudflare websites

    …Data loss for Cloudflare websites The issue has been resolved. Thank you for your patience!…

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 3 in these hours).

Show all 17

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