Skip to main content
Chargebee

Avalara Service Degradation

Degraded Lasted 1h 48m · started · Chargebee's page

Level
confirmed
Worst impact
Degraded
Components
Avalara
Down Index
30of 100

What to do

  • Check whether you use Chargebee Avalara. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 48m it lasted.

    Anything that failed between 2026-08-24 15:59 UTC and 2026-08-24 17:47 UTC may need a replay.
  • Subscribe to Chargebee's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=chargebee works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Chargebee 2

  1. monitoring

    Between 14:54 UTC and 15:32 UTC, we experienced intermittent errors with our tax calculation provider, Avalara, which temporarily impacted a few API requests. The errors have stopped, and we are continuing to monitor services to ensure stability.

    provider

  2. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-31bdd7e7ba

Is Chargebee still down?

No, this incident was resolved 2026-08-24 17:47 UTC. For Chargebee's live state, see https://down.guide/chargebee.

How long did it last?

1h 48m, from 2026-08-24 15:59 UTC to 2026-08-24 17:47 UTC, by the times Chargebee posted.

What was affected?

Chargebee named Avalara.

What caused it?

Chargebee hasn't published a root cause. If it does, it shows here.

Where does this come from?

Chargebee's official status page, https://status.chargebee.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.