Sigma Computing experienced a ~12.5-hour incident on June 24, 2026 (05:00–17:30 UTC) in which scheduled exports and materializations failed to execute on time in the AWS US-WEST-2 region. The root cause was slow-running database queries that caused a backlog of scheduled tasks. Engineers applied mitigation measures to clear the backlog, after which delayed exports and materializations were processed and normal scheduling resumed.
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.
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
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
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
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.
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