Sep <var data-var='date'>26</var>, <var data-var='time'>16:11</var> UTC Resolved - 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 Sep <var data-var='date'>26</var>, <var data-var='time'>16:08</var> UTC Update - 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 Sep <var data-var='date'>26</var>, <var data-var='time'>15:25</var> 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.

Export Failures Incident

Sep <var data-var='date'>21</var>, <var data-var='time'>18:29</var> UTC Resolved - The issue has now been fixed and users should be able to change the scheduled export email messages successfully now. Sep <var data-var='date'>21</var>, <var data-var='time'>18:28</var> UTC Update - We are continuing to monitor for any further issues. Sep <var data-var='date'>21</var>, <var data-var='time'>18:25</var> UTC Monitoring - A fix has been implemented and we are monitoring the results now. Sep <var data-var='date'>21</var>, <var data-var='time'>17:03</var> UTC Identified - The issue has been identified and a fix is being implemented by the Engineering team. Sep <var data-var='date'>21</var>, <var data-var='time'>16:34</var> UTC Investigating - 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. Impacted Cloud Regions & Services: All regions User Experience: Upon changing the scheduled export message, it reverts back to the default message. Incident Start Time: Approximately 15:43 UTC September 21, 2026

Unable to change email message in scheduled exports inside Sigma reports

Sep <var data-var='date'>14</var>, <var data-var='time'>22:53</var> UTC 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 <var data-var='date'>14</var>, <var data-var='time'>21:55</var> 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 <var data-var='date'>14</var>, <var data-var='time'>21:19</var> 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 <var data-var='date'>14</var>, <var data-var='time'>19:31</var> 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.

Databricks Azure East US query timeout

Sep <var data-var='date'>11</var>, <var data-var='time'>22:01</var> UTC 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 <var data-var='date'>11</var>, <var data-var='time'>17:51</var> 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 <var data-var='date'>11</var>, <var data-var='time'>04:14</var> 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 <var data-var='date'>11</var>, <var data-var='time'>02:37</var> 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 <var data-var='date'>11</var>, <var data-var='time'>00:37</var> 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 <var data-var='date'>10</var>, <var data-var='time'>22:43</var> 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 <var data-var='date'>10</var>, <var data-var='time'>19:18</var> 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 <var data-var='date'>10</var>, <var data-var='time'>18:24</var> 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!

Input Table Edits Failing if customer updated warehouse connection

Sep <var data-var='date'> 2</var>, <var data-var='time'>13:37</var> UTC 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

Scheduled Materialization and Export Failures

Sep <var data-var='date'> 1</var>, <var data-var='time'>16:55</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>16:23</var> 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 <var data-var='date'> 1</var>, <var data-var='time'>15:34</var> 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.

Widespread failures are preventing Sigma from loading for GCP-hosted organizations.

Sep <var data-var='date'> 1</var>, <var data-var='time'>04:00</var> UTC 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

Exports displayed number and date columns as text in Excel and Google Sheets

Aug <var data-var='date'>11</var>, <var data-var='time'>17:32</var> UTC Resolved - Status: 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 Time: Aug 5, 2026, 15:37 UTC Incident End Time: Aug 11, 2026, 14:47 UTC Aug <var data-var='date'>11</var>, <var data-var='time'>04:18</var> UTC 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. Aug <var data-var='date'>10</var>, <var data-var='time'>22:52</var> UTC Update - 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. Aug <var data-var='date'>10</var>, <var data-var='time'>18:37</var> UTC 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

Delayed audit logs and usage data in AWS US West

