Changes / Sigma Computing / Widespread failures are preventing Sigma from loading for GCP-hosted organizations.
Sigma Computing: Critical incident: Widespread failures are preventing Sigma from loading for GCP-hosted organizations.
Summary
A critical outage prevented GCP-hosted organizations in us-central1 from reliably accessing Sigma. The recorded incident ran from 2026-09-01 15:34 UTC to 2026-09-01 16:55 UTC (1 h 20 min), though Sigma reported an approximate start of 2:46 PM UTC. The postmortem attributed the disruption to a Google Cloud networking incident; services returned to normal.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Widespread failures are preventing Sigma from loading for GCP-hosted organizations.
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2026-09-01 15:34 UTC
Before: not present
After: 2026-09-01 16:55 UTC
Before: not present
After: GCP - Sigma - GCP (US), Sigma - GCP (US)
Before: not present
After: We have received reports of errors causing users to be unable to utilize all portions of the Sigma application.
We are investigating the issue at the highest priority.
Our preliminary investigations indicate the following:
Impacted Cloud Regions & Services: organization hosted on GCP
User Experience: Unable to load Sigma
Incident Start Time: Approximately 2:46 PM UTC
We will provide updates on this page in the next 1 hour.
Before: not present
After: Our engineers are seeing signs of recovery from an outage associated with GCP and related networking failures. We are monitoring the service closely and awaiting confirmation from Google Cloud that the incident is fully resolved before declaring this issue resolved. We will provide another update when we have further information.
Impacted Cloud Regions & Services: Sigma users hosted on GCP
User Experience: We expect GCP-hosted users starting to be able to load Sigma, open workbooks, or render reports fine
Incident Start Time: Approximately 02:46 UTC Sep 1, 2026
Before: not present
After: This incident has been resolved. Our engineers are seeing services have returned to normal. Multiple customers have confirmed that they can load Sigma successfully. We apologize for the inconvenience and will continue monitoring the service closely. 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: Sigma users hosted on GCP
User Experience: GCP-hosted users will be able to load Sigma, open workbooks, or render reports without any issues.
Incident Start Time: Approximately 02:46 PM UTC Sep 1, 2026
Incident End Time: Approximately 05:29 PM UTC Sep1, 2026
Before: not present
After: **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](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev) 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Widespread failures are preventing Sigma from loading for GCP-hosted organizations. (this change) A critical outage prevented GCP-hosted organizations in us-central1 from reliably accessing Sigma. The recorded incident ran from 2026-09-01 15:34 UTC to 2026-09-01 16:55 UTC (1 h 20 min), though Sigma reported an approximate start of 2:46 PM UTC. The postmortem attributed the disruption to a Google Cloud networking incident; services returned to normal. | Major incident |
All Sigma Computing changes → · Sigma Computing profile · Markdown · JSON