Chargebee: Avalara address validation issue
Timeline of updates
- resolved
We have reached out to Avalara support and identified the issue, which was a validation error with one of their APIs. The original problem no longer persists, but address validation may have an increased rate of error for the next 24 hours.
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 2019-09-16 16:06 UTC, resolved after 45 h, 1 update(s).
- Title
- Avalara address validation issue
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/21h5z9b4zttr
Chargebee profileRecent Chargebee incidentsAll outages on September 16, 2019Chargebee in September 2019MarkdownJSON