Chargebee: Degradation In The Estimate For Subscription Cancellations
Timeline of updates
- resolved
Between June 6, 2024, 04:30 UTC, and June 10, 2024, 04:30 UTC, a deployment made the cancel_reason_codeparameter mandatory in the cancel subscription estimate API, causing 4xx errors when it was not provided. The issue has been resolved by reverting the parameter to optional. No product functionality was impacted.
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 2024-06-10 06:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Degradation In The Estimate For Subscription Cancellations
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/gm3z5mmmw7qs
Chargebee profileRecent Chargebee incidentsAll outages on June 10, 2024Chargebee in June 2024MarkdownJSON