Chargebee: Avalara Service Degradation (Test Sites)
Timeline of updates
- resolved
Between 04:54 and 05:03 UTC, Avalara experienced internal server errors impacting certain merchants. The root cause has been identified as stemming from a third-party service provider, Avalara. The errors have ceased, and there are no ongoing impacts as of 5:03:00 AM UTC. This incident exclusively pertained to the TEST site; no LIVE sites were affected during the specified timeframe.
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-20 05:57 UTC, resolved after 0 min, 1 update(s).
- Title
- Avalara Service Degradation (Test Sites)
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/tzsrn3k9g004
Chargebee profileRecent Chargebee incidentsAll outages on March 20, 2024Chargebee in March 2024MarkdownJSON