Chargebee: API Service Degradation
Affected components: API Endpoints - API (US)API (US)
Timeline of updates
- investigating
We have noticed intermittent API failures in US Region, Our team is investigating the cause and will provide updates as soon as we have more information.
- monitoring
We have not observed any errors since 14:46 UTC. We are monitoring the API responses.
- resolved
We experienced intermittent API request timeouts during two brief one-minute windows between 14:23 and 14:46 UTC. The issue has since been resolved, and services are operating normally.
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
f30831b6cb4c6f6b…
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 2026-02-26 16:45 UTC, resolved after 0 min, 3 update(s).
- Title
- API Service Degradation
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/rcp9cv0r1ftp
Chargebee profileRecent Chargebee incidentsAll outages on February 26, 2026Chargebee in February 2026MarkdownJSON