Live

API Service Degradation

0

Chargebee reported degraded API service and API endpoint performance in the US region. Chargebee later stated that a brief cloud provider issue caused intermittent API failures for some US merchants, and that services recovered. Chargebee resolved the incident after about 147 minutes.

State

Resolved

Started

Lasted

2 h 27 min

Worst impact

Degraded

Timeline

3 updates
09:1309:4910:2611:0311:39
DegradedUpdate postedTimes in UTC

Investigating

1 h 17 min 53%

Monitoring

1 h 9 min 47%

Updates

Times in UTC

As posted by Chargebee

Resolved

This incident has been resolved.

Monitoring

A brief cloud provider issue caused intermittent API failures for some merchants in the US region. Services have recovered, and we are monitoring our systems for ongoing stability.

Investigating

We are investigating a service interruption affecting our API services in the US region. We will provide updates as we progress.

Affected components

2
API (US)API Endpoints - API (US)

Chargebee in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

18

Days with an incident

27

Median duration

57 min

This incident

2.6× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 days
median 57 min
90 days agoToday

Other Chargebee incidents

All incidents

Follow Chargebee

Your coding agent knows when Chargebee is down, and tells you when a failure is theirs, not yours. You can also get Chargebee incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "chargebee" and tell me if Chargebee has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=chargebee
Slack
/feed subscribe https://outages.live/feed.xml?providers=chargebee

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane