Sigma Computing Incident History

1. resolvedSep 11 · 22:01 UTC

   The mitigation measures have proven effective, and the issue is resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.

Reported by Sigma Computing on their status page.

1. resolvedSep 2 · 13:37 UTC

   We received reports of errors causing scheduled materializations and exports to fail. This has been resolved now. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days. Impacted Cloud Regions & Services: azure:production:eastus2 and aws:us-west-2 User Experience: For organizations hosted in the affected regions (aws:us-west-2 and azure:production:eastus2), scheduled materializations and scheduled exports did not run for the duration of the incident. Exports and materializations have since returned to normal operation. Organizations with a high volume of scheduled exports may experience some delayed processing as queued jobs catch up. Incident Start Time: Approximately 12:02 PM UTC Incident End Time: Approximately 1:01PM UTC

Reported by Sigma Computing on their status page.

1. postmortemSep 8 · 17:59 UTC

   Incident date: September 1, 2026
   Duration: Approximately 90 minutes
   Affected service: Sigma organizations hosted in Google Cloud Platform (GCP) us-central1

   Summary

   On September 1, a Google Cloud networking incident in part of the us-central1 region interrupted connectivity to Sigma services. Customers hosted in GCP us-central1 were unable to reliably access the Sigma application, administration UI, workbooks, and some embedded experiences. No Sigma code or configuration change triggered the incident.

   Root cause

   During routine maintenance, Google Cloud experienced a network failure in part of the us-central1-b zone. Sigma services in the region had a non-redundant network dependency in the affected zone, so a zone-scoped failure caused a broader service disruption for customers hosted in the region. See the Google Cloud incident report for details about the cloud provider event.

   Resolution

   Google Cloud restored the underlying network service, and Sigma recovered without a Sigma-side deployment. Customers did not need to make changes to resume using Sigma.

   Corrective actions

   Sigma is taking the following actions:

   • Increase network redundancy across affected Sigma services in this region. Other regions are not impacted by the same deficiency as that in us-central1.
   • Add additional production health monitoring that operates independently of the environment it monitors.
   • Improve zone-level availability monitoring and alerting for external status pages.
   • Improve retry and recovery behavior for background workloads (including materialization) during transient network failures.

   We apologize for the disruption and are using this incident to improve the resilience and independent detection of Sigma services.

Reported by Sigma Computing on their status page.

1. resolvedSep 1 · 04:00 UTC

   Between August 28 at approximately 11:47 PM UTC and September 1 at approximately 4:09 PM UTC, scheduled and direct exports displayed some number and date columns as text when opened in Excel and Google Sheets. The cause has been identified and resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days. Timeline Incident start time: August 28, approximately 11:47 PM UTC Incident end time: September 1, approximately 4:09 PM UTC

Reported by Sigma Computing on their status page.