Changes / Chargebee / API Service Degradation

Chargebee: Major incident: API Service Degradation

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 diff below (Sol; type: incident degradation). Check the diff before relying on it.

Major incidentLabel: degradation (model (Jev), 54%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: API Service Degradation
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-05-18 11:05 UTC
AddedResolved time#5
Before: not present
After: 2026-05-18 11:05 UTC
AddedAffected components#6
Before: not present
After: API (AU), API Endpoints - API (AU), API Endpoints - API (EU), API Endpoints - API (US), API (EU), API (US)
AddedUpdateresolved#7
Before: not present
After: 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

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: API Service Degradation (this change)
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).
Major incident

All Chargebee changes → · Chargebee profile · Markdown · JSON