{
  "page": {
    "id": "4hr8rdym840d",
    "name": "Sigma Computing",
    "url": "https://status.sigmacomputing.com"
  },
  "status": {
    "indicator": "none",
    "description": "All Systems Operational"
  },
  "components": [{"status":"operational","name":"AWS","created_at":"2023-07-07T18:24:53.380Z","updated_at":"2023-07-07T18:24:53.380Z","position":10,"description":null,"showcase":false,"start_date":null,"id":"x8z7lpzf6cw4","group_id":null,"page_id":"4hr8rdym840d","components":["6hfstyp7zpd3","lzpwt4by0yrr","lwlh7jqfrzcb","whpg3nhtgj0x","kvkmm2zhw1f9"]},{"status":"operational","name":"Azure","created_at":"2023-07-07T18:25:23.479Z","updated_at":"2023-07-07T18:25:23.479Z","position":11,"description":null,"showcase":false,"start_date":null,"id":"50vclq2nhymf","group_id":null,"page_id":"4hr8rdym840d","components":["f754w346xp3s","tsjxslp28m2q","y5pgm6yj6krd","mm4z3ph7rkcb","xghj0y85btkv"]},{"status":"operational","name":"GCP","created_at":"2023-07-07T18:25:38.078Z","updated_at":"2023-07-07T18:25:38.078Z","position":12,"description":null,"showcase":false,"start_date":null,"id":"9r4w7gjmsl4s","group_id":null,"page_id":"4hr8rdym840d","components":["c2ftyy6cgk24","n0247mbsflvk","2qzd4whtn5f2"]}],
  "incidents": [{"name":"Degraded performance in AWS US-WEST-2 hosted organizations","status":"resolved","created_at":"2026-11-07T00:21:39.715Z","updated_at":"2026-11-07T01:24:08.860Z","monitoring_at":"2026-11-07T00:21:39.924Z","resolved_at":"2026-11-07T01:24:08.837Z","impact":"minor","shortlink":"https://stspg.io/jnwlx03yrqhy","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-11-07T00:21:39.702Z","reminder_intervals":null,"id":"7gnvjggs63qs","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"This incident has been resolved. AWS status page: https://health.aws.amazon.com/health/status","created_at":"2026-11-07T01:24:08.837Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-11-07T01:24:08.837Z","display_at":"2026-11-07T01:24:08.837Z","deliver_notifications":false,"tweet_id":null,"id":"r80f4yd801yg","incident_id":"7gnvjggs63qs","custom_tweet":null,"affected_components":[{"code":"6hfstyp7zpd3","name":"AWS - Sigma - AWS (US)","old_status":"degraded_performance","new_status":"operational"}]},{"status":"monitoring","body":"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.","created_at":"2026-11-07T00:21:39.924Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-11-07T00:21:39.924Z","display_at":"2026-11-07T00:21:39.924Z","deliver_notifications":false,"tweet_id":null,"id":"4w9pvt52chwb","incident_id":"7gnvjggs63qs","custom_tweet":null,"affected_components":[{"code":"6hfstyp7zpd3","name":"AWS - Sigma - AWS (US)","old_status":"operational","new_status":"degraded_performance"}]}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[{"status":"operational","name":"Sigma - AWS (US)","created_at":"2021-08-05T20:09:19.522Z","updated_at":"2026-11-09T21:58:19.804Z","position":1,"description":"System status tracking for Sigma organizations hosted on Amazon Web Service (AWS) US region.","showcase":true,"start_date":"2021-08-05T00:00:00.000Z","id":"6hfstyp7zpd3","page_id":"4hr8rdym840d","group_id":"x8z7lpzf6cw4"}]},{"name":"Service degradation in GCP-US-hosted organizations","status":"resolved","created_at":"2026-11-05T03:17:24.383Z","updated_at":"2026-11-05T03:17:24.442Z","monitoring_at":null,"resolved_at":"2026-11-05T09:00:00.000Z","impact":"none","shortlink":"https://stspg.io/jgctxtqc3q7v","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-11-05T03:17:24.379Z","reminder_intervals":null,"id":"y2h3hlzch6nr","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"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.\n\nIncident Start Time: November 5, 2026 01:28 UTC\nIncident End Time: November 5, 2026 02:25 UTC\n\nWe will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.","created_at":"2026-11-05T03:17:24.433Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-11-05T03:17:24.433Z","display_at":"2026-11-05T09:00:00.000Z","deliver_notifications":false,"tweet_id":null,"id":"ymjjn72drzlz","incident_id":"y2h3hlzch6nr","custom_tweet":null,"affected_components":null}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[]},{"name":"Service Degradation for writeback functionality on Databricks connections","status":"resolved","created_at":"2026-10-12T15:11:31.000Z","updated_at":"2026-10-12T18:17:53.852Z","monitoring_at":"2026-10-12T17:29:57.203Z","resolved_at":"2026-10-12T18:17:53.824Z","impact":"major","shortlink":"https://stspg.io/1h966c5jr6b1","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":"major","scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-10-12T15:11:31.000Z","reminder_intervals":null,"id":"69dryztvj3dj","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"The AWS US West Databricks service interruption has been resolved. Sigma connections to Databricks on affected region are no longer experiencing writeback failures.\n\nThe root cause has been identified as a Databricks AWS US West 2 service interruption (https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1). If you continue to have writeback errors on your Databricks connection in Sigma, please reach out to us.\n\nWe apologize for the disruption and thank you for your patience.","created_at":"2026-10-12T18:17:53.824Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-10-12T18:17:53.824Z","display_at":"2026-10-12T18:17:53.824Z","deliver_notifications":false,"tweet_id":null,"id":"ltmp5rvcdfr0","incident_id":"69dryztvj3dj","custom_tweet":null,"affected_components":null},{"status":"monitoring","body":"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.\n\nIt was caused by an incident on Databricks here - https://status.databricks.com/pages/incident/5cf02dde58a00904bda41926/6accd920d492610581e1c8c1\n\nWe apologize for the disruption and thank you for your patience. We will continue to update this page as we monitor the status.","created_at":"2026-10-12T17:29:57.203Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-10-12T17:29:57.203Z","display_at":"2026-10-12T17:29:57.203Z","deliver_notifications":false,"tweet_id":null,"id":"mx3hv65xfl9l","incident_id":"69dryztvj3dj","custom_tweet":null,"affected_components":null},{"status":"identified","body":"Sigma is currently being affected by a 3rd party Databricks outage and some customers are unable to upload CSVs to our Sample Connection. \n\nWriteback functionality, such as Input Tables for customers with Databricks on the affected regions listed below may also be affected by this event.\n\nOur 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 \n\nWe will provide another update within 120 minutes as the situation develops.","created_at":"2026-10-12T16:10:24.082Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-10-12T16:10:24.082Z","display_at":"2026-10-12T16:10:24.082Z","deliver_notifications":false,"tweet_id":null,"id":"zzp01wq2m7f8","incident_id":"69dryztvj3dj","custom_tweet":null,"affected_components":null},{"status":"identified","body":"Sigma is currently being affected by a 3rd party Databricks outage and some customers are unable to upload CSVs to our Sample Connection. \n\nWriteback functionality, such as Input Tables for customers with Databricks on the affected regions listed below may also be affected by this event.\n\nOur 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 \n\nWe will update this page as the situation develops.","created_at":"2026-10-12T15:11:31.103Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-10-12T15:13:34.469Z","display_at":"2026-10-12T15:11:31.000Z","deliver_notifications":false,"tweet_id":null,"id":"mt8p3vhwldl0","incident_id":"69dryztvj3dj","custom_tweet":null,"affected_components":null}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[]},{"name":"Export Failures Incident","status":"resolved","created_at":"2026-09-26T15:25:35.567Z","updated_at":"2026-09-26T16:11:07.714Z","monitoring_at":null,"resolved_at":"2026-09-26T16:11:07.695Z","impact":"major","shortlink":"https://stspg.io/mkpxm54chr2x","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-09-26T15:25:35.545Z","reminder_intervals":null,"id":"vj4whfqnfhsl","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"We've identified the root cause and applied a fix, and we're now monitoring the resolution.\n\nScheduled exports should resume as expected, and users on orgs with password authentication should now be able to sign in. \n\nOur preliminary investigations indicate the following:\nImpacted Cloud Regions: Azure, AWS, GCP\nIncident Start Time: Approximately September 26, 2026, at 11:24 AM UTC","created_at":"2026-09-26T16:11:07.695Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-26T16:11:07.695Z","display_at":"2026-09-26T16:11:07.695Z","deliver_notifications":true,"tweet_id":null,"id":"vvgqgmdsn0k4","incident_id":"vj4whfqnfhsl","custom_tweet":null,"affected_components":[{"code":"6hfstyp7zpd3","name":"AWS - Sigma - AWS (US)","old_status":"operational","new_status":"operational"},{"code":"whpg3nhtgj0x","name":"AWS - Sigma - AWS (Canada)","old_status":"operational","new_status":"operational"},{"code":"f754w346xp3s","name":"Azure - Sigma - Azure (US)","old_status":"operational","new_status":"operational"},{"code":"c2ftyy6cgk24","name":"GCP - Sigma - GCP (US)","old_status":"operational","new_status":"operational"}]},{"status":"investigating","body":"We've identified the root cause and applied a fix, and we're now monitoring the resolution.\n\nScheduled exports should resume as expected, and users on orgs with password authentication should now be able to sign in. \n\nOur preliminary investigations indicate the following:\nImpacted Cloud Regions: Azure, AWS, GCP\nIncident Start Time: Approximately September 26, 2026, at 11:24 AM UTC","created_at":"2026-09-26T16:08:30.309Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-26T16:08:30.309Z","display_at":"2026-09-26T16:08:30.309Z","deliver_notifications":true,"tweet_id":null,"id":"9l7zql7n07k9","incident_id":"vj4whfqnfhsl","custom_tweet":null,"affected_components":[{"code":"6hfstyp7zpd3","name":"AWS - Sigma - AWS (US)","old_status":"partial_outage","new_status":"operational"},{"code":"whpg3nhtgj0x","name":"AWS - Sigma - AWS (Canada)","old_status":"partial_outage","new_status":"operational"},{"code":"f754w346xp3s","name":"Azure - Sigma - Azure (US)","old_status":"partial_outage","new_status":"operational"},{"code":"c2ftyy6cgk24","name":"GCP - Sigma - GCP (US)","old_status":"partial_outage","new_status":"operational"}]},{"status":"investigating","body":"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.\n\nBoth 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.\n\nOur preliminary investigations indicate the following:\nImpacted Cloud Regions \u0026 Services: Azure, AWS, GCP\nIncident Start Time: Approximately September 26, 2026, at 11:24 AM UTC\n\nWe will provide updates on this page when we have pertinent status updates.","created_at":"2026-09-26T15:25:35.730Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-26T15:25:35.730Z","display_at":"2026-09-26T15:25:35.730Z","deliver_notifications":true,"tweet_id":null,"id":"m8qf14wxlphz","incident_id":"vj4whfqnfhsl","custom_tweet":null,"affected_components":[{"code":"6hfstyp7zpd3","name":"AWS - Sigma - AWS (US)","old_status":"operational","new_status":"partial_outage"},{"code":"whpg3nhtgj0x","name":"AWS - Sigma - AWS (Canada)","old_status":"operational","new_status":"partial_outage"},{"code":"f754w346xp3s","name":"Azure - Sigma - Azure (US)","old_status":"operational","new_status":"partial_outage"},{"code":"c2ftyy6cgk24","name":"GCP - Sigma - GCP (US)","old_status":"operational","new_status":"partial_outage"}]}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[{"status":"operational","name":"Sigma - GCP (US)","created_at":"2020-04-17T17:42:13.607Z","updated_at":"2026-09-26T16:08:30.233Z","position":1,"description":"System status tracking for Sigma organizations hosted on Google Cloud Platform (GCP) US region.","showcase":true,"start_date":null,"id":"c2ftyy6cgk24","page_id":"4hr8rdym840d","group_id":"9r4w7gjmsl4s"},{"status":"operational","name":"Sigma - AWS (US)","created_at":"2021-08-05T20:09:19.522Z","updated_at":"2026-11-09T21:58:19.804Z","position":1,"description":"System status tracking for Sigma organizations hosted on Amazon Web Service (AWS) US region.","showcase":true,"start_date":"2021-08-05T00:00:00.000Z","id":"6hfstyp7zpd3","page_id":"4hr8rdym840d","group_id":"x8z7lpzf6cw4"},{"status":"operational","name":"Sigma - Azure (US)","created_at":"2023-06-30T17:03:38.961Z","updated_at":"2026-09-26T16:08:30.249Z","position":1,"description":"System status tracking for Sigma organizations hosted on Microsoft Azure US region.","showcase":true,"start_date":"2023-04-15T00:00:00.000Z","id":"f754w346xp3s","page_id":"4hr8rdym840d","group_id":"50vclq2nhymf"},{"status":"operational","name":"Sigma - AWS (Canada)","created_at":"2023-07-07T18:55:07.362Z","updated_at":"2026-11-09T21:58:24.796Z","position":4,"description":"System status tracking for Sigma organizations hosted on Amazon Web Service (AWS) Canada region.","showcase":true,"start_date":"2022-07-27T00:00:00.000Z","id":"whpg3nhtgj0x","page_id":"4hr8rdym840d","group_id":"x8z7lpzf6cw4"}]},{"name":"Unable to change email message in scheduled exports inside Sigma reports","status":"resolved","created_at":"2026-09-21T16:34:54.826Z","updated_at":"2026-09-21T18:29:50.148Z","monitoring_at":"2026-09-21T18:25:11.536Z","resolved_at":"2026-09-21T18:29:50.132Z","impact":"none","shortlink":"https://stspg.io/w78ytsrlch0q","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-09-21T16:34:54.819Z","reminder_intervals":null,"id":"s4z1tnxb3mz3","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"The issue has now been fixed and users should be able to change the scheduled export email messages successfully now.","created_at":"2026-09-21T18:29:50.132Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-21T18:29:50.132Z","display_at":"2026-09-21T18:29:50.132Z","deliver_notifications":false,"tweet_id":null,"id":"mm76rgq1npc5","incident_id":"s4z1tnxb3mz3","custom_tweet":null,"affected_components":null},{"status":"monitoring","body":"We are continuing to monitor for any further issues.","created_at":"2026-09-21T18:28:26.347Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-21T18:28:26.347Z","display_at":"2026-09-21T18:28:26.347Z","deliver_notifications":false,"tweet_id":null,"id":"5m5kpmhgff69","incident_id":"s4z1tnxb3mz3","custom_tweet":null,"affected_components":null},{"status":"monitoring","body":"A fix has been implemented and we are monitoring the results now.","created_at":"2026-09-21T18:25:11.536Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-21T18:25:11.536Z","display_at":"2026-09-21T18:25:11.536Z","deliver_notifications":false,"tweet_id":null,"id":"w31ls5mr3s66","incident_id":"s4z1tnxb3mz3","custom_tweet":null,"affected_components":null},{"status":"identified","body":"The issue has been identified and a fix is being implemented by the Engineering team.","created_at":"2026-09-21T17:03:50.097Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-21T17:03:50.097Z","display_at":"2026-09-21T17:03:50.097Z","deliver_notifications":false,"tweet_id":null,"id":"pxn58k5g5j3g","incident_id":"s4z1tnxb3mz3","custom_tweet":null,"affected_components":null},{"status":"investigating","body":"We are investigating an issue with scheduled exports in reports where users are unable to change the email message. We are treating this as our highest priority. Our apologies for any inconvenience caused.\n\nImpacted Cloud Regions \u0026 Services: All regions\n\nUser Experience: Upon changing the scheduled export message, it reverts back to the default message. \n\nIncident Start Time: Approximately 15:43 UTC September 21, 2026","created_at":"2026-09-21T16:34:54.869Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-21T16:34:54.869Z","display_at":"2026-09-21T16:34:54.869Z","deliver_notifications":false,"tweet_id":null,"id":"20qfbck0k8x2","incident_id":"s4z1tnxb3mz3","custom_tweet":null,"affected_components":null}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[]},{"name":"Databricks Azure East US query timeout","status":"resolved","created_at":"2026-09-14T19:31:55.661Z","updated_at":"2026-09-14T22:53:03.176Z","monitoring_at":"2026-09-14T21:55:54.758Z","resolved_at":"2026-09-14T22:53:03.159Z","impact":"major","shortlink":"https://stspg.io/fxjbwj7s8x7c","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-09-14T19:31:55.656Z","reminder_intervals":null,"id":"2hs2qc5jpdc6","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"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. \n\nThis 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. \n\nWe apologize for the disruption and thank you for your patience.","created_at":"2026-09-14T22:53:03.159Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-14T22:53:03.159Z","display_at":"2026-09-14T22:53:03.159Z","deliver_notifications":true,"tweet_id":null,"id":"kvl1bn3cms5h","incident_id":"2hs2qc5jpdc6","custom_tweet":null,"affected_components":[{"code":"f754w346xp3s","name":"Azure - Sigma - Azure (US)","old_status":"partial_outage","new_status":"operational"}]},{"status":"monitoring","body":"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.\n\nThis 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/\n\nWe apologize for the disruption and thank you for your patience.","created_at":"2026-09-14T21:55:54.758Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-14T21:55:54.758Z","display_at":"2026-09-14T21:55:54.758Z","deliver_notifications":true,"tweet_id":null,"id":"4q57p5zd47gx","incident_id":"2hs2qc5jpdc6","custom_tweet":null,"affected_components":[{"code":"f754w346xp3s","name":"Azure - Sigma - Azure (US)","old_status":"partial_outage","new_status":"partial_outage"}]},{"status":"identified","body":"Databricks Azure East US is degraded services which is  affecting Sigma connections and causing query execution failures and timeouts on Databrick warehouse. \n\nWe 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. \nIf your Databrick connection in Sigma is experiencing errors, please continue monitoring: https://status.azuredatabricks.net/ \n\nWe apologize for the disruption and will keep this page updated.","created_at":"2026-09-14T21:19:26.330Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-14T21:19:26.330Z","display_at":"2026-09-14T21:19:26.330Z","deliver_notifications":true,"tweet_id":null,"id":"rzth80fvjprx","incident_id":"2hs2qc5jpdc6","custom_tweet":null,"affected_components":[{"code":"f754w346xp3s","name":"Azure - Sigma - Azure (US)","old_status":"operational","new_status":"partial_outage"}]},{"status":"identified","body":"Databricks Azure East US is degraded services which is  affecting Sigma connections and causing query execution failures and timeouts on Databrick warehouse. \n\nWe 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. \nIf your Databrick connection in Sigma is experiencing errors, please continue monitoring: https://status.azuredatabricks.net/ \n\nOur apologies for any inconvenience caused.","created_at":"2026-09-14T19:31:55.692Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-14T19:31:55.692Z","display_at":"2026-09-14T19:31:55.692Z","deliver_notifications":false,"tweet_id":null,"id":"j37mnq7zmvgc","incident_id":"2hs2qc5jpdc6","custom_tweet":null,"affected_components":null}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[{"status":"operational","name":"Sigma - Azure (US)","created_at":"2023-06-30T17:03:38.961Z","updated_at":"2026-09-26T16:08:30.249Z","position":1,"description":"System status tracking for Sigma organizations hosted on Microsoft Azure US region.","showcase":true,"start_date":"2023-04-15T00:00:00.000Z","id":"f754w346xp3s","page_id":"4hr8rdym840d","group_id":"50vclq2nhymf"}]},{"name":"Input Table Edits Failing if customer updated warehouse connection","status":"resolved","created_at":"2026-09-10T18:24:19.145Z","updated_at":"2026-09-11T22:01:46.613Z","monitoring_at":"2026-09-11T04:14:11.183Z","resolved_at":"2026-09-11T22:01:46.598Z","impact":"none","shortlink":"https://stspg.io/wcwq15r7xg4r","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-09-10T22:43:23.000Z","reminder_intervals":null,"id":"jqwn9m2bh02k","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"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.","created_at":"2026-09-11T22:01:46.598Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-11T22:01:46.598Z","display_at":"2026-09-11T22:01:46.598Z","deliver_notifications":false,"tweet_id":null,"id":"n9ply3pcksrm","incident_id":"jqwn9m2bh02k","custom_tweet":null,"affected_components":null},{"status":"monitoring","body":"We applied a mitigation and are monitoring its effect closely. Customers can now safely change warehouse connection auth method and make input table edits. \n\nWe'll share our next update in 4 hours. Thanks for your patience.","created_at":"2026-09-11T17:51:23.619Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-11T17:51:23.619Z","display_at":"2026-09-11T17:51:23.619Z","deliver_notifications":false,"tweet_id":null,"id":"88fnfd9m221n","incident_id":"jqwn9m2bh02k","custom_tweet":null,"affected_components":null},{"status":"monitoring","body":"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.","created_at":"2026-09-11T04:14:11.183Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-11T04:14:11.183Z","display_at":"2026-09-11T04:14:11.183Z","deliver_notifications":false,"tweet_id":null,"id":"q4dgzx3g74ds","incident_id":"jqwn9m2bh02k","custom_tweet":null,"affected_components":null},{"status":"identified","body":"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.\n\nWe apologize for the inconvenience and will continue to update this page as we make progress.","created_at":"2026-09-11T02:37:15.706Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-11T02:37:15.706Z","display_at":"2026-09-11T02:37:15.706Z","deliver_notifications":false,"tweet_id":null,"id":"28hlqljqkxnj","incident_id":"jqwn9m2bh02k","custom_tweet":null,"affected_components":null},{"status":"identified","body":"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. \n\nWe apologize for the inconvenience and will continue to update this page as we make progress!","created_at":"2026-09-11T00:37:01.125Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-11T00:46:27.670Z","display_at":"2026-09-11T00:37:01.000Z","deliver_notifications":false,"tweet_id":null,"id":"27w344v5zs0b","incident_id":"jqwn9m2bh02k","custom_tweet":null,"affected_components":null},{"status":"identified","body":"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. \n\nOur engineering team is now testing a fix in internal environments. we will continue to update the page as we make progress. \n\nThanks for your patience!","created_at":"2026-09-10T22:43:23.658Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-10T22:45:58.643Z","display_at":"2026-09-10T22:43:23.000Z","deliver_notifications":false,"tweet_id":null,"id":"w0pytvb7pdf8","incident_id":"jqwn9m2bh02k","custom_tweet":null,"affected_components":null},{"status":"identified","body":"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.\n\nWe apologize for the inconvenience and will continue to update this page as we make progress!","created_at":"2026-09-10T19:18:04.110Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-10T19:18:04.110Z","display_at":"2026-09-10T19:18:04.110Z","deliver_notifications":false,"tweet_id":null,"id":"clxkwjzm0jgb","incident_id":"jqwn9m2bh02k","custom_tweet":null,"affected_components":null},{"status":"identified","body":"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.\n\nImpact: Some customers are unable to save edits to existing input tables on affected connections.\n\nNext 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.\n\nWe apologize for the inconvenience and will continue to update this page as we make progress!","created_at":"2026-09-10T18:24:19.198Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-10T18:24:19.198Z","display_at":"2026-09-10T18:24:19.198Z","deliver_notifications":false,"tweet_id":null,"id":"m033fwqcdlx6","incident_id":"jqwn9m2bh02k","custom_tweet":null,"affected_components":null}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[]},{"name":"Scheduled Materialization and Export Failures","status":"resolved","created_at":"2026-09-02T13:37:26.466Z","updated_at":"2026-09-02T13:37:26.531Z","monitoring_at":null,"resolved_at":"2026-09-02T13:37:26.520Z","impact":"none","shortlink":"https://stspg.io/r6d19lv7p6dk","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-09-02T13:37:26.454Z","reminder_intervals":null,"id":"dc3xdgdz224t","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"We received reports of errors causing scheduled materializations and exports to fail.\nThis 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.\n\nImpacted Cloud Regions \u0026 Services:  azure:production:eastus2 and aws:us-west-2\n\nUser 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.\n\nIncident Start Time: Approximately 12:02 PM UTC\nIncident End Time: Approximately 1:01PM UTC","created_at":"2026-09-02T13:37:26.520Z","wants_twitter_update":false,"twitter_updated_at":null,"updated_at":"2026-09-02T13:37:26.520Z","display_at":"2026-09-02T13:37:26.520Z","deliver_notifications":true,"tweet_id":null,"id":"kmbt3xrpbqbc","incident_id":"dc3xdgdz224t","custom_tweet":null,"affected_components":[{"code":"6hfstyp7zpd3","name":"AWS - Sigma - AWS (US)","old_status":"operational","new_status":"operational"},{"code":"f754w346xp3s","name":"Azure - Sigma - Azure (US)","old_status":"operational","new_status":"operational"}]}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[{"status":"operational","name":"Sigma - AWS (US)","created_at":"2021-08-05T20:09:19.522Z","updated_at":"2026-11-09T21:58:19.804Z","position":1,"description":"System status tracking for Sigma organizations hosted on Amazon Web Service (AWS) US region.","showcase":true,"start_date":"2021-08-05T00:00:00.000Z","id":"6hfstyp7zpd3","page_id":"4hr8rdym840d","group_id":"x8z7lpzf6cw4"},{"status":"operational","name":"Sigma - Azure (US)","created_at":"2023-06-30T17:03:38.961Z","updated_at":"2026-09-26T16:08:30.249Z","position":1,"description":"System status tracking for Sigma organizations hosted on Microsoft Azure US region.","showcase":true,"start_date":"2023-04-15T00:00:00.000Z","id":"f754w346xp3s","page_id":"4hr8rdym840d","group_id":"50vclq2nhymf"}]},{"name":"Widespread failures are preventing Sigma from loading for GCP-hosted organizations.","status":"resolved","created_at":"2026-09-01T15:34:55.000Z","updated_at":"2026-09-08T17:59:24.891Z","monitoring_at":"2026-09-01T16:23:18.000Z","resolved_at":"2026-09-01T16:55:18.059Z","impact":"critical","shortlink":"https://stspg.io/pmd7gw49xwkk","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-09-01T15:34:55.000Z","reminder_intervals":null,"id":"8ttp4ncqt8lp","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"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.\n\nImpacted Cloud Regions \u0026 Services: Sigma users hosted on GCP\n\nUser Experience: GCP-hosted users will be able to load Sigma, open workbooks, or render reports without any issues.\n\nIncident Start Time: Approximately 02:46 PM UTC Sep 1, 2026\nIncident End Time: Approximately 05:29 PM UTC Sep1, 2026","created_at":"2026-09-01T16:55:18.059Z","wants_twitter_update":true,"twitter_updated_at":null,"updated_at":"2026-09-01T16:55:18.059Z","display_at":"2026-09-01T16:55:18.059Z","deliver_notifications":true,"tweet_id":null,"id":"fwm0v8d7356h","incident_id":"8ttp4ncqt8lp","custom_tweet":null,"affected_components":[{"code":"c2ftyy6cgk24","name":"GCP - Sigma - GCP (US)","old_status":"degraded_performance","new_status":"operational"}]},{"status":"monitoring","body":"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.\n\nImpacted Cloud Regions \u0026 Services: Sigma users hosted on GCP\n\nUser Experience: We expect GCP-hosted users starting to be able to load Sigma, open workbooks, or render reports fine\n\nIncident Start Time: Approximately 02:46 UTC Sep 1, 2026","created_at":"2026-09-01T16:23:18.867Z","wants_twitter_update":true,"twitter_updated_at":null,"updated_at":"2026-09-01T16:28:09.811Z","display_at":"2026-09-01T16:23:18.000Z","deliver_notifications":true,"tweet_id":null,"id":"dtk1kb2t8vtt","incident_id":"8ttp4ncqt8lp","custom_tweet":null,"affected_components":[{"code":"c2ftyy6cgk24","name":"GCP - Sigma - GCP (US)","old_status":"major_outage","new_status":"degraded_performance"}]},{"status":"investigating","body":"We have received reports of errors causing users to be unable to utilize all portions of the Sigma application.\nWe are investigating the issue at the highest priority.\n\nOur preliminary investigations indicate the following:\nImpacted Cloud Regions \u0026 Services: organization hosted on GCP\nUser Experience: Unable to load Sigma\nIncident Start Time: Approximately 2:46 PM UTC\n\nWe will provide updates on this page in the next 1 hour.","created_at":"2026-09-01T15:34:55.391Z","wants_twitter_update":true,"twitter_updated_at":null,"updated_at":"2026-09-01T16:27:58.970Z","display_at":"2026-09-01T15:34:55.000Z","deliver_notifications":true,"tweet_id":null,"id":"0vvxvzyjjbtz","incident_id":"8ttp4ncqt8lp","custom_tweet":null,"affected_components":[{"code":"c2ftyy6cgk24","name":"GCP - Sigma - GCP (US)","old_status":"operational","new_status":"major_outage"}]}],"postmortem_body":"**Incident date:** September 1, 2026  \n**Duration:** Approximately 90 minutes  \n**Affected service:** Sigma organizations hosted in Google Cloud Platform \\(GCP\\) us-central1  \n\n## Summary\n\nOn September 1, a Google Cloud networking incident in part of the us-central1 region interrupted connectivity to Sigma services. Customers hosted in GCP us-central1 were unable to reliably access the Sigma application, administration UI, workbooks, and some embedded experiences. No Sigma code or configuration change triggered the incident.  \n\n## Root cause\n\nDuring routine maintenance, Google Cloud experienced a network failure in part of the us-central1-b zone. Sigma services in the region had a non-redundant network dependency in the affected zone, so a zone-scoped failure caused a broader service disruption for customers hosted in the region. See the [Google Cloud incident report](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev) for details about the cloud provider event.  \n\n## Resolution\n\nGoogle Cloud restored the underlying network service, and Sigma recovered without a Sigma-side deployment. Customers did not need to make changes to resume using Sigma.  \n\n## Corrective actions\n\nSigma is taking the following actions:  \n\n* Increase network redundancy across affected Sigma services in this region. Other regions are not impacted by the same deficiency as that in us-central1.\n* Add additional production health monitoring that operates independently of the environment it monitors.\n* Improve zone-level availability monitoring and alerting for external status pages.\n* Improve retry and recovery behavior for background workloads \\(including materialization\\) during transient network failures.\n\nWe apologize for the disruption and are using this incident to improve the resilience and independent detection of Sigma services.","postmortem_body_last_updated_at":"2026-09-08T17:59:24.871Z","postmortem_ignored":false,"postmortem_published_at":"2026-09-08T17:59:24.871Z","postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[{"status":"operational","name":"Sigma - GCP (US)","created_at":"2020-04-17T17:42:13.607Z","updated_at":"2026-09-26T16:08:30.233Z","position":1,"description":"System status tracking for Sigma organizations hosted on Google Cloud Platform (GCP) US region.","showcase":true,"start_date":null,"id":"c2ftyy6cgk24","page_id":"4hr8rdym840d","group_id":"9r4w7gjmsl4s"}]},{"name":"Exports displayed number and date columns as text in Excel and Google Sheets","status":"resolved","created_at":"2026-09-01T04:00:55.000Z","updated_at":"2026-09-02T19:07:17.306Z","monitoring_at":null,"resolved_at":"2026-09-01T04:00:55.000Z","impact":"none","shortlink":"https://stspg.io/2qt4b848lscd","scheduled_for":null,"scheduled_until":null,"scheduled_remind_prior":false,"scheduled_reminded_at":null,"impact_override":null,"scheduled_auto_in_progress":false,"scheduled_auto_completed":false,"metadata":{},"started_at":"2026-09-01T04:00:55.000Z","reminder_intervals":null,"id":"d33g04w6z61d","page_id":"4hr8rdym840d","incident_updates":[{"status":"resolved","body":"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. \n\nThe 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.\n\nTimeline\nIncident start time: August 28, approximately 11:47 PM UTC\nIncident end time: September 1, approximately 4:09 PM UTC","created_at":"2026-09-02T18:56:55.703Z","wants_twitter_update":true,"twitter_updated_at":null,"updated_at":"2026-09-02T19:07:17.188Z","display_at":"2026-09-01T04:00:55.000Z","deliver_notifications":false,"tweet_id":null,"id":"tc4q7y451ctd","incident_id":"d33g04w6z61d","custom_tweet":null,"affected_components":null}],"postmortem_body":null,"postmortem_body_last_updated_at":null,"postmortem_ignored":false,"postmortem_published_at":null,"postmortem_notified_subscribers":false,"postmortem_notified_twitter":false,"components":[]}]
}