Chargebee: Webhook Failure
Timeline of updates
- resolved
Systems are back to normal state and failed Webhooks were successfully rescheduled. During the time of incident, we identified latency in the Data Replication service between shards, causing internal delays on Webhook events. A case has been raised with AWS to understand further.
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 2020-06-02 01:00 UTC, resolved after 4.7 h, 1 update(s).
- Title
- Webhook Failure
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/z69p1w1hblkh
Chargebee profileRecent Chargebee incidentsAll outages on June 2, 2020Chargebee in June 2020MarkdownJSON