Aug <var data-var='date'> 5</var>, <var data-var='time'>03:19</var> UTC Resolved - The 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 inconvenience this may have caused. Impacted Cloud Regions & Services: Sigma users hosted on AWS US-West-2 using materialization User Experience: Customers using materializations on AWS US-West-2 should no longer see the previously reported table accumulation. Incident Start Time: Approximately August 3, 2026, at 2:44 PM UTC Incident End Time: Approximately August 5, 2026, at 02:40 AM UTC Aug <var data-var='date'> 5</var>, <var data-var='time'>00:20</var> UTC 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 clears; no new action is needed. Incident Start Time: Approximately August 3, 2026, at 2:44:18 PM UTC Aug <var data-var='date'> 4</var>, <var data-var='time'>23:58</var> UTC 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 AWS US-West-2 may see stale materialization tables accumulating in their connected warehouse, which over time could approach warehouse storage/object limits. Incident Start Time: Approximately August 3, 2026, at 2:44:18 PM UTC

Materialization cleanup delayed for Sigma users on AWS US-West-2

Aug <var data-var='date'> 4</var>, <var data-var='time'>11:11</var> UTC Resolved - Sigma 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 our findings in a postmortem note on the Sigma Community site in the coming days. Impacted Cloud Regions & Services: All Regions User Experience: Workbooks should now load normally after a hard refresh or browser restart. Incident Start Time: Approximately 08:30 UTC, August 4, 2026 Incident End Time: Approximately 10:42 UTC, August 4, 2026 Aug <var data-var='date'> 4</var>, <var data-var='time'>10:37</var> UTC 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. Incident Start Time: Approximately 08:30 UTC, August 4, 2026

Workbooks containing Snowflake Semantic Views fail to load

Aug <var data-var='date'> 3</var>, <var data-var='time'>18:07</var> UTC Resolved - Resolved - 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 update, this issue has now been resolved. Incident end time: 16:36 UTC August 03, 2026 Aug <var data-var='date'> 3</var>, <var data-var='time'>17:38</var> UTC 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 Aug <var data-var='date'> 3</var>, <var data-var='time'>15:26</var> UTC 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. Aug <var data-var='date'> 3</var>, <var data-var='time'>14:55</var> UTC 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.

Query Timeouts for Snowflake Connections

Jun <var data-var='date'>24</var>, <var data-var='time'>19:35</var> UTC Resolved - The mitigation measures have proven effective, and our monitoring indicates that this issue is resolved. We will continue monitoring closely this incident for any recurrence in the next hours. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in the coming days. Impacted Cloud Regions & Services: AWS US-WEST-2 User Experience: We expect users to no longer experience delayed scheduled exports and materializations. Users should have received previously delayed scheduled exports and delayed materializations should have ran. Incident Start Time: Approximately 05:00 UTC June 24, 2026 Incident End Time: Approximately 17:30 UTC June 24, 2026 Jun <var data-var='date'>24</var>, <var data-var='time'>16:53</var> UTC Update - 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 Jun <var data-var='date'>24</var>, <var data-var='time'>14:53</var> UTC 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 meantime. Incident Start Time: Approximately 05:00 UTC June 24, 2026 Jun <var data-var='date'>24</var>, <var data-var='time'>13:30</var> UTC 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 this page when we have pertinent status updates.

Scheduled exports and materializations are delayed

Jun <var data-var='date'>22</var>, <var data-var='time'>18:52</var> UTC Resolved - We 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 our monitoring indicates that this 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 the coming days. Impacted Cloud Regions & Services: AWS US-WEST-2 User Experience: We expect users to no longer experience workbook errors. Incident Start Time: Approximately 17:30 UTC June 22, 2026 Incident End Time: Approximately 18:14 UTC June 22, 2026 Jun <var data-var='date'>22</var>, <var data-var='time'>18:11</var> UTC 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.

High errors showing being displayed in workbooks

May <var data-var='date'>15</var>, <var data-var='time'>13:49</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>15</var>, <var data-var='time'>01:21</var> UTC Identified - Users are experiencing elevated errors when exporting pivot tables, with the error message "Column alias not found".

Errors on pivot table export

Apr <var data-var='date'> 8</var>, <var data-var='time'>23:39</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'> 8</var>, <var data-var='time'>23:30</var> UTC Investigating - The permission denied issue got resolved Impacted Cloud Regions & Services: All regions User Experience: Users get permission denied error in the workbook Incident Start Time: Approximately 2:00PM UTC April 08, 2026

