Rewindex

CompaniesSigma ComputingIncidents

Sigma Computing: Cloudflare Outage

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.sigmacomputing.com (opens in new tab)
Part of an outage event

Cloudflare outage, Jul 17, 2020 · 24 vendors, 24 incidents

Sigma Computing’s incident blames Cloudflare as the cause. (hop 1, posted +0 min vs the first vendor naming Cloudflare)

“…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…”

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 CloudflareHotjarSigma Computing (this incident)posted +0 min
Cloudflareown incident not archivedWithin an hour6 vendors, 6 blamed CloudflareSigma Computing, WorkOS,Doppler, Linode (Akamai) +21 to 4 hours later1 vendor, 1 blamed CloudflareHotjarSigma Computing (this incident)posted +0 min
Sigma Computing is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
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
  me["Sigma Computing (this incident)<br/>posted +0 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    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 following: https://blog.cloudflare.com/cloudflare-outage-on-july-17-2020/

From Sigma Computing’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.sigmacomputing.com (opens in new tab).

Sigma Computing profileRecent Sigma Computing incidentsMarkdownJSON