Chargebee: AWS RDS Failover
Timeline of updates
- resolved
We faced temporary failures due to AWS RDS failover at 18:56 to 18:57 UTC, that occurred in one of our availability zones. Two of our db shards present in that zone were affected, Customers present in those shards were affected during this event. The failover was successful and the errors have stopped. Failover has occurred due an issue with AWS EC2 API. During the time of event, we received few intermittent request failures and PDF errors. We will be contacting the affected customers separately via mail. AWS has acknowledged on the issue, more details on the issue can be found here - https://status.aws.amazon.com/ (opens in new tab)
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 2020-07-29 19:38 UTC, resolved after 0 min, 1 update(s).
- Title
- AWS RDS Failover
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/8mdz7f87wz83
Chargebee profileRecent Chargebee incidentsAll outages on July 29, 2020Chargebee in July 2020MarkdownJSON