Live  /  Sigma Computing  /  Incident

Sigma Computing: Service Degradation for writeback functionality on Databricks connections

Sigma Computing · sigmacomputing.comMajor incidentResolved2026-10-12 18:17 UTC
Public — what happened

Summary

Sigma Computing reported a major service degradation on October 12, 2026, starting at 15:11 UTC, in which some customers could not upload CSV files to its Sample Connection and writeback features such as Input Tables could fail for customers using Databricks in affected regions. Sigma attributed the problem to an outage at its third-party provider Databricks. At 17:29 UTC the company said Databricks' AWS US West 2 region had recovered and affected connections should be working again. Sigma marked the incident resolved at 18:17.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Sigma Computing against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Sigma Computing: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Sigma Computing report →

More from Sigma Computing

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Sigma Computing status & history page.

Related: Sigma Computing status & history. SquidGrid is not affiliated with Sigma Computing.