All Systems Operational

AWS Operational
Sigma - AWS (US) Operational
Sigma - AWS (Europe) Operational
Sigma - AWS (APAC Australia) Operational
Sigma - AWS (Canada) Operational
Sigma - AWS (UK) Operational
Azure Operational
Sigma - Azure (US) Operational
Sigma - Azure (Europe) Operational
Sigma - Azure (Canada) Operational
Sigma - Azure (UK) Operational
Sigma - Azure (Australia) Operational
GCP Operational
Sigma - GCP (US) Operational
Sigma - GCP (UK) Operational
Sigma - GCP (KSA) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Nov 18, 2026

No incidents reported today.

Nov 17, 2026

Resolved - The incident affecting Databricks, which caused slow or failed loading of workbooks and input tables using Databricks connections, has been resolved. Databricks has confirmed their service is operational, and we have verified that workbooks using Databricks connections are loading normally again. If you are still seeing issues, please contact Sigma Support.
Nov 17, 20:51 UTC
Monitoring - Databricks has reported that the issue affecting their service has been mitigated. We are seeing workbooks and input tables that use Databricks connections recover, and we are continuing to monitor to confirm performance is back to normal. We will post another update once we have confirmed full recovery.
Nov 17, 20:12 UTC
Identified - Databricks has identified the issue and is rolling back a change to restore service. Our team is closely monitoring the situation and will provide updates as more information becomes available.
Nov 17, 19:52 UTC
Investigating - We are currently seeing degraded performance and query timeouts for workbooks and input tables that use Databricks connections. Affected content may load slowly or fail to load. This is related to an ongoing incident reported by Databricks. Our team is closely monitoring the situation and will provide updates as more information becomes available.
Nov 17, 19:44 UTC

Nov 16, 2026

Resolved - This incident has been resolved.
Nov 16, 19:50 UTC
Monitoring - We are currently experiencing an issue with our third-party chat provider (Intercom), which is preventing us from receiving or responding to live chat messages. Our team is actively monitoring the situation with Intercom. In the meantime, if you encounter issue with raising a new chat, you can submit a request through the Sigma Support portal (https://help.sigmacomputing.com/docs/escalate-critical-issues) or email at support@sigmacomputing.com.
Nov 16, 19:40 UTC

Nov 15, 2026

No incidents reported.

Nov 14, 2026

No incidents reported.

Nov 13, 2026

No incidents reported.

Nov 12, 2026

No incidents reported.

Nov 11, 2026

No incidents reported.

Nov 10, 2026

No incidents reported.

Nov 9, 2026

No incidents reported.

Nov 8, 2026

No incidents reported.

Nov 7, 2026

Resolved - This incident has been resolved. AWS status page: https://health.aws.amazon.com/health/status
Nov 7, 01:24 UTC
Monitoring - At approximately 22:51 UTC on November 6, 2026, AWS reported elevated launch failures in the US-WEST-2 region (AWS status page: https://health.aws.amazon.com/health/status). Sigma organizations hosted on AWS US-WEST-2 may experience elevated latency during this time. We are monitoring AWS status.
Nov 7, 00:21 UTC

Nov 6, 2026

No incidents reported.

Nov 5, 2026

Postmortem - Read details
Nov 13, 00:46 UTC
Resolved - On November 5, 2026 between approximately 01:28 UTC to 02:25 UTC, Sigma users in GCP-US-hosted organizations saw high error rates when creating workbooks and explorations, publishing workbooks, tagging workbooks, and sending instant exports. This incident is now resolved and the Sigma app is fully operational.

Incident Start Time: November 5, 2026 01:28 UTC
Incident End Time: November 5, 2026 02:25 UTC

We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.

Nov 5, 09:00 UTC

Nov 4, 2026

No incidents reported.