Chargebee: Avalara Service Degradation
Timeline of updates
- resolved
On March 25, 2024, between 1:18 and 1:19 UTC, Avalara encountered internal server errors affecting specific merchants. Investigation revealed the root cause to be related to a third-party service provider utilized by Avalara. The errors have since subsided, with no further impact reported.
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-25 03:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Avalara Service Degradation
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/fvrt6k2yqh42
Chargebee profileRecent Chargebee incidentsAll outages on March 25, 2024Chargebee in March 2024MarkdownJSON