- Level
- confirmed
- Worst impact
- Degraded
- Components
- API (US)
- Regions
- us
- Down Index
- 33of 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 1h 38m it lasted.
Anything that failed between 2025-12-03 18:24 UTC and 2025-12-03 20:01 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 3
- identified
We experienced a brief interruption to our API service due to an internal server issue, and we are analysing the impact.
provider
- monitoring
API timeouts were observed in the US region during two intervals: 17:44–17:54 UTC and 18:00–18:02 UTC. The services have fully recovered, and we are continuing to monitor system reliability.
provider
- resolved
We have identified that the issue was due to the AWS platform, leading to increased API timeouts. AWS has confirmed that the services have fully recovered. We apologize for any inconvenience 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-98c4660bc2
Is Chargebee still down?
No, this incident was resolved 2025-12-03 20:01 UTC. For Chargebee's live state, see https://down.guide/chargebee.
How long did it last?
1h 38m, from 2025-12-03 18:24 UTC to 2025-12-03 20:01 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.