- Level
- confirmed
- Worst impact
- Degraded
- Components
- API (US)
- Regions
- us
- Down Index
- 23of 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 0m it lasted.
Anything that failed between 2025-12-04 04:51 UTC and 2025-12-04 04: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
- resolved
Between 01:30 to 02:54 UTC, a few customers in the US region experienced intermittent app latency and API timeouts due to an underlying issue with the AWS platform. Service has since stabilized. We will work with the service provider on a long-term fix. We are also implementing additional redundancy internally to mitigate and prevent similar disruptions.
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-c4fccbef51
Is Chargebee still down?
No, this incident was resolved 2025-12-04 04:51 UTC. For Chargebee's live state, see https://down.guide/chargebee.
How long did it last?
0m, from 2025-12-04 04:51 UTC to 2025-12-04 04:51 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.