Chargebee: Spreedly Core API errors
Timeline of updates
- resolved
After a period of monitoring, Spreedly has not seen any recurrence of this issue. The lagging data has been resolved and all systems are stabilized and functioning normally with the current data.
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 2022-12-30 19:51 UTC, resolved after 2 d, 1 update(s).
- Title
- Spreedly Core API errors
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/1gz1fhc23svt
Chargebee profileRecent Chargebee incidentsAll outages on December 30, 2022Chargebee in December 2022MarkdownJSON