Chargebee: Intermittent errors between 17:16 to 18:48 UTC
Timeline of updates
- resolved
Monday, October 14th between 17:16 to 18:48 UTC, certain actions in the merchant console would have failed with the error "Access has been blocked temporarily. High request surge". We identified the root cause as a bug in our middleware server. We have deployed the fix and the issue is now resolved.
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: none) posted by Chargebee, started 2019-10-14 21:32 UTC, resolved after 0 min, 1 update(s).
- Title
- Intermittent errors between 17:16 to 18:48 UTC
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/rp2y2qbfzgjg
Chargebee profileRecent Chargebee incidentsAll outages on October 14, 2019Chargebee in October 2019MarkdownJSON