Chargebee: API & UI Service Degradation In AU Region
Timeline of updates
- resolved
On April 10, 2024, between 06:43 and 07:06 UTC, a code merge disrupted our API services and caused intermittent failures in the user interface (UI). These issues primarily affected a small subset of our customers located in Australia. The major spikes in the UI and API requests were observed between 07:00 and 07:03 UTC. However, our team quickly identified and resolved the problem, restoring both API and UI services to their normal functioning. We apologize for any inconvenience experienced by the impacted customers.
From Chargebee’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.chargebee.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Chargebee, started 2024-04-10 07:33 UTC, resolved after 0 min, 1 update(s).
- Title
- API & UI Service Degradation In AU Region
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/xncpfybn7pst
Chargebee profileRecent Chargebee incidentsAll outages on April 10, 2024Chargebee in April 2024MarkdownJSON