Chargebee: API Service Degradation
Affected components: API Endpoints - API (US)API (US)
Timeline of updates
- monitoring
We experienced a brief service interruption that resulted in a small number of failed API requests. All services have completely recovered, and we are monitoring our systems to ensure ongoing stability. We apologize for any disruption this may have caused.
- resolved
We noticed API failures between 11:49 UTC and 12:01 UTC. While the overall incident window lasted for 12 minutes, the actual disruptions were limited to 4 minutes. Our systems remain fully stable, and we are resolving this incident.
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
7ab99651fc5a05a5…
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-09-03 13:51 UTC, resolved after 22 min, 2 update(s).
- Title
- API Service Degradation
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/sdtvpdlfkvhn
Chargebee profileRecent Chargebee incidentsAll outages on September 3, 2026Chargebee in September 2026MarkdownJSON