Looking for an update now? Check the current status, or follow Sigma Computing for future changes.
94.8%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
90%
30
3
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Service Degradation for writeback functionality on Databricks connections
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.
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 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.
We'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.
Our preliminary investigations indicate the following:
Impacted Cloud Regions: Azure, AWS, GCP
Incident Start Time: Approximately September 26, 2026, at 11:24 AM UTC
investigating
We are currently looking into reports that users with password authentication are unable to log in to Sigma, along with failures in scheduled report delivery.
Both issues appear to stem from a disruption in the email service. We are actively investigating and will share an update as soon as more information is available.
Our preliminary investigations indicate the following:
Impacted Cloud Regions & Services: Azure, AWS, GCP
Incident Start Time: Approximately September 26, 2026, at 11:24 AM UTC
We will provide updates on this page when we have pertinent status updates.
Databricks Azure East US has recovered and is now operational. Sigma connections to Databricks Azure East US should no longer experience query execution failures or timeouts, and warehouse connections should be working normally.
This was caused by a Databricks Azure East US service interruption (https://status.azuredatabricks.net/). If you're still seeing errors on your Databricks connection in Sigma, please continue monitoring: https://status.azuredatabricks.net/
We apologize for the disruption and thank you for your patience.
identified
Databricks Azure East US is degraded services which is affecting Sigma connections and causing query execution failures and timeouts on Databrick warehouse.
We are investigating these errors owing to Databricks Azure East US service interruption (https://status.azuredatabricks.net/) and haven't detected an issue other warehouses at the moment.
If your Databrick connection in Sigma is experiencing errors, please continue monitoring: https://status.azuredatabricks.net/
We apologize for the disruption and will keep this page updated.
identified
Databricks Azure East US is degraded services which is affecting Sigma connections and causing query execution failures and timeouts on Databrick warehouse.
We are investigating these errors owing to Databricks Azure East US service interruption (https://status.azuredatabricks.net/) and haven't detected an issue other warehouses at the moment.
If your Databrick connection in Sigma is experiencing errors, please continue monitoring: https://status.azuredatabricks.net/
Our apologies for any inconvenience caused.
Widespread failures are preventing Sigma from loading for GCP-hosted organizations.
Our engineers are seeing signs of recovery from an outage associated with GCP and related networking failures. We are monitoring the service closely and awaiting confirmation from Google Cloud that the incident is fully resolved before declaring this issue resolved. We will provide another update when we have further information.
Impacted Cloud Regions & Services: Sigma users hosted on GCP
User Experience: We expect GCP-hosted users starting to be able to load Sigma, open workbooks, or rend...
investigating
We have received reports of errors causing users to be unable to utilize all portions of the Sigma application.
We are investigating the issue at the highest priority.
Our preliminary investigations indicate the following:
Impacted Cloud Regions & Services: organization hosted on GCP
User Experience: Unable to load Sigma
Incident Start Time: Approximately 2:46 PM UTC
We will provide updates on this page in the next 1 hour.
Legacy Incident Archive
9 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Delayed audit logs and usage data in AWS US West
Source not attested
Last archived state: resolved
View archived record details
monitoring
Status: Mitigated
The issue has been mitigated - audit logs and usage data are flowing and updating normally again. We're now in a monitoring phase to confirm stability. No data has been lost.
identified
The resync remains in progress. No data has been lost - records are being backfilled and will appear as the sync progresses. We'll provide another update as soon as there's meaningful progress to share.
identified
Impact: Some organizations in the AWS US West (Oregon) region are seeing delayed updates to audit logs and usage dashboards.
Our engineering team has identified the cause and is actively resyncing the affected data. No data has been lost - records are being backfilled and will appear as the sync progresses. We'll post an update as soon as the data is fully current.
Incident Start Time: Aug 5, 2026, 15:37 UTC
Materialization cleanup delayed for Sigma users on AWS US-West-2
Source not attested
Last archived state: resolved
View archived record details
monitoring
Our engineers have implemented mitigation measures for this issue and are closely monitoring their effectiveness. We expect the backlog to continue clearing over the next several hours. We will provide a further update once we can confirm full resolution.
Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization
User Experience: Customers using materializations on AWS US-West-2 may continue to see table accumulation reported earlier while the backlog clear...
investigating
We are investigating an issue affecting materialization tables, which are not being cleaned up as expected in some customers' connected warehouses, causing them to accumulate over time. We are treating this as our highest priority and are actively working to identify and resolve the root cause. We apologize for any inconvenience this may cause.
Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization
User Experience: Customers using materializations on AW...
Workbooks containing Snowflake Semantic Views fail to load
Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue where workbooks containing a Snowflake Semantic View fail to load. Sigma Engineering is actively engaged as our highest priority. We apologize for any inconvenience caused.
Impacted Cloud Regions & Services: All Regions
User Experience: Workbook stuck in loading state when containing snowflake semantic views
Workarounds: None at this time
ETA: We do not have an ETA for resolution at this time. Updates will be provided as more information becomes available.
I...
Query Timeouts for Snowflake Connections
Source not attested
Last archived state: resolved
View archived record details
monitoring
Monitoring – Query Timeouts for Snowflake Connections
Snowflake has updated their status page to indicate that a fix was pushed to resolve the previously reported incident.
Customers using Sigma with Snowflake may have seen elevated "DeadlineExceeded" errors or "Query timed out while running in the data warehouse" errors during this incident window. Based on Snowflake’s latest status update, this issue has now been resolved.
Incident end time: 16:36 UTC August 03, 2026
identified
Snowflake is currently experiencing degraded functionality, which began at 13:35 UTC and was reported at 14:11 UTC. Customers may experience a corresponding spike in DeadlineExceeded and "Query timed out while running in the data warehouse" errors using a Snowflake data warehouse.
If your connection uses Sigma with Snowflake, please monitor http://status.snowflake.com/ for updates.
We have not detected any issues with other data warehouse providers at this time.
investigating
Investigating – Query Timeouts for Snowflake Connections
We are currently investigating an issue causing query timeouts for customers connected via Snowflake. Affected users may see errors such as DeadlineExceeded or Query timed out while running in the data warehouse when running queries.
We do not have an ETA for resolution at this time. Updates will be provided as more information becomes available.
June 2026
Scheduled exports and materializations are delayed
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Mitigation measures have proven effective and our monitoring indicates that delayed scheduled exports and materializations are now being executed.
Impacted Cloud Regions & Services: AWS US-WEST-2
User Experience: We expect users to start seeing their delayed exports and materializations come through and new ones process.
Incident Start Time: Approximately 05:00 UTC June 24, 2026
monitoring
Our engineers have identified scheduled exports and materializations being delayed due to slow running queries in our database causing scheduled tasks to be backed up. Mitigations measures have been taken to circumvent the issue causing this backup and our engineers are monitoring their effect closely.
Impacted Cloud Regions & Services: AWS US-WEST-2
User Experience: Scheduled exports and materializations remain delayed. Users are advised to manually run scheduled exports as needed in the m...
investigating
We have received reports of scheduled exports and materializations being delayed and not executing on their planned schedules. We are investigating the issue at the highest priority.
Our preliminary investigations indicate the following:
Impacted Cloud Regions & Services: AWS US
User Experience: Scheduled exports not being received at planned time and materializations not being created at scheduled time.
Incident Start Time: Approximately 5:00 UTC June 24, 2026
We will provide updates on th...
High errors showing being displayed in workbooks
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have received reports of errors loading workbook elements on their Sigma application.
We are investigating the issue at the highest priority.
Our preliminary investigations indicate the following:
Impacted Cloud Regions & Services: AWS aws-us-west-2
User Experience: "An error has occurred" presented on workbooks.
Incident Start Time: Approximately 10:30 AM PST
We will provide updates on this page when we have pertinent status updates.
May 2026
Errors on pivot table export
Source not attested
Last archived state: resolved
View archived record details
identified
Users are experiencing elevated errors when exporting pivot tables, with the error message "Column alias not found".
April 2026
Permission Denied Errors on Elements Sourced from Custom SQL Tables
Source not attested
Last archived state: resolved
View archived record details
investigating
We're continuing to investigate the permissions issues that users are facing that lead to users seeing permission denied on workbooks.
Impacted Cloud Regions & Services: All regions
User Experience: View/Lite users get permission denied error in the workbook
Incident Start Time: Approximately 2:00PM UTC April 08, 2026
March 2026
Experiencing issues with Google sheets Integration
Source not attested
Last archived state: resolved
View archived record details
monitoring
Our engineers have implemented mitigation measures to circumvent the issue and we are monitoring their effect closely.
Impacted Cloud Regions & Services: All regions
User Experience: Google Sheets integration and related exports should now be functioning as expected.
Incident Start Time: Approximately 19:15 UTC March 31, 2026
Incident End Time: Approximately 22:12 UTC March 31, 2026
identified
We have identified the root cause for this issue with Google sheets integration and are currently deploying a fix to all regions. We will update here once we have additional information. We are treating this as our highest priority. Our apologies for any inconvenience caused.
Impacted Cloud Regions & Services: All regions
User Experience: Affected users are unable to create or use Google Sheets integrations in their exports.
Incident Start Time: Approximately 19:15 UTC March 31, 2026
