Stigg Outage History

Stigg is up right now

Stigg had 13 outages in the last 2 years totaling 25h 5m of downtime — averaging 0.5 incidents per month.

There were 13 Stigg outages since October 17, 2025 totaling 25h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.stigg.io

Minor September 30, 2026

Increased API response times

Detected by Pingoru
Sep 30, 2026, 01:10 PM UTC
Resolved
Sep 30, 2026, 02:00 PM UTC
Duration
50m
Affected: API
Timeline · 2 updates
  1. identified Sep 30, 2026, 01:10 PM UTC

    Status: Identified Since 12:20 UTC, some requests to the Stigg API and SDKs are responding slower than usual. Our team is actively investigating and working on a fix. We will share an update as soon as we have more information. Affected components API (Degraded performance)

  2. resolved Sep 30, 2026, 02:00 PM UTC

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

Read the full incident report →

Minor September 14, 2026

edge api degraded performance

Detected by Pingoru
Sep 14, 2026, 01:40 PM UTC
Resolved
Sep 14, 2026, 02:14 PM UTC
Duration
33m
Affected: Edge API
Timeline · 4 updates
  1. investigating Sep 14, 2026, 01:40 PM UTC

    Status: Investigating We noticed failures to retrieve data from our edge-api Affected components Edge API (Partial outage)

  2. identified Sep 14, 2026, 01:59 PM UTC

    Status: Identified Root cause has been identified. Affected components Edge API (Partial outage)

  3. monitoring Sep 14, 2026, 02:13 PM UTC

    Status: Monitoring A fix has been deployed, and we're continue monitoring. Affected components Edge API (Partial outage)

  4. resolved Sep 14, 2026, 02:14 PM UTC

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

Read the full incident report →

Minor September 11, 2026

Delayed processing of billing provider events

Detected by Pingoru
Sep 11, 2026, 09:38 AM UTC
Resolved
Sep 11, 2026, 01:18 PM UTC
Duration
3h 40m
Affected: API
Timeline · 2 updates
  1. investigating Sep 11, 2026, 09:38 AM UTC

    Status: Investigating Billing events are not being processed. Some subscription updates and checkout attempts may fail. Affected components API (Partial outage)

  2. resolved Sep 11, 2026, 01:18 PM UTC

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

Read the full incident report →

Minor August 26, 2026

Elevated API errors

Detected by Pingoru
Aug 26, 2026, 02:41 PM UTC
Resolved
Aug 26, 2026, 08:31 PM UTC
Duration
5h 50m
Affected: API
Timeline · 2 updates
  1. identified Aug 26, 2026, 02:41 PM UTC

    Status: Identified Root cause has been identified. Affected components API (Partial outage)

  2. resolved Aug 26, 2026, 08:31 PM UTC

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

Read the full incident report →

Minor June 5, 2026

Product catalog entities are missing from the UI

Detected by Pingoru
Jun 05, 2026, 09:15 AM UTC
Resolved
Jun 05, 2026, 09:51 AM UTC
Duration
36m
Affected: Stigg app
Timeline · 3 updates
  1. investigating Jun 05, 2026, 09:15 AM UTC

    Status: Investigating Product catalog entities are missing from the UI. The team is investigating Affected components Stigg app (Partial outage)

  2. identified Jun 05, 2026, 09:40 AM UTC

    Status: Identified We have identified the root cause and determined that the issue is related to a third-party permission provider Affected components Stigg app (Partial outage)

  3. resolved Jun 05, 2026, 09:51 AM UTC

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

Read the full incident report →

Minor March 23, 2026

Degraded UI functionality – navigation unavailable

Detected by Pingoru
Mar 23, 2026, 01:23 PM UTC
Resolved
Mar 23, 2026, 04:42 PM UTC
Duration
3h 19m
Affected: Stigg app
Timeline · 4 updates
  1. 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)

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

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

  4. 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)

Read the full incident report →

Minor March 2, 2026

Issues creating subscriptions

Detected by Pingoru
Mar 02, 2026, 10:03 AM UTC
Resolved
Mar 02, 2026, 12:48 PM UTC
Duration
2h 44m
Timeline · 3 updates
  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.

Read the full incident report →

Minor February 4, 2026

Degraded API Performance

Detected by Pingoru
Feb 04, 2026, 03:59 PM UTC
Resolved
Feb 04, 2026, 04:22 PM UTC
Duration
22m
Affected: API
Timeline · 2 updates
  1. 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)

  2. resolved Feb 04, 2026, 04:22 PM UTC

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

Read the full incident report →