# Chargebee: Webhook Failure

> Chargebee status incident “Webhook Failure” on 2020-06-02: impact none (vendor’s label), 4.7 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/chargebee/incidents/z69p1w1hblkh
Last updated: 2020-06-02T05:40:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2020-06-02 01:00 UTC · Resolved: 2020-06-02 05:40 UTC · Duration: 4.7 h
- Updates: 1
- [Vendor status page: https://status.chargebee.com/incidents/z69p1w1hblkh](https://status.chargebee.com/incidents/z69p1w1hblkh)
- [Company: Chargebee](https://rewindex.com/company/chargebee.md)

## Timeline of updates

- **resolved** 2020-06-02 05:40 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/chargebee/incidents/z69p1w1hblkh
- Citation: Chargebee, “Webhook Failure” (2020-06-02 01:00 UTC). Archived by Rewindex: https://rewindex.com/company/chargebee/incidents/z69p1w1hblkh (CC BY 4.0).
- Markdown link: `[Chargebee: Webhook Failure (2020-06-02)](https://rewindex.com/company/chargebee/incidents/z69p1w1hblkh)`


---
Canonical: https://rewindex.com/company/chargebee/incidents/z69p1w1hblkh · Markdown: https://rewindex.com/company/chargebee/incidents/z69p1w1hblkh.md · JSON: https://rewindex.com/api/v1/companies/chargebee/incidents/z69p1w1hblkh · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:22:02.690Z