Sigma Computing Outage History

22 incidents recorded over the last 365 days, 22 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Sigma Computing status100.00% uptime history

Every Recorded Sigma Computing Incident

Sigma Computing incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 12, 2026Service Degradation for writeback functionality on Databricks connectionsThe 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…3h 6mResolved
Sep 26, 2026Export Failures IncidentWe've identified the root cause and applied a fix, and we're now monitoring the resolution. Scheduled exports should resume as expected, and users on orgs with password authentication should now be able to sign in…45 minResolved
Sep 21, 2026Unable to change email message in scheduled exports inside Sigma reportsThe issue has now been fixed and users should be able to change the scheduled export email messages successfully now.1h 54mResolved
Sep 14, 2026Databricks Azure East US query timeoutThe Azure East US Databricks service interruption has been resolved. Sigma connections to Databricks Azure East US are no longer experiencing query execution failures or timeouts, and warehouse connections are working…3h 21mResolved
Sep 10, 2026Input Table Edits Failing if customer updated warehouse connectionThe mitigation measures have proven effective, and the issue is resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.27h 37mResolved
Sep 2, 2026Exports displayed number and date columns as text in Excel and Google SheetsBetween August 28 at approximately 11:47 PM UTC and September 1 at approximately 4:09 PM UTC, scheduled and direct exports displayed some number and date columns as text when opened in Excel and Google Sheets. The…-2336 minResolved
Sep 2, 2026Scheduled Materialization and Export FailuresWe received reports of errors causing scheduled materializations and exports to fail. This has been resolved now. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma…0 minResolved
Sep 1, 2026Widespread failures are preventing Sigma from loading for GCP-hosted organizations.**Incident date:** September 1, 2026 **Duration:** Approximately 90 minutes **Affected service:** Sigma organizations hosted in Google Cloud Platform \(GCP\) us-central1 ## Summary On September 1, a Google Cloud…1h 20mResolved
Aug 10, 2026Delayed audit logs and usage data in AWS US WestStatus: Resolved The issue has been resolved and audit logs and usage data are fully up to date. All previously delayed records have been backfilled. No data was lost at any point during this incident. Incident Start…22h 54mResolved
Aug 4, 2026Materialization cleanup delayed for Sigma users on AWS US-West-2The mitigation measures have proven effective, and the issue has been resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note in the coming days. We apologize for any…3h 20mResolved
Aug 4, 2026Workbooks containing Snowflake Semantic Views fail to loadSigma engineering has identified the cause, and the issue is now resolved. Users will need to perform a hard refresh of their browser to see the fix take effect. We will conduct a root cause analysis (RCA) and publish…33 minResolved
Aug 3, 2026Query Timeouts for Snowflake ConnectionsResolved - Query Timeouts for Snowflake Connections Snowflake has updated their status page to indicate that a fix was pushed to resolve the previously reported incident. Hence, based on Snowflake’s latest status…3h 12mResolved
Jun 24, 2026Scheduled exports and materializations are delayedSigma Engineering has completed the postmortem of this incident. A Root Cause Analysis \(RCA\) is available on the Sigma Community site: [Postmortem for Delayed Scheduled Exports and…6h 5mResolved
Jun 22, 2026High errors showing being displayed in workbooksWe identified a higher than usual spike in CPU usage during the timeframe below on our AWS instance. We scaled our infrastructure accordingly to accommodate this and the mitigation measures have proven effective, and…41 minResolved
May 15, 2026Errors on pivot table exportThis incident has been resolved.12h 28mResolved
Apr 8, 2026Permission Denied Errors on Elements Sourced from Custom SQL TablesThis incident has been resolved.8 minResolved
Mar 31, 2026Experiencing issues with Google sheets IntegrationThe mitigation measures have proven effective, and the issue is resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days. Impacted…6h 21mResolved
Mar 5, 2026Issue with Burst email exports are resolvedSigma Engineering has completed the postmortem of this incident. A Root Cause Analysis \(RCA\) is available on the Sigma Community site: [Postmortem For March 03, 2026 Burst Email Export…103h 21mResolved
Jan 9, 2026Chat Support experiencing 3rd party outageOur 3rd party vendor has updated their incident marking it as now resolved. We have confirmed that our chat support system is fully operational and our technical support engineers are available there. We will mark this…1h 49mResolved
Jan 5, 2026Scheduled Backend Tasks not running on AWS USThis incident has been resolved. The queued tasks should start recovering automatically1h 55mResolved
Dec 11, 2025Degraded performance on PDF ExportsSigma Engineering has completed the postmortem of this incident. A Root Cause Analysis \(RCA\) is available on the Sigma Community site: [Post Mortem for Dec 11, 2025 incident - Degraded performance for Schedule PDF &…1h 55mResolved
Dec 5, 2025Sigma Service Disruption Due to Cloudflare IncidentAt 08:56 UTC Cloudflare's scheduled maintenance to their Web Application Firewalls failed and an incident was declared. At 09:12 UTC a fix was deployed and traffic was restored. Sigma's service was impacted by this…-427 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Sigma Computing incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Sigma Computing Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Sigma Computing acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Sigma Computing outage in this window ran 4d 7h, against a mean recovery of 10h 8m. If you depend on Sigma Computing in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.