# Chargebee: Avalara Service Degradation

> Chargebee status incident “Avalara Service Degradation” on 2024-03-25: impact minor (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/chargebee/incidents/fvrt6k2yqh42
Last updated: 2024-03-25T03:00:00Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2024-03-25 03:00 UTC · Resolved: 2024-03-25 03:00 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.chargebee.com/incidents/fvrt6k2yqh42](https://status.chargebee.com/incidents/fvrt6k2yqh42)
- [Company: Chargebee](https://rewindex.com/company/chargebee.md)

## Timeline of updates

- **resolved** 2024-03-25 03:00 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/chargebee/incidents/fvrt6k2yqh42
- Citation: Chargebee, “Avalara Service Degradation” (2024-03-25 03:00 UTC). Archived by Rewindex: https://rewindex.com/company/chargebee/incidents/fvrt6k2yqh42 (CC BY 4.0).
- Markdown link: `[Chargebee: Avalara Service Degradation (2024-03-25)](https://rewindex.com/company/chargebee/incidents/fvrt6k2yqh42)`


---
Canonical: https://rewindex.com/company/chargebee/incidents/fvrt6k2yqh42 · Markdown: https://rewindex.com/company/chargebee/incidents/fvrt6k2yqh42.md · JSON: https://rewindex.com/api/v1/companies/chargebee/incidents/fvrt6k2yqh42 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:36:13.213Z