Sigma Computing Outage History

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

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

Between August 28 at approximately 11:47 PM UTC and September 1 at approximately 4:09 PM UTC, scheduled and direct exports displayed 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

Status: Resolved The issue has been resolved and audit logs and usage data are fully up to date. All previously delayed records have been backfilled. No data was lost at any point during this incident. Incident Start Time: Aug 5, 2026, 15:37 UTC Incident End Time: Aug 11, 2026, 14:47 UTC

The mitigation measures have proven effective, and the issue has been resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note in the coming days. We apologize for any inconvenience this may have caused. Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization User Experience: Customers using materializations on AWS US-West-2 should no longer see the previously reported table accumulation. Incident Start Time: Approximately August 3, 2026, at 2:44 PM UTC Incident End Time: Approximately August 5, 2026, at 02:40 AM UTC

Sigma engineering has identified the cause, and the issue is now resolved. Users will need to perform a hard refresh of their browser to see the fix take effect. We will conduct a root cause analysis (RCA) and publish our findings in a postmortem note on the Sigma Community site in the coming days. Impacted Cloud Regions & Services: All Regions User Experience: Workbooks should now load normally after a hard refresh or browser restart. Incident Start Time: Approximately 09:30 UTC, August 4, 2026 Incident End Time: Approximately 10:42 UTC, August 4, 2026

Resolved - Query Timeouts for Snowflake Connections Snowflake has updated their status page to indicate that a fix was pushed to resolve the previously reported incident. Hence, based on Snowflake’s latest status update, this issue has now been resolved. Incident end time: 16:36 UTC August 03, 2026

We identified a higher than usual spike in CPU usage during the timeframe below on our AWS instance. We scaled our infrastructure accordingly to accommodate this and the mitigation measures have proven effective, and our monitoring indicates that this 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 the coming days. Impacted Cloud Regions & Services: AWS US-WEST-2 User Experience: We expect users to no longer experience workbook errors. Incident Start Time: Approximately 17:30 UTC June 22, 2026 Incident End Time: Approximately 18:14 UTC June 22, 2026

This incident has been resolved.

This incident has been resolved.

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. Impacted Cloud Regions & Services: All regions User Experience: Google Sheets integration and related exports should now be functioning as expected. Incident Start Time: Approximately 19:15 UTC March 31, 2026 Incident End Time: Approximately 22:12 UTC March 31, 2026

Our 3rd party vendor has updated their incident marking it as now resolved. We have confirmed that our chat support system is fully operational and our technical support engineers are available there. We will mark this incident as resolved as well. Again we apologize for the inconvenience this has caused, and appreciate your understanding.

This incident has been resolved. The queued tasks should start recovering automatically

We have identified that PDF export failures were impacting a small percentage of our users. We applied mitigation steps and our monitoring indicates that this issue has been resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in the coming days. Impacted Cloud Regions & Services: AWS US and GCP US regions, PDF Exports User Experience: We expect impacted users' scheduled exports to succeed without the errors seen previously Incident Start Time: Approximately 13:00 UTC on 2025-12-11 Incident End Time: Approximately 17:50 UTC on 2025-12-11

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.

This incident has been resolved.

Starting at 7:11 UTC, AWS reported increased error rates and latencies for multiple services in the US-EAST-1 Region. At 10:35 UTC, AWS declared the incident in the US-EAST-1 region mitigated. While Sigma's service was not impacted by the incident, third party services that Sigma uses were impacted. Customers may have experienced intermittent delays or failures when accessing or using cloud data warehouse services during the incident. Contacting Sigma Support via Live Chat or email was disrupted during the incident. Incident Start Time: 7:11 UTC Incident End Time: 10:35 UTC

This incident has been resolved.