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
- Started — 2026-10-12 15:11 UTC
- Identified — 2026-10-12 15:11 UTC (2 updates)
- Monitoring — 2026-10-12 17:29 UTC
- Resolved — 2026-10-12 18:17 UTC · 3h 06m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.