- Level
- confirmed
- Worst impact
- Degraded
- Components
- Copilot Services
- Down Index
- 29of 100
What to do
Check whether you use Chargebee Copilot Services. 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 6m it lasted.
Anything that failed between 2026-06-30 22:55 UTC and 2026-07-01 00:00 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
- identified
We are aware of an issue causing server errors to appear in the Chargebee Copilot panel within the Growth application. Users may be unable to load or interact with the Copilot interface. All core billing functions are completely unaffected and operating normally.
provider
- resolved
We have confirmed that these alerts were false positive and no actual degradation of service occurred. We apologize for any confusion this may have 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-46a08acd32
Is Chargebee still down?
No, this incident was resolved 2026-07-01 00:00 UTC. For Chargebee's live state, see https://down.guide/chargebee.
How long did it last?
1h 6m, from 2026-06-30 22:55 UTC to 2026-07-01 00:00 UTC, by the times Chargebee posted.
What was affected?
Chargebee named Copilot Services.
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.