Skip to main content
Chargebee

API Service Degradation

Degraded Lasted 0m · started · Chargebee's page

Level
confirmed
Worst impact
Degraded
Components
API (EU)
Regions
eu
Down Index
23of 100

What to do

  • Check whether you use Chargebee API (EU) in eu. 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 0m it lasted.

    Anything that failed between 2026-09-17 03:51 UTC and 2026-09-17 03:51 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 1

  1. resolved

    Between 01:59 UTC and 02:09 UTC, we experienced a brief service interruption in the EU region due to an AWS platform issue, which led to failed API requests for some users. All services have fully recovered. We apologize for any disruption this may have caused

    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-30e04b8f55

Is Chargebee still down?

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

How long did it last?

0m, from 2026-09-17 03:51 UTC to 2026-09-17 03:51 UTC, by the times Chargebee posted.

What was affected?

Chargebee named API (EU) in eu.

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.