API Service Degradation

What to do

• Check whether you use Chargebee API (US), API (EU), API (AU) in eu, 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 2h 13m it lasted.

  Anything that failed between 2025-12-10 04:08 UTC and 2025-12-10 06:21 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

1. identifiedDec 10, 2025, 4:08 AM UTC

   We are experiencing intermittent API timeouts in the US region due to an issue with our cloud service provider. We will share further updates as we make progress.

   provider

2. monitoringDec 10, 2025, 6:14 AM UTC

   Between 02:00 and 05:40 UTC, we experienced elevated error rates and increased latencies across all regions. During this period, customers may have encountered 5XX errors and slower response times when making API calls. The underlying issue has been resolved by AWS, and all services have fully recovered. We will continue to monitor the platform to ensure ongoing stability.

   provider

3. resolvedDec 10, 2025, 6:21 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.