Input Table Edits Failing if customer updated warehouse connection
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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 18:24 UTC
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 11, 2026

Unresolved incident: Input Table Edits Failing if customer updated warehouse connection.

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

Sep 1, 2026

Widespread failures are preventing Sigma from loading for GCP-hosted organizations.
Postmortem - Read details
Sep 8, 17:59 UTC
Resolved - This incident has been resolved. Our engineers are seeing services have returned to normal. Multiple customers have confirmed that they can load Sigma successfully. We apologize for the inconvenience and will continue monitoring the service closely. 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: Sigma users hosted on GCP

User Experience: GCP-hosted users will be able to load Sigma, open workbooks, or render reports without any issues.

Incident Start Time: Approximately 02:46 PM UTC Sep 1, 2026
Incident End Time: Approximately 05:29 PM UTC Sep1, 2026
Sep 1, 16:55 UTC
Monitoring - 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 render reports fine

Incident Start Time: Approximately 02:46 UTC Sep 1, 2026
Sep 1, 16:23 UTC
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.
Sep 1, 15:34 UTC
Exports displayed number and date columns as text in Excel and Google Sheets
Resolved - Between 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 cause has been identified and 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.

Timeline
Incident start time: August 28, approximately 11:47 PM UTC
Incident end time: September 1, approximately 4:09 PM UTC
Sep 1, 04:00 UTC

Aug 31, 2026

No incidents reported.

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage