Stigg incident

Issues creating subscriptions

Minor Resolved View vendor source →
Started
Mar 02, 2026, 12:48 PM UTC
Resolved
Mar 02, 2026, 12:48 PM UTC
Duration
Detected by Pingoru
Mar 02, 2026, 12:48 PM UTC

Update timeline

  1. 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.

  2. 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.

  3. 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.

Looking to track Stigg downtime and outages?

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

  • Real-time alerts when Stigg reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Stigg alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Stigg for free

5 free monitors · No credit card required