Changes / Sigma Computing / Service Degradation for writeback functionality on Databricks connections
Sigma Computing: Major incident: Service Degradation for writeback functionality on Databricks connections
Summary
Sigma reported a major degradation affecting CSV uploads to Sample Connection and potentially Databricks writeback functionality, including Input Tables, caused by a Databricks AWS US West 2 service interruption. The incident started at 2026-10-12 15:11 UTC and was resolved at 2026-10-12 18:17 UTC, lasting 3 h 6 min; writeback failures were no longer occurring.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Service Degradation for writeback functionality on Databricks connections
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-10-12 15:11 UTC
Before: not present
After: 2026-10-12 18:17 UTC
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Service Degradation for writeback functionality on Databricks connections (this change) Sigma reported a major degradation affecting CSV uploads to Sample Connection and potentially Databricks writeback functionality, including Input Tables, caused by a Databricks AWS US West 2 service interruption. The incident started at 2026-10-12 15:11 UTC and was resolved at 2026-10-12 18:17 UTC, lasting 3 h 6 min; writeback failures were no longer occurring. | Major incident |
All Sigma Computing changes → · Sigma Computing profile · Markdown · JSON