Sigma Computing experienced a 42-minute incident on June 22, 2026 (approximately 17:30–18:14 UTC) in which users on the AWS US-WEST-2 region encountered "An error has occurred" messages when loading workbook elements. The root cause was an abnormal spike in CPU usage on Sigma's AWS infrastructure. The issue was resolved by scaling infrastructure to handle the increased load, with a full postmortem to be published to the Sigma Community site.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with