Companies / Chargebee / incidents

Chargebee: API Service Degradation

Impact: majorStatus: resolvedStarted Resolved (0 min)1 updateSource: stspg.io (opens in new tab)
Summary

Chargebee reported major API degradation across AU, EU and US, with intermittent 5xx errors caused by an internal change; reverting it restored stability. The stated impact window was 10:06 UTC to 10:17 UTC on 2026-05-18, while recorded start and resolution were both 2026-05-18 11:05 UTC (computed duration: 0 min).

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: API (AU)API Endpoints - API (AU)API Endpoints - API (US)API (US)API Endpoints - API (EU)API (EU)

Timeline of updates

  1. resolved

    We experienced an issue causing intermittent 5xx errors across all regions, which was traced back to an internal change. We have reverted it to restore full stability. We apologize for any inconvenience this may have caused. Update: Impact Window: 10:06 UTC to 10:17 UTC

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Chargebee profile · Recent Chargebee incidents · Markdown · JSON