All Systems Operational

Uptime over the past 90 days. View historical uptime.
AWS Operational
Sigma - AWS (Europe) Operational
Sigma - AWS (US) Operational
Sigma - AWS (Canada) Operational
Sigma - AWS (APAC Australia) Operational
Sigma - AWS (UK) Operational
Azure Operational
Sigma - Azure (US) Operational
Sigma - Azure (Europe) Operational
Sigma - Azure (Canada) Operational
Sigma - Azure (UK) Operational
GCP Operational
Sigma - GCP (US) 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.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
app.sigmacomputing.com - uptime
Fetching

Sep 16, 2026

No incidents reported today.

Sep 15, 2026

No incidents reported.

Sep 14, 2026

Databricks Azure East US query timeout
Resolved - The 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 normally.

This was caused by a Databricks Azure East US service interruption (https://status.azuredatabricks.net/). If you continue to see errors on your Databricks connection in Sigma, please reach out to us.

We apologize for the disruption and thank you for your patience.
Sep 14, 22:53 UTC
Monitoring - 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.
Sep 14, 21:55 UTC
Update - 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.
Sep 14, 21:19 UTC
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.
Sep 14, 19:31 UTC

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

Input Table Edits Failing if customer updated warehouse connection
Resolved - The 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.
Sep 11, 22:01 UTC
Update - We applied a mitigation and are monitoring its effect closely. Customers can now safely change warehouse connection auth method and make input table edits.

We'll share our next update in 4 hours. Thanks for your patience.
Sep 11, 17:51 UTC
Monitoring - Our engineers have implemented mitigation measures to circumvent the issue and we are monitoring their effect closely. Customers can now safely change warehouse connection auth method and make input table edits.
Sep 11, 04:14 UTC
Update - Customers can now safely change warehouse connection auth method. We are still restoring the impacted customers who are unable to make edits to input tables that were created prior to the auth method change. We will post another update once the input tables have been restored.

We apologize for the inconvenience and will continue to update this page as we make progress.
Sep 11, 02:37 UTC
Update - Customers can now change auth methods safely. However we are still restoring the affected customers who are unable to make edits to input tables. We will post another update once the input tables have been restored.

We apologize for the inconvenience and will continue to update this page as we make progress!
Sep 11, 00:37 UTC
Update - We've identified an issue causing edits to existing input tables to fail on certain connections using OAuth authentication when connection was changed from non-OAuth connection.

Our engineering team is now testing a fix in internal environments. we will continue to update the page as we make progress.

Thanks for your patience!
Sep 10, 22:43 UTC
Update - We have reverted the issue, customers can now change their warehouse connection Auth Method without breaking input tables. We are still working to restore writeback on input tables for the affected connections. We will post another update once the input tables have been restored.

We apologize for the inconvenience and will continue to update this page as we make progress!
Sep 10, 19:18 UTC
Identified - We've identified an issue causing edits to existing input tables to fail on certain connections using OAuth authentication when connection was changed from non-OAuth connection.

Impact: Some customers are unable to save edits to existing input tables on affected connections.

Next Steps: We are reverting the change that introduced this regression and are working to restore writeback on input tables for the affected connections. We will post another update once a fix has been deployed.

We apologize for the inconvenience and will continue to update this page as we make progress!
Sep 10, 18:24 UTC

Sep 10, 2026

Sep 9, 2026

No incidents reported.

Sep 8, 2026

No incidents reported.

Sep 7, 2026

No incidents reported.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

No incidents reported.

Sep 3, 2026

No incidents reported.

Sep 2, 2026

Scheduled Materialization and Export Failures
Resolved - We 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 Community site in coming days.

Impacted Cloud Regions & Services: azure:production:eastus2 and aws:us-west-2

User Experience: For organizations hosted in the affected regions (aws:us-west-2 and azure:production:eastus2), scheduled materializations and scheduled exports did not run for the duration of the incident. Exports and materializations have since returned to normal operation. Organizations with a high volume of scheduled exports may experience some delayed processing as queued jobs catch up.

Incident Start Time: Approximately 12:02 PM UTC
Incident End Time: Approximately 1:01PM UTC
Sep 2, 13:37 UTC
Incident History Powered by Atlassian Statuspage