Chargebee: API service degradation
Timeline of updates
- resolved
We discovered that one of our application instances was unhealthy. The reason indicates that the instances were restarted as part of the service restart thus causing service degradation for 8 minutes. The elevated errors were noticed from 14:54 to 15:02 UTC. Please accept our sincerest apologies for any inconvenience this may have caused. Email communications have been sent out to the impacted customers affected by this event.
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-12 16:37 UTC, resolved after 16 min, 1 update(s).
- Title
- API service degradation
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/6zyztqrgd98k
Chargebee profileRecent Chargebee incidentsAll outages on July 12, 2023Chargebee in July 2023MarkdownJSON