Skip to main content
Menu
Chargebee

Incident

API Service Degradation

Degraded Lasted 1h 23m · started · Chargebee's page

DWN-5cd7de8368

Level
confirmed
Worst impact
Degraded
Components
API (US)
Regions
us
Down Index
33of 100

Summary

Chargebee says its API Service Degradation incident is resolved. Intermittent API failures in the US region were caused by unexpected cloud provider maintenance. The provider says all services have fully recovered.

Written by anthropic/claude-haiku-5.5 from Chargebee's own updates.

What to do

  • Check whether you use Chargebee API (US) in us. Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 23m it lasted.

    Anything that failed between 2026-11-15 08:48 UTC and 2026-11-15 10:10 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

  1. monitoring

    We experienced intermittent API failures in the US region. Services have recovered, and we are monitoring them for ongoing stability.

    provider

  2. resolved

    This service interruption was caused by unexpected cloud provider maintenance. All services have fully recovered. We apologize for any disruption 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-5cd7de8368

Is Chargebee still down?

No, this incident was resolved 2026-11-15 10:10 UTC. For Chargebee's live state, see https://down.guide/providers/chargebee.

How long did it last?

1h 23m, from 2026-11-15 08:48 UTC to 2026-11-15 10:10 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.