Permission Denied Errors on Elements Sourced from Custom SQL Tables

Apr <var data-var='date'> 1</var>, <var data-var='time'>03:30</var> UTC 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. 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 Mar <var data-var='date'>31</var>, <var data-var='time'>21:50</var> UTC 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 Mar <var data-var='date'>31</var>, <var data-var='time'>21:08</var> UTC 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

Experiencing issues with Google sheets Integration

Mar <var data-var='date'> 9</var>, <var data-var='time'>17:31</var> UTC Resolved - Issue with Burst Email Exports are resolved We previously re-enabled Burst Email Exports after deploying a fix for the issue impacting this feature. Since re-enabling, our team has closely monitored system performance and error rates, and we have not observed any recurring problems. At this time, the incident is considered fully resolved, and Burst Email Exports are operating as expected. If you encounter any new or unexpected behavior with Burst Email Exports, please contact our support team via live chat so we can investigate promptly. Mar <var data-var='date'> 7</var>, <var data-var='time'>01:27</var> UTC Monitoring - Burst Email Exports have now been re-enabled. Our engineering team has identified and deployed a fix for the issue affecting Email Burst Exports. Following thorough internal validation and testing, we have re-enabled the feature and will continue monitoring performance closely. If you experience any further issues with Burst Email Exports, please reach out to our support team via live chat. Mar <var data-var='date'> 7</var>, <var data-var='time'>01:22</var> UTC Update - We are continuing to work on a fix for this issue. Mar <var data-var='date'> 6</var>, <var data-var='time'>20:28</var> UTC Identified - Burst email exports remain unavailable. We have deployed a fix and are currently validating it internally. Standard (non-burst) exports remain fully operational. We will provide further updates as validation progresses and before re-enabling burst email exports more broadly. Thank you for your patience. Mar <var data-var='date'> 6</var>, <var data-var='time'>10:26</var> UTC Update - Internal validation tests are ongoing and we will share further updates as we have them. Standard (non-burst) exports remain fully operational and are unaffected. Thank you for your continued patience. Impact on Customers: Burst email exports remain temporarily unavailable while the investigation is ongoing. Mar <var data-var='date'> 6</var>, <var data-var='time'>06:06</var> UTC Update - Our engineering team has deployed a fix and is currently validating it internally. Standard (non-burst) exports remain fully operational and are unaffected. We will share a further update as validation progresses Thank you for your continued patience. Impact on Customers: Burst email exports remain temporarily unavailable while the investigation is ongoing. Mar <var data-var='date'> 6</var>, <var data-var='time'>00:36</var> UTC Update - Our engineers are actively investigating the on-going issue with burst email exports. We appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing. Mar <var data-var='date'> 5</var>, <var data-var='time'>21:33</var> UTC Update - Our engineers are actively investigating the on-going issue with burst email exports. We appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing. Mar <var data-var='date'> 5</var>, <var data-var='time'>18:33</var> UTC Update - Our engineers are actively investigating the on-going issue with burst email exports. We appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing. Mar <var data-var='date'> 5</var>, <var data-var='time'>10:10</var> UTC Update - Our engineers are continuing to investigate the burst email exports issue. We appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing. Mar <var data-var='date'> 5</var>, <var data-var='time'>05:31</var> UTC Update - Our engineers are actively investigating the on-going issue with burst email exports. We understand the impact this has on your workflows and appreciate your patience. Impact on customers: This feature will remain unavailable while the investigation is ongoing. Mar <var data-var='date'> 5</var>, <var data-var='time'>01:27</var> UTC Update - Our engineers are actively investigating the issue with burst email exports. This feature will remain paused until the root cause. We will update this status with new developments as soon as they become available. Mar <var data-var='date'> 4</var>, <var data-var='time'>22:25</var> UTC Update - Our engineers are still investigating the issue with burst email exports. This feature will remain paused until investigation has identified the root cause. We apologize for the inconvenience and we will update this status with new developments as soon as they become available. Mar <var data-var='date'> 4</var>, <var data-var='time'>20:50</var> UTC Investigating - We have temporarily paused burst email exports to investigate a technical issue. Status: Burst exports are unavailable. Unaffected: Standard exports are fully operational. We will update this notification with new developments.

