Chargebee: Service Interruption in the GoCardless Gateway
Timeline of updates
- resolved
A recent change in our application led to failures in processing collect-invoice and sub-renewal requests via the GoCardless gateway. This was due to incomplete error handling, resulting in null pointer exceptions. We fixed this by addressing how we handle these errors, ensuring transactions can now fail gracefully. We apologize for any inconvenience this may have caused. Note – The impact was very minimal as only a few transactions failed. We handled them well during the impacted timeframe with no further impact from the incident.
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-03-01 10:42 UTC, resolved after 5.0 h, 1 update(s).
- Title
- Service Interruption in the GoCardless Gateway
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/n71lqq7zvg32
Chargebee profileRecent Chargebee incidentsAll outages on March 1, 2024Chargebee in March 2024MarkdownJSON