- Level
- confirmed
- Worst impact
- Degraded
- Components
- API (US)
- Regions
- us
- Down Index
- 30of 100
What to do
Check whether you use Chargebee API (US) in 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 22m it lasted.
Anything that failed between 2026-09-03 13:51 UTC and 2026-09-03 14:13 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
- monitoring
We experienced a brief service interruption that resulted in a small number of failed API requests. All services have completely recovered, and we are monitoring our systems to ensure ongoing stability. We apologize for any disruption this may have caused.
provider
- resolved
We noticed API failures between 11:49 UTC and 12:01 UTC. While the overall incident window lasted for 12 minutes, the actual disruptions were limited to 4 minutes. Our systems remain fully stable, and we are resolving this incident.
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-9d7ca74a79
Is Chargebee still down?
No, this incident was resolved 2026-09-03 14:13 UTC. For Chargebee's live state, see https://down.guide/chargebee.
How long did it last?
22m, from 2026-09-03 13:51 UTC to 2026-09-03 14:13 UTC, by the times Chargebee posted.
What was affected?
Chargebee named API (US) in 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.