Issue with Burst email exports are resolved

Jan <var data-var='date'> 9</var>, <var data-var='time'>22:23</var> UTC Resolved - Our 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 incident as resolved as well. Again we apologize for the inconvenience this has caused, and appreciate your understanding. Jan <var data-var='date'> 9</var>, <var data-var='time'>21:18</var> UTC Monitoring - Our 3rd party system has updated their incident saying a fix has been implemented. Sigma support team has noticed that the chat application is currently online and our Support Engineers are online but we will continue monitoring for any up new development. Jan <var data-var='date'> 9</var>, <var data-var='time'>21:15</var> UTC Investigating - We are continuing to investigate this issue. Jan <var data-var='date'> 9</var>, <var data-var='time'>21:12</var> UTC Monitoring - Our 3rd party system has updated their incident saying a fix has been implemented. Sigma support team has noticed that the chat application is currently online and our Support Engineers are online but we will continue monitoring for any up new development. Jan <var data-var='date'> 9</var>, <var data-var='time'>20:33</var> UTC Investigating - Our 3rd party chat system Intercom is currently experiencing an outage as listed here https://www.intercomstatus.com/us-hosting. If you have an urgent request that requires immediate attention while this outage is ongoing, please go to https://support.sigmacomputing.com and press "Submit a Request" to submit a ticket. Expect response times being slower than usual. We apologize for this inconvenience and will update this page as the situation develops.

Chat Support experiencing 3rd party outage

Jan <var data-var='date'> 5</var>, <var data-var='time'>23:33</var> UTC Resolved - This incident has been resolved. The queued tasks should start recovering automatically Jan <var data-var='date'> 5</var>, <var data-var='time'>23:13</var> UTC Monitoring - A fix has been implemented and we are monitoring the results Jan <var data-var='date'> 5</var>, <var data-var='time'>21:38</var> UTC Investigating - We are currently investigating an issue affecting scheduled exports, materializations, and warehouse view updates on AWS US

Scheduled Backend Tasks not running on AWS US

Dec <var data-var='date'>11</var>, <var data-var='time'>18:17</var> UTC Resolved - We have identified that PDF export failures were impacting a small percentage of our users. We applied mitigation steps and our monitoring indicates that this issue has been resolved. We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in the coming days. Impacted Cloud Regions & Services: AWS US and GCP US regions, PDF Exports User Experience: We expect impacted users' scheduled exports to succeed without the errors seen previously Incident Start Time: Approximately 13:00 UTC on 2025-12-11 Incident End Time: Approximately 17:50 UTC on 2025-12-11 Dec <var data-var='date'>11</var>, <var data-var='time'>17:29</var> UTC Update - We are continuing to investigate the issue at the highest priority. We will provide updates on this page when we have pertinent status updates. Dec <var data-var='date'>11</var>, <var data-var='time'>16:21</var> UTC Investigating - We have received reports of errors causing PDF exports to fail. We are investigating the issue at the highest priority. Our preliminary investigations indicate the following: Impacted Cloud Regions & Services: AWS US and GCP US regions, PDF Exports User Experience: Timeout errors causing PDF export failures Incident Start Time: Approximately 13:00 UTC on 2025-12-11 We will provide updates on this page when we have pertinent status updates.

Degraded performance on PDF Exports

Dec <var data-var='date'> 5</var>, <var data-var='time'>09:00</var> UTC Resolved - At 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 incident, as this did not allow traffic to reach our servers. Our internal monitoring matches the incident timeline and indicated that customers may have experienced failures when using our services during this brief incident.

Sigma Service Disruption Due to Cloudflare Incident

