Rewindex

CompaniesSigma ComputingIncidents

Sigma Computing: Sigma Service Disruption Due to Cloudflare Incident

No impact listedStatus: resolvedStarted Resolved (-428 min)1 updatestspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Dec 5, 2025 · 46 vendors, 46 incidents

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

“…Sigma Service Disruption Due to Cloudflare Incident At 08:56 UTC Cloudflare's scheduled maintenance to their Web Application Firewalls failed and an incident was declared. At 09:12 UTC a fix was deplo…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamed CloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingSigma Computing (this incident)posted +7 h 21 min
Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamedCloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingSigma Computing (this incident)posted +7 h 21 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/>18 vendors, 18 blamed Cloudflare<br/>Unbounce, Expo, GitLab +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Klaviyo"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed Cloudflare<br/>Bitrise, Sigma Computing"]:::blames
  root --> later
  me["Sigma Computing (this incident)<br/>posted +7 h 21 min"]:::me
  later --- 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

    At 08:56 UTC Cloudflare's scheduled maintenance to their Web Application Firewalls failed and an incident was declared. At 09:12 UTC a fix was deployed and traffic was restored. Sigma's service was impacted by this incident, as this did not allow traffic to reach our servers. Our internal monitoring matches the incident timeline and indicated that customers may have experienced failures when using our services during this brief incident.

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

Sigma Computing profileRecent Sigma Computing incidentsMarkdownJSON