- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API (US), API (EU), API (AU)
- Regions
- eu, us
- Down Index
- 37of 100
What to do
Check whether you use Chargebee API (US), API (EU), API (AU) in eu, us. 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-05-18 11:05 UTC and 2026-05-18 11:05 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
- resolved
We experienced an issue causing intermittent 5xx errors across all regions, which was traced back to an internal change. We have reverted it to restore full stability. We apologize for any inconvenience this may have caused. Update: Impact Window: 10:06 UTC to 10:17 UTC
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-872fd67cc8
Is Chargebee still down?
No, this incident was resolved 2026-05-18 11:05 UTC. For Chargebee's live state, see https://down.guide/chargebee.
How long did it last?
0m, from 2026-05-18 11:05 UTC to 2026-05-18 11:05 UTC, by the times Chargebee posted.
What was affected?
Chargebee named API (US), API (EU), API (AU) in eu, us.
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.