Chargebee: Service Interruption Due to Third-Party Service Provider
Timeline of updates
- resolved
On December 17, 2023, between 16:46 and 16:47 UTC, one of our systems experienced a service interruption. This disruption was caused by an issue on the AWS platform, which led to an unexpected increase in API failures in all the regions. Our technical team promptly identified the cause of the problem as an external issue on the AWS platform and took immediate steps to address it. We apologize for any inconvenience this may have caused.
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-12-17 16:55 UTC, resolved after 0 min, 1 update(s).
- Title
- Service Interruption Due to Third-Party Service Provider
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/xnll4qfvpgxh
Chargebee profileRecent Chargebee incidentsAll outages on December 17, 2023Chargebee in December 2023MarkdownJSON