Skip to main content
Chargebee

Service Degradation: Location Validation Service Issues

Degraded Lasted 32m · started · Chargebee's page

Level
confirmed
Worst impact
Degraded
Components
API (US), API (EU), API (AU)
Regions
eu, us
Down Index
35of 100

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 32m it lasted.

    Anything that failed between 2026-01-08 20:21 UTC and 2026-01-08 20:53 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. identified

    We are investigating an issue affecting merchants who have Location Validation enabled in their Chargebee settings. Impacted users may experience 5xx errors or failures when attempting to create subscriptions and perform other related API operations. We are working with our third-party provider to resolve this. We recommend temporarily disabling the Location Validation option in your Tax Configuration settings. --- Reference Guide - https://www.chargebee.com/docs/billing/2.0/taxes/eu-vat

    provider

  2. resolved

    The errors have stopped, and services are currently operational. We are coordinating with our vendor on a permanent fix. If you continue to experience any issues, please reach out to support@chargebee.com.

    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-1bb5a48cac

Is Chargebee still down?

No, this incident was resolved 2026-01-08 20:53 UTC. For Chargebee's live state, see https://down.guide/chargebee.

How long did it last?

32m, from 2026-01-08 20:21 UTC to 2026-01-08 20:53 UTC, by the times Chargebee posted.

What was affected?

Chargebee named API (US), API (EU), API (AU) in eu, 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.