Is Sigma Computing down?

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.

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.

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.

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.

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.

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

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

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

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

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

We are continuing to monitor for any further issues.

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

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.

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.

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.

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.

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!

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!

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.

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!

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.

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.

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.

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.