Service Degradation for writeback functionality on Databricks connections
Incident
Report for Sigma Computing
Resolved
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.
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.
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.
Update
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.
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.