- Level
- confirmed
- Worst impact
- Degraded
- Components
- HubSpot
- Down Index
- 28of 100
What to do
Check whether you use Chargebee HubSpot. 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 43m it lasted.
Anything that failed between 2025-12-05 09:17 UTC and 2025-12-05 10: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 3
- identified
We are currently experiencing disruptions to our support ticketing and chat systems. Certain integrations and workflows that depend on Cloudflare may experience delays or degraded performance. More details - https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q
provider
- monitoring
We are seeing recovery across our support and chat services. Integrations and workflows that rely on Cloudflare are also recovering. We will continue to monitor until all affected services are fully stable.
provider
- resolved
This incident has been resolved.
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-222792ad11
Is Chargebee still down?
No, this incident was resolved 2025-12-05 10:00 UTC. For Chargebee's live state, see https://down.guide/chargebee.
How long did it last?
43m, from 2025-12-05 09:17 UTC to 2025-12-05 10:00 UTC, by the times Chargebee posted.
What was affected?
Chargebee named HubSpot.
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.