Resolved after 2 hours 44 minutes, on March 2, 2026.
We have identified the root cause of the issue, and all operations have returned to normal. The incident was caused by an issue with underlying AWS components. We are exploring solutions for the subscriptions that were affected and we will continue to monitor the system to ensure stability.
Update timeline
- investigating Mar 02, 2026, 10:03 AM UTC
Users are reporting issues with subscription creation and update. We're actively investigating the situation Update (11:20AM UTC): We're actively exploring a potential lead or the root cause. In parallel, we’re assessing immediate mitigation steps to stabilize the situation and reduce the ongoing impact.
- monitoring Mar 02, 2026, 12:47 PM UTC
We have identified the root cause of the issue, and all operations have returned to normal. The incident was caused by an issue with underlying AWS components. We are exploring solutions for the subscriptions that were affected and we will continue to monitor the system to ensure stability.
- resolved Mar 02, 2026, 12:48 PM UTC
We have identified the root cause of the issue, and all operations have returned to normal. The incident was caused by an issue with underlying AWS components. We are exploring solutions for the subscriptions that were affected and we will continue to monitor the system to ensure stability.
Your product runs on more than Stigg
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