Chargebee: API Service Degradation
Affected components: API Endpoints - API (US)API (US)
Timeline of updates
- resolved
Between 01:30 to 02:54 UTC, a few customers in the US region experienced intermittent app latency and API timeouts due to an underlying issue with the AWS platform. Service has since stabilized. We will work with the service provider on a long-term fix.
We are also implementing additional redundancy internally to mitigate and prevent similar disruptions.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3539475e51262d8e…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Chargebee, started 2025-12-04 04:51 UTC, resolved after 0 min, 1 update(s).
- Title
- API Service Degradation
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/xjq4krhyw461
Chargebee profileRecent Chargebee incidentsAll outages on December 4, 2025Chargebee in December 2025MarkdownJSON