Oct <var data-var='date'>29</var>, <var data-var='time'>22:29</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>29</var>, <var data-var='time'>16:57</var> UTC Monitoring - We are currently investigating a partial service disruption affecting Azure-hosted customers. Users may notice issues with loading, displaying, or uploading images and other custom assets. Initial reports suggest this appears to be caused by an Azure CDN outage. We are actively monitoring the situation.

Service disruption affecting Azure-hosted customers

Oct <var data-var='date'>20</var>, <var data-var='time'>07:00</var> UTC Resolved - Starting at 7:11 UTC, AWS reported increased error rates and latencies for multiple services in the US-EAST-1 Region. At 10:35 UTC, AWS declared the incident in the US-EAST-1 region mitigated. While Sigma's service was not impacted by the incident, third party services that Sigma uses were impacted. Customers may have experienced intermittent delays or failures when accessing or using cloud data warehouse services during the incident. Contacting Sigma Support via Live Chat or email was disrupted during the incident. Incident Start Time: 7:11 UTC Incident End Time: 10:35 UTC

Error rates and latencies in the AWS US-EAST-1 Region impacting third party services

Sep <var data-var='date'>21</var>, <var data-var='time'>06:37</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>21</var>, <var data-var='time'>03:43</var> UTC Update - We are continuing to monitor for any further issues. Sep <var data-var='date'>21</var>, <var data-var='time'>03:42</var> UTC Monitoring - The issue is now mitigated. All Azure users should be able to log into Sigma without issue at this time. Sep <var data-var='date'>21</var>, <var data-var='time'>02:56</var> UTC Investigating - We are investigating an issue with Sigma organizations hosted on Azure that impacts login. We are treating this as our highest priority. Our apologies for any inconvenience caused. User Experience: Login page does not load

Outage affecting Sigma organizations hosted on Azure

Jun <var data-var='date'>12</var>, <var data-var='time'>21:25</var> UTC Resolved - Status: Resolved Update: Sigma services affected by the Google GCP outage have fully recovered at this time. Incident Start Time: Approximately 17:55 UTC June 12, 2025 Incident End Time: Approximately 20:45 UTC June 12, 2025 Jun <var data-var='date'>12</var>, <var data-var='time'>21:04</var> UTC Update - Update: All Sigma customers should be able to resume using Sigma at this time. We are seeing our services operating normally at this time. Note: Google has not fully resolved the outage so customers may encounter errors intermittently. Incident Start Time: Approximately 17:55 UTC June 12, 2025 Incident End Time: Approximately 20:45 UTC June 12, 2025 Jun <var data-var='date'>12</var>, <var data-var='time'>20:12</var> UTC Monitoring - Update: GCP is still not fully recovered (https://status.cloud.google.com/). A number of services and providers are also on the path to recovery and we are starting to see services recover but are continuing to monitor closely. User Experience: Users should expect the decreased errors for affected sigma organizations. Incident Start Time: Approximately 17:55 UTC June 12, 2025 Jun <var data-var='date'>12</var>, <var data-var='time'>18:58</var> UTC Investigating - GCP Outage affecting Sigma organizations hosted on multiple cloud providers We are investigating an issue with Sigma organizations hosted on GCP experiencing errors owing to GCP outage (https://status.cloud.google.com/). A number of services and providers we use are also down so there may be some impact in other cloud providers as well. We are treating this as our highest priority. Our apologies for any inconvenience caused. User Experience: Increased error rates when performing regular operations. Incident Start Time: Approximately 17:55 UTC June 12, 2025

Is Sigma Computing down?

Sigma Computing status is UP

Lastest published events

Export Failures Incident

Unable to change email message in scheduled exports inside Sigma reports

Databricks Azure East US query timeout

Sigma Computing Services, Components and Regions

Recent Sigma Computing events

Export Failures Incident

Unable to change email message in scheduled exports inside Sigma reports

Databricks Azure East US query timeout

Input Table Edits Failing if customer updated warehouse connection

Scheduled Materialization and Export Failures

Widespread failures are preventing Sigma from loading for GCP-hosted organizations.