Chargebee: Elevated 500 Errors on API requests only in the EU region
Timeline of updates
- resolved
We discovered that a code change had inadvertently affected some customers, resulting in elevated errors in the API requests. We have reverted the change and the errors are completely stopped. The elevated errors were noticed from 8:28 AM to 9:28 AM UTC. Please accept our sincerest apologies for any inconvenience this may have caused. If you have any questions, please reach out to our support team at support@chargebee.com
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 2023-07-07 10:03 UTC, resolved after 32 min, 1 update(s).
- Title
- Elevated 500 Errors on API requests only in the EU region
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/pntv6w66sr89
Chargebee profileRecent Chargebee incidentsAll outages on July 7, 2023Chargebee in July 2023MarkdownJSON