Chargebee: Intermittent 5xx Errors in EU Region
Timeline of updates
- resolved
On 16th March 2025, an AWS RDS failover event caused two brief periods of elevated 5xx errors due to the temporary unavailability of the database. The disruptions occurred between 07:49 to 07:50 UTC and 07:52 to 07:53 UTC, during which application connectivity to the database was intermittently impacted. As a result, approximately 0.7% of merchants encountered errors, affecting less than 4.9% of total requests in the EU region. The failover was automatically handled by AWS, and services recovered without manual intervention. We apologize for any disruption this may have caused. Update: The earlier reported incident window of 07:48 to 08:03 UTC has been updated to reflect the actual impact duration, which was limited to 07:49 to 07:50 UTC and 07:52 to 07:53 UTC based on detailed analysis.
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 2025-03-16 10:58 UTC, resolved after 0 min, 1 update(s).
- Title
- Intermittent 5xx Errors in EU Region
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/l1qy2984w920
Chargebee profileRecent Chargebee incidentsAll outages on March 16, 2025Chargebee in March 2025MarkdownJSON