Sigma Computing incident
Issues with production services accessing databases on Sigma AWS
Resolved after 1 hour 5 minutes, affecting Sigma - AWS (US), on May 21, 2024.
At approximately 17:22 UTC, we had applied an erroneous network security change which prevented incoming network connections to our services. This was detected by our internal monitors and we quickly reverted it at 17:26 UTC. Customers on AWS us-west-2 may have experienced intermittent slowness or erroring queries in loading their workbooks during that time. The mitigation measures have proven effective, and the issue is resolved. Incident Start Time: Approximately 17:22 UTC Incident End Time: Approximately 18:27 UTC We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.
Affected components
Update timeline
- resolved May 21, 2024, 06:51 PM UTC
At approximately 17:22 UTC, we had applied an erroneous network security change which prevented incoming network connections to our services. This was detected by our internal monitors and we quickly reverted it at 17:26 UTC. Customers on AWS us-west-2 may have experienced intermittent slowness or erroring queries in loading their workbooks during that time. The mitigation measures have proven effective, and the issue is resolved. Incident Start Time: Approximately 17:22 UTC Incident End Time: Approximately 18:27 UTC We will perform a root cause analysis (RCA) and publish our findings in a postmortem note to the Sigma Community site in coming days.
Your product runs on more than Sigma Computing
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services