- 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 2026-02-26 16:45 UTC and 2026-02-26 16:45 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
- investigating
We have noticed intermittent API failures in US Region, Our team is investigating the cause and will provide updates as soon as we have more information.
provider
- monitoring
We have not observed any errors since 14:46 UTC. We are monitoring the API responses.
provider
- resolved
We experienced intermittent API request timeouts during two brief one-minute windows between 14:23 and 14:46 UTC. The issue has since been resolved, and services are operating normally.
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-a96f896b33
Is Chargebee still down?
No, this incident was resolved 2026-02-26 16:45 UTC. For Chargebee's live state, see https://down.guide/chargebee.
How long did it last?
0m, from 2026-02-26 16:45 UTC to 2026-02-26 16:45 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.