Service Degradation for writeback functionality on Databricks connections
View the provider incident record →Current answer
Sigma Computing experienced a major incident: Service Degradation for writeback functionality on Databricks connections. ServiceAlert observed recovery on Oct 12, 2026.
Official Sigma Computing status page Current Sigma Computing status
ServiceAlert observed status change:
Looking for an update now? Check the current status, or follow Sigma Computing for future changes.
Incident Lifecycle
Incident Timeline
Monitoring
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.
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.
Oct 12, 2026 at 5:29 PM UTC
Identified
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.
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.
Oct 12, 2026 at 4:10 PM UTC
Identified
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.
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.
Oct 12, 2026 at 3:11 PM UTC
Was your business affected by this Sigma Computing outage?
Follow Sigma Computing and route available status alerts to email or a team channel.