Sigma Computing Outage History

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.

Status: Resolved Update: Sigma services affected by the Google GCP outage have fully recovered at this time. Incident Start Time: Approximately 17:55 UTC June 12, 2025 Incident End Time: Approximately 20:45 UTC June 12, 2025

Our upstream provider has confirmed the issue has resolved as of 11:06 AM UTC on January 29, 2025. Users may have experienced "404 NoSuchBucket" errors when accessing Sigma from EU/UK regions between the hours of 08:55 AM UTC and 10:01 AM UTC. This issue is now resolved and all services are operating normally.

On December 17, some Sigma users encountered column errors—such as "Reference to errored column" and "Expression contains errors"—when loading visualizations and tables. This issue surfaced as a result of introducing a workbook performance enhancement to the product. The issue has been resolved by reverting the recent change, and the Sigma application is now fully operational. We will conduct a thorough root cause analysis and share a detailed postmortem in the Sigma Community in the coming days. Incident Start Time: 15:49 UTC Incident End Time: 16:55 UTC

At approximately 22:38 UTC on September 10, 2024, some Sigma users were unable to publish workbooks and upload CSVs due to a spike in error rates caused by a third-party service network rule. The incident has been resolved by disabling the rule that was triggering the issue and Sigma is actively working with the service to mitigate this in the future. Users should now be able to publish workbooks and the Sigma app is fully operational. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days. Incident Start Time: Approximately 22:38 UTC September 10, 2024 Incident End Time: Approximately 23:50 UTC September 10, 2024

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: Sigma users hosted on AWS US West 2 User Experience: We expect the rate of errors to be negligible for all Sigma users hosted on AWS US West 2 Incident Start Time: Approximately 14:00 UTC September 4, 2024 Incident End Time: Approximately 14:30 UTC September 4, 2024