Sigma Computing Outage History

Started Oct 12, 2026, 03:11 PM UTC· resolved Oct 12, 2026, 06:17 PM UTC

1. identified Oct 12, 2026, 03:11 PM UTC

   Sigma is currently being affected by a 3rd party Databricks outage and some customers are unable to upload CSVs to our Sample Connection. Writeback functionality, such as Input Tables for customers with Databricks on the affected regions listed below may also be affected by this event. Our internal monitoring has identified a correlation between the two systems and we are currently monitoring the active incident here - https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1 We will update this page as the situation develops.

2. identified Oct 12, 2026, 04:10 PM UTC

   Sigma is currently being affected by a 3rd party Databricks outage and some customers are unable to upload CSVs to our Sample Connection. Writeback functionality, such as Input Tables for customers with Databricks on the affected regions listed below may also be affected by this event. Our internal monitoring has identified a correlation between the two systems and we are currently monitoring the active incident here - https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1 We will provide another update within 120 minutes as the situation develops.

3. monitoring Oct 12, 2026, 05:29 PM UTC

   Databricks AWS US West 2 has recovered. Sigma Databricks connections in the affected region should no longer experience failures with writeback functionality, such as Input Tables. It was caused by an incident on Databricks here - https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1 We apologize for the disruption and thank you for your patience. We will continue to update this page as we monitor the status.

4. resolved Oct 12, 2026, 06:17 PM UTC

   The AWS US West Databricks service interruption has been resolved. Sigma connections to Databricks on affected region are no longer experiencing writeback failures. The root cause has been identified as a Databricks AWS US West 2 service interruption (https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1). If you continue to have writeback errors on your Databricks connection in Sigma, please reach out to us. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Sep 26, 2026, 03:25 PM UTC· resolved Sep 26, 2026, 04:11 PM UTC

1. investigating Sep 26, 2026, 03:25 PM UTC

   We are currently looking into reports that users with password authentication are unable to log in to Sigma, along with failures in scheduled report delivery. Both issues appear to stem from a disruption in the email service. We are actively investigating and will share an update as soon as more information is available. Our preliminary investigations indicate the following: Impacted Cloud Regions & Services: Azure, AWS, GCP Incident Start Time: Approximately September 26, 2026, at 11:24 AM UTC We will provide updates on this page when we have pertinent status updates.

2. investigating Sep 26, 2026, 04:08 PM UTC

   We've identified the root cause and applied a fix, and we're now monitoring the resolution. Scheduled exports should resume as expected, and users on orgs with password authentication should now be able to sign in. Our preliminary investigations indicate the following: Impacted Cloud Regions: Azure, AWS, GCP Incident Start Time: Approximately September 26, 2026, at 11:24 AM UTC

3. resolved Sep 26, 2026, 04:11 PM UTC

   We've identified the root cause and applied a fix, and we're now monitoring the resolution. Scheduled exports should resume as expected, and users on orgs with password authentication should now be able to sign in. Our preliminary investigations indicate the following: Impacted Cloud Regions: Azure, AWS, GCP Incident Start Time: Approximately September 26, 2026, at 11:24 AM UTC

Read the full incident report →

Started Sep 21, 2026, 04:34 PM UTC· resolved Sep 21, 2026, 06:29 PM UTC

1. investigating Sep 21, 2026, 04:34 PM UTC

   We are investigating an issue with scheduled exports in reports where users are unable to change the email message. We are treating this as our highest priority. Our apologies for any inconvenience caused. Impacted Cloud Regions & Services: All regions User Experience: Upon changing the scheduled export message, it reverts back to the default message. Incident Start Time: Approximately 15:43 UTC September 21, 2026

2. identified Sep 21, 2026, 05:03 PM UTC

   The issue has been identified and a fix is being implemented by the Engineering team.

3. monitoring Sep 21, 2026, 06:25 PM UTC

   A fix has been implemented and we are monitoring the results now.

4. monitoring Sep 21, 2026, 06:28 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Sep 21, 2026, 06:29 PM UTC

   The issue has now been fixed and users should be able to change the scheduled export email messages successfully now.

Read the full incident report →

Started Sep 14, 2026, 07:31 PM UTC· resolved Sep 14, 2026, 10:53 PM UTC

