Stigg Outage History

There were 3 Stigg outages since February 4, 2026. Each is summarised below — incident details, duration, and resolution information.

Minor March 23, 2026

Degraded UI functionality – navigation unavailable

Affected: Stigg app

Timeline · 4 updates

investigating Mar 23, 2026, 01:23 PM UTC

Status: Investigating Some of our customers are experiencing issues accessing the Stigg UI. We are actively investigating and will provide updates as soon as possible. Affected components Stigg app (Partial outage)
identified Mar 23, 2026, 01:42 PM UTC

Status: Identified We’ve identified that the issue is caused by our authorization provider and is impacting customers using RBAC. We are actively monitoring the situation and will share updates as soon as more information becomes available. Affected components Stigg app (Partial outage)
monitoring Mar 23, 2026, 03:24 PM UTC

Status: Monitoring Our authorization provider has deployed a fix and access is gradually being restored. We are actively monitoring the status and will continue to provide updates as needed. Affected components Stigg app (Degraded performance)
resolved Mar 23, 2026, 04:42 PM UTC

Status: Resolved The issue has been resolved and access has been restored for affected customers. Affected components Stigg app (Operational)

Minor March 2, 2026

Timeline · 3 updates

investigating Mar 02, 2026, 10:03 AM UTC

Status: Investigating 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

Status: Monitoring 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

Status: Resolved 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.

Minor February 4, 2026

Affected: API

Timeline · 2 updates

monitoring Feb 04, 2026, 03:59 PM UTC

Status: Monitoring Between 3:14 PM and 3:38 PM UTC, we experienced a period of degraded performance with our API. The root cause has been addressed, and system performance has returned to normal. we are continuing to monitor the situation closely Affected components API (Degraded performance)
resolved Feb 04, 2026, 04:22 PM UTC

Status: Resolved Issue has been resolved. The system is now fully operational. Affected components API (Operational)

Pingoru polls Stigg's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

5 free monitors · No credit card required