rewindex

CompaniesChargebeeIncidents

Chargebee: Spreedly Core Transactional API Errors

MinorStatus: resolvedStarted Resolved (9.2 h)1 updatestatus.chargebee.com (opens in new tab)

Timeline of updates

  1. resolved

    Spreedly has fixed the 5xx errors but callback delivery may continue to experience delays. Any delayed or missed callbacks will be re-queued tomorrow.

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 2023-01-05 18:39 UTC, resolved after 9.2 h, 1 update(s).

Title
Spreedly Core Transactional API Errors
Vendor
Chargebee
Date
URL
https://rewindex.com/company/chargebee/incidents/jck7bk66j8lh

Chargebee profileRecent Chargebee incidentsAll outages on January 5, 2023Chargebee in January 2023MarkdownJSON