1. identified Sep 14, 2026, 07:31 PM UTC

   Databricks Azure East US is degraded services which is affecting Sigma connections and causing query execution failures and timeouts on Databrick warehouse. We are investigating these errors owing to Databricks Azure East US service interruption (https://status.azuredatabricks.net/) and haven't detected an issue other warehouses at the moment. If your Databrick connection in Sigma is experiencing errors, please continue monitoring: https://status.azuredatabricks.net/ Our apologies for any inconvenience caused.

2. identified Sep 14, 2026, 09:19 PM UTC

   Databricks Azure East US is degraded services which is affecting Sigma connections and causing query execution failures and timeouts on Databrick warehouse. We are investigating these errors owing to Databricks Azure East US service interruption (https://status.azuredatabricks.net/) and haven't detected an issue other warehouses at the moment. If your Databrick connection in Sigma is experiencing errors, please continue monitoring: https://status.azuredatabricks.net/ We apologize for the disruption and will keep this page updated.

3. monitoring Sep 14, 2026, 09:55 PM UTC

   Databricks Azure East US has recovered and is now operational. Sigma connections to Databricks Azure East US should no longer experience query execution failures or timeouts, and warehouse connections should be working normally. This was caused by a Databricks Azure East US service interruption (https://status.azuredatabricks.net/). If you're still seeing errors on your Databricks connection in Sigma, please continue monitoring: https://status.azuredatabricks.net/ We apologize for the disruption and thank you for your patience.

4. resolved Sep 14, 2026, 10:53 PM UTC

   The Azure East US Databricks service interruption has been resolved. Sigma connections to Databricks Azure East US are no longer experiencing query execution failures or timeouts, and warehouse connections are working normally. This was caused by a Databricks Azure East US service interruption (https://status.azuredatabricks.net/). If you continue to see errors on your Databricks connection in Sigma, please reach out to us. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Sep 10, 2026, 06:24 PM UTC· resolved Sep 11, 2026, 10:01 PM UTC

1. identified Sep 10, 2026, 06:24 PM UTC

   We've identified an issue causing edits to existing input tables to fail on certain connections using OAuth authentication when connection was changed from non-OAuth connection. Impact: Some customers are unable to save edits to existing input tables on affected connections. Next Steps: We are reverting the change that introduced this regression and are working to restore writeback on input tables for the affected connections. We will post another update once a fix has been deployed. We apologize for the inconvenience and will continue to update this page as we make progress!

2. identified Sep 10, 2026, 07:18 PM UTC

   We have reverted the issue, customers can now change their warehouse connection Auth Method without breaking input tables. We are still working to restore writeback on input tables for the affected connections. We will post another update once the input tables have been restored. We apologize for the inconvenience and will continue to update this page as we make progress!

3. identified Sep 10, 2026, 10:43 PM UTC

   We've identified an issue causing edits to existing input tables to fail on certain connections using OAuth authentication when connection was changed from non-OAuth connection. Our engineering team is now testing a fix in internal environments. We'll share another update once writeback is fully restored. Thanks for your patience! We'll keep this page updated as we progress.

4. identified Sep 11, 2026, 12:37 AM UTC

   Customers can now change auth methods safely. However we are still restoring the effected customers who are unable to make edits to input tables. We will post another update once the input tables have been restored. We apologize for the inconvenience and will continue to update this page as we make progress!

5. identified Sep 11, 2026, 02:37 AM UTC

   Customers can now safely change warehouse connection auth method. We are still restoring the impacted customers who are unable to make edits to input tables that were created prior to the auth method change. We will post another update once the input tables have been restored. We apologize for the inconvenience and will continue to update this page as we make progress.

6. monitoring Sep 11, 2026, 04:14 AM UTC

   Our engineers have implemented mitigation measures to circumvent the issue and we are monitoring their effect closely. Customers can now safely change warehouse connection auth method and make input table edits.

7. monitoring Sep 11, 2026, 05:51 PM UTC

   We applied a mitigation and are monitoring its effect closely. Customers can now safely change warehouse connection auth method and make input table edits. We'll share our next update in 4 hours. Thanks for your patience.

8. resolved Sep 11, 2026, 10:01 PM 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.

Read the full incident report →

Started Sep 02, 2026, 12:02 PM UTC· resolved Sep 02, 2026, 01:01 PM UTC

1. resolved Sep 02, 2026, 01:37 PM 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

Read the full incident report →

Started Sep 01, 2026, 03:34 PM UTC· resolved Sep 01, 2026, 04:55 PM UTC

1. investigating Sep 01, 2026, 03:34 PM UTC

   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 3:06 PM UTC We will provide updates on this page in the next 1 hour.

2. monitoring Sep 01, 2026, 04:23 PM UTC

   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

3. resolved Sep 01, 2026, 04:55 PM 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

4. postmortem Sep 08, 2026, 05:59 PM 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](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.

Read the full incident report →

Started Sep 01, 2026, 04:00 AM UTC· resolved Sep 02, 2026, 04:09 PM UTC

1. resolved Sep 02, 2026, 06:56 PM UTC

   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

Read the full incident report →

Started Aug 10, 2026, 06:37 PM UTC· resolved Aug 11, 2026, 05:32 PM UTC

1. identified Aug 10, 2026, 06:37 PM UTC

   Impact: Some organizations in the AWS US West (Oregon) region are seeing delayed updates to audit logs and usage dashboards. Our engineering team has identified the cause and is actively resyncing the affected data. No data has been lost - records are being backfilled and will appear as the sync progresses. We'll post an update as soon as the data is fully current. Incident Start Time: Aug 5, 2026, 15:37 UTC

2. identified Aug 10, 2026, 10:52 PM UTC

   The resync remains in progress. No data has been lost - records are being backfilled and will appear as the sync progresses. We'll provide another update as soon as there's meaningful progress to share.

3. monitoring Aug 11, 2026, 04:18 AM UTC

   The issue has been mitigated - audit logs and usage data are flowing and updating normally again. We're now in a monitoring phase to confirm stability. No data has been lost.

4. resolved Aug 11, 2026, 05:32 PM UTC

   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

Read the full incident report →

Started Aug 04, 2026, 11:58 PM UTC· resolved Aug 05, 2026, 03:19 AM UTC

1. investigating Aug 04, 2026, 11:58 PM UTC

   We are investigating an issue affecting materialization tables, which are not being cleaned up as expected in some customers' connected warehouses, causing them to accumulate over time. We are treating this as our highest priority and are actively working to identify and resolve the root cause. We apologize for any inconvenience this may cause. Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization User Experience: Customers using materializations on AWS US-West-2 may see stale materialization tables accumulating in their connected warehouse, which over time could approach warehouse storage/object limits. Incident Start Time: Approximately August 3, 2026, at 2:44:18 PM UTC

2. monitoring Aug 05, 2026, 12:20 AM UTC

   Our engineers have implemented mitigation measures for this issue and are closely monitoring their effectiveness. We expect the backlog to continue clearing over the next several hours. We will provide a further update once we can confirm full resolution. Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization User Experience: Customers using materializations on AWS US-West-2 may continue to see table accumulation reported earlier while the backlog clears; no new action is needed. Incident Start Time: Approximately August 3, 2026, at 2:44:18 PM UTC

3. resolved Aug 05, 2026, 03:19 AM 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

Read the full incident report →

Started Aug 04, 2026, 10:37 AM UTC· resolved Aug 04, 2026, 11:11 AM UTC

1. investigating Aug 04, 2026, 10:37 AM UTC

   We are investigating an issue where workbooks containing a Snowflake Semantic View fail to load. Sigma Engineering is actively engaged as our highest priority. We apologize for any inconvenience caused. Impacted Cloud Regions & Services: All Regions User Experience: Workbook stuck in loading state when containing snowflake semantic views Workarounds: None at this time ETA: We do not have an ETA for resolution at this time. Updates will be provided as more information becomes available. Incident Start Time: Approximately 09:30 UTC, August 4, 2026

2. resolved Aug 04, 2026, 11:11 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

Read the full incident report →

Started Aug 03, 2026, 02:55 PM UTC· resolved Aug 03, 2026, 06:07 PM UTC

1. investigating Aug 03, 2026, 02:55 PM UTC

   Investigating – Query Timeouts for Snowflake Connections We are currently investigating an issue causing query timeouts for customers connected via Snowflake. Affected users may see errors such as DeadlineExceeded or Query timed out while running in the data warehouse when running queries. We do not have an ETA for resolution at this time. Updates will be provided as more information becomes available.

2. identified Aug 03, 2026, 03:26 PM UTC

   Snowflake is currently experiencing degraded functionality, which began at 14:11 UTC. Customers may experience a corresponding spike in DeadlineExceeded and "Query timed out while running in the data warehouse" errors using a Snowflake data warehouse. If your connection uses Sigma with Snowflake, please monitor http://status.snowflake.com/ for updates. We have not detected any issues with other data warehouse providers at this time.

3. monitoring Aug 03, 2026, 05:38 PM UTC

   Monitoring – Query Timeouts for Snowflake Connections Snowflake has updated their status page to indicate that a fix was pushed to resolve the previously reported incident. Customers using Sigma with Snowflake may have seen elevated "DeadlineExceeded" errors or "Query timed out while running in the data warehouse" errors during this incident window. Based on Snowflake’s latest status update, this issue has now been resolved. Incident end time: 16:36 UTC August 03, 2026

4. resolved Aug 03, 2026, 06:07 PM UTC

   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

Read the full incident report →

Started Jun 24, 2026, 01:30 PM UTC· resolved Jun 24, 2026, 07:35 PM UTC

1. investigating Jun 24, 2026, 01:30 PM UTC

   We have received reports of scheduled exports and materializations being delayed and not executing on their planned schedules. We are investigating the issue at the highest priority. Our preliminary investigations indicate the following: Impacted Cloud Regions & Services: AWS US User Experience: Scheduled exports not being received at planned time and materializations not being created at scheduled time. Incident Start Time: Approximately 5:00 UTC June 24, 2026 We will provide updates on this page when we have pertinent status updates.

2. monitoring Jun 24, 2026, 02:53 PM UTC

   Our engineers have identified scheduled exports and materializations being delayed due to slow running queries in our database causing scheduled tasks to be backed up. Mitigations measures have been taken to circumvent the issue causing this backup and our engineers are monitoring their effect closely. Impacted Cloud Regions & Services: AWS US-WEST-2 User Experience: Scheduled exports and materializations remain delayed. Users are advised to manually run scheduled exports and materializations as needed in the meantime. Incident Start Time: Approximately 05:00 UTC June 24, 2026

3. monitoring Jun 24, 2026, 04:53 PM UTC

   Mitigation measures have proven effective and our monitoring indicates that delayed scheduled exports and materializations are now being executed. Impacted Cloud Regions & Services: AWS US-WEST-2 User Experience: We expect users to start seeing their delayed exports and materializations come through and new ones process. Incident Start Time: Approximately 05:00 UTC June 24, 2026

4. resolved Jun 24, 2026, 07:35 PM UTC

   The mitigation measures have proven effective, and our monitoring indicates that this issue is resolved. We will continue monitoring closely this incident for any recurrence in the next hours. 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 delayed scheduled exports and materializations. Users should have received previously delayed scheduled exports and delayed materializations should have ran. Incident Start Time: Approximately 05:00 UTC June 24, 2026 Incident End Time: Approximately 17:30 UTC June 24, 2026

5. postmortem Jul 21, 2026, 09:20 PM UTC

   Sigma Engineering has completed the postmortem of this incident. A Root Cause Analysis \(RCA\) is available on the Sigma Community site: [Postmortem for Delayed Scheduled Exports and Materializations](https://community.sigmacomputing.com/t/postmortem-for-delayed-scheduled-exports-and-materializations/7125)

Read the full incident report →

Started Jun 22, 2026, 06:11 PM UTC· resolved Jun 22, 2026, 06:52 PM UTC

1. investigating Jun 22, 2026, 06:11 PM UTC

   We have received reports of errors loading workbook elements on their Sigma application. We are investigating the issue at the highest priority. Our preliminary investigations indicate the following: Impacted Cloud Regions & Services: AWS aws-us-west-2 User Experience: "An error has occurred" presented on workbooks. Incident Start Time: Approximately 10:30 AM PST We will provide updates on this page when we have pertinent status updates.

2. resolved Jun 22, 2026, 06:52 PM UTC

   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

Read the full incident report →

Started May 15, 2026, 01:21 AM UTC· resolved May 15, 2026, 01:49 PM UTC

1. identified May 15, 2026, 01:21 AM UTC

   Users are experiencing elevated errors when exporting pivot tables, with the error message "Column alias not found".

2. resolved May 15, 2026, 01:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 08, 2026, 06:22 PM UTC· resolved Apr 08, 2026, 11:39 PM UTC

1. investigating Apr 08, 2026, 06:22 PM UTC

   The permission denied issue got resolved Impacted Cloud Regions & Services: All regions User Experience: Users get permission denied error in the workbook Incident Start Time: Approximately 2:00PM UTC April 08, 2026

2. resolved Apr 08, 2026, 11:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 31, 2026, 09:08 PM UTC· resolved Apr 01, 2026, 03:30 AM UTC

1. identified Mar 31, 2026, 09:08 PM UTC

   We have identified the root cause for this issue with Google sheets integration and are currently deploying a fix to all regions. We will update here once we have additional information. We are treating this as our highest priority. Our apologies for any inconvenience caused. Impacted Cloud Regions & Services: All regions User Experience: Affected users are unable to create or use Google Sheets integrations in their exports. Incident Start Time: Approximately 19:15 UTC March 31, 2026

2. monitoring Mar 31, 2026, 09:50 PM UTC

   Our engineers have implemented mitigation measures to circumvent the issue and we are monitoring their effect closely. 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

3. resolved Apr 01, 2026, 03:30 AM 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. 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

Read the full incident report →

Started Mar 04, 2026, 08:50 PM UTC· resolved Mar 09, 2026, 05:31 PM UTC

1. investigating Mar 04, 2026, 08:50 PM UTC

   We have temporarily paused burst email exports to investigate a technical issue. Status: Burst exports are unavailable. Unaffected: Standard exports are fully operational. We will update this notification with new developments.

2. investigating Mar 04, 2026, 10:25 PM UTC

   Our engineers are still investigating the issue with burst email exports. This feature will remain paused until investigation has identified the root cause. We apologize for the inconvenience and we will update this status with new developments as soon as they become available.

3. investigating Mar 05, 2026, 01:27 AM UTC

   Our engineers are actively investigating the issue with burst email exports. This feature will remain paused until the root cause. We will update this status with new developments as soon as they become available.

4. investigating Mar 05, 2026, 05:31 AM UTC

   Our engineers are actively investigating the on-going issue with burst email exports. We understand the impact this has on your workflows and appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing.

5. investigating Mar 05, 2026, 10:10 AM UTC

   Our engineers are continuing to investigate the burst email exports issue. We appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing.

6. investigating Mar 05, 2026, 06:33 PM UTC

   Our engineers are actively investigating the on-going issue with burst email exports. We appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing.

7. investigating Mar 05, 2026, 09:33 PM UTC

   Our engineers are actively investigating the on-going issue with burst email exports. We appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing.

8. investigating Mar 06, 2026, 12:36 AM UTC

   Our engineers are actively investigating the on-going issue with burst email exports. We appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing.

9. investigating Mar 06, 2026, 06:06 AM UTC

   Our engineering team has deployed a fix and is currently validating it internally. Standard (non-burst) exports remain fully operational and are unaffected. We will share a further update as validation progresses Thank you for your continued patience. Impact on Customers: Burst email exports remain temporarily unavailable while the investigation is ongoing.

10. investigating Mar 06, 2026, 10:26 AM UTC

    Internal validation tests are ongoing and we will share further updates as we have them. Standard (non-burst) exports remain fully operational and are unaffected. Thank you for your continued patience. Impact on Customers: Burst email exports remain temporarily unavailable while the investigation is ongoing.

11. identified Mar 06, 2026, 08:28 PM UTC

    Burst email exports remain unavailable. We have deployed a fix and are currently validating it internally. Standard (non-burst) exports remain fully operational. We will provide further updates as validation progresses and before re-enabling burst email exports more broadly. Thank you for your patience.

12. identified Mar 07, 2026, 01:22 AM UTC

    We are continuing to work on a fix for this issue.

13. monitoring Mar 07, 2026, 01:27 AM UTC

    Burst Email Exports have now been re-enabled. Our engineering team has identified and deployed a fix for the issue affecting Email Burst Exports. Following thorough internal validation and testing, we have re-enabled the feature and will continue monitoring performance closely. If you experience any further issues with Burst Email Exports, please reach out to our support team via live chat.

14. resolved Mar 09, 2026, 05:31 PM UTC

    Issue with Burst Email Exports are resolved We previously re-enabled Burst Email Exports after deploying a fix for the issue impacting this feature. Since re-enabling, our team has closely monitored system performance and error rates, and we have not observed any recurring problems. At this time, the incident is considered fully resolved, and Burst Email Exports are operating as expected. If you encounter any new or unexpected behavior with Burst Email Exports, please contact our support team via live chat so we can investigate promptly.

15. postmortem Mar 17, 2026, 04:19 PM UTC

    Sigma Engineering has completed the postmortem of this incident. A Root Cause Analysis \(RCA\) is available on the Sigma Community site: [Postmortem For March 03, 2026 Burst Email Export Issue](https://community.sigmacomputing.com/t/postmortem-for-march-03-2026-burst-email-export-issue/6632)

Read the full incident report →

Started Jan 09, 2026, 08:33 PM UTC· resolved Jan 09, 2026, 10:23 PM UTC

1. investigating Jan 09, 2026, 08:33 PM UTC

   Our 3rd party chat system Intercom is currently experiencing an outage as listed here https://www.intercomstatus.com/us-hosting. If you have an urgent request that requires immediate attention while this outage is ongoing, please go to https://support.sigmacomputing.com and press "Submit a Request" to submit a ticket. Expect response times being slower than usual. We apologize for this inconvenience and will update this page as the situation develops.

2. monitoring Jan 09, 2026, 09:12 PM UTC

   Our 3rd party system has updated their incident saying a fix has been implemented. Sigma support team has noticed that the chat application is currently online and our Support Engineers are online but we will continue monitoring for any up new development.

3. investigating Jan 09, 2026, 09:15 PM UTC

   We are continuing to investigate this issue.

4. monitoring Jan 09, 2026, 09:18 PM UTC

   Our 3rd party system has updated their incident saying a fix has been implemented. Sigma support team has noticed that the chat application is currently online and our Support Engineers are online but we will continue monitoring for any up new development.

5. resolved Jan 09, 2026, 10:23 PM UTC

   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.

Read the full incident report →

Started Jan 05, 2026, 09:38 PM UTC· resolved Jan 05, 2026, 11:33 PM UTC

1. investigating Jan 05, 2026, 09:38 PM UTC

   We are currently investigating an issue affecting scheduled exports, materializations, and warehouse view updates on AWS US

2. monitoring Jan 05, 2026, 11:13 PM UTC

   A fix has been implemented and we are monitoring the results

3. resolved Jan 05, 2026, 11:33 PM UTC

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

Read the full incident report →

Started Dec 11, 2025, 04:21 PM UTC· resolved Dec 11, 2025, 06:17 PM UTC

1. investigating Dec 11, 2025, 04:21 PM UTC

   We have received reports of errors causing PDF exports to fail. We are investigating the issue at the highest priority. Our preliminary investigations indicate the following: Impacted Cloud Regions & Services: AWS US and GCP US regions, PDF Exports User Experience: Timeout errors causing PDF export failures Incident Start Time: Approximately 13:00 UTC on 2025-12-11 We will provide updates on this page when we have pertinent status updates.

2. investigating Dec 11, 2025, 05:29 PM UTC

   We are continuing to investigate the issue at the highest priority. We will provide updates on this page when we have pertinent status updates.

3. resolved Dec 11, 2025, 06:17 PM UTC

   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

4. postmortem Dec 19, 2025, 12:56 PM UTC

   Sigma Engineering has completed the postmortem of this incident. A Root Cause Analysis \(RCA\) is available on the Sigma Community site: [Post Mortem for Dec 11, 2025 incident - Degraded performance for Schedule PDF & PNG Exports, AWS US and GCP regions](https://community.sigmacomputing.com/t/post-mortem-for-dec-11-2025-incident-degraded-performance-for-schedule-pdf-png-exports-aws-us-and-gcp-regions/6401).

Read the full incident report →

Started Dec 05, 2025, 08:56 AM UTC· resolved Dec 05, 2025, 09:12 AM UTC

1. resolved Dec 05, 2025, 04:07 PM UTC

   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.

Read the full incident report →

Started Oct 29, 2025, 04:57 PM UTC· resolved Oct 29, 2025, 10:29 PM UTC

1. monitoring Oct 29, 2025, 04:57 PM UTC

   We are currently investigating a partial service disruption affecting Azure-hosted customers. Users may notice issues with loading, displaying, or uploading images and other custom assets. Initial reports suggest this appears to be caused by an Azure CDN outage. We are actively monitoring the situation.

2. resolved Oct 29, 2025, 10:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 07:00 AM UTC· resolved Oct 20, 2025, 10:35 AM UTC

1. resolved Oct 20, 2025, 12:22 PM UTC

   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

Read the full incident report →

Started Sep 21, 2025, 02:56 AM UTC· resolved Sep 21, 2025, 06:37 AM UTC

1. investigating Sep 21, 2025, 02:56 AM UTC

   We are investigating an issue with Sigma organizations hosted on Azure that impacts login. We are treating this as our highest priority. Our apologies for any inconvenience caused. User Experience: Login page does not load

2. monitoring Sep 21, 2025, 03:42 AM UTC

   The issue is now mitigated. All Azure users should be able to log into Sigma without issue at this time.

3. monitoring Sep 21, 2025, 03:43 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Sep 21, 2025, 06:37 AM UTC

   This incident has been resolved.

Read the full incident report →