outages.live
Live
CChargebeeIncident · 2026-09-02 13:28 UTC

API Service Degradation

ResolvedOfficial update

This incident has been resolved.

The latest update from Chargebee.

State

Resolved

Started

60 d ago

2026-09-02 13:28 UTC

Lasted

8 min

until 2026-09-02 13:35 UTC

Worst impact

Partial outage

Timeline

2 updates
13:2813:3013:3213:3413:35
Partial outageUpdate postedTimes in UTC

Monitoring

8 min 100%

Updates

Times in UTC

As posted by Chargebee

Resolved2026-09-02 13:35 UTC

This incident has been resolved.

Monitoring2026-09-02 13:28 UTC

Between 12:54 UTC and 12:57 UTC, some users may have experienced intermittent API failures in the US region. The services have recovered, and we are monitoring the situation for stability.

Affected components

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

Chargebee in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

14

Days with an incident

21

Median duration

22 min

This incident

64% shorter than the median

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

10 days
median 22 min
90 days agoToday

Other Chargebee incidents

All incidents
C

Chargebee·API Service Degradation - EU Region

This incident has been resolved.

Resolvedresolved 5 d ago
C

Chargebee·Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability

Chargebee reports no impact from the PHPshell zero-day vulnerability on its Product Security component. Chargebee states that it does not use PHP in customer-facing workflows. The provider continues to monitor the situation and no customer action is required.

Noticeupdated 10 d ago
C

Chargebee·API Service Degradation

We experienced a brief service interruption in the US region due to an AWS platform issue, which resulted in intermittent API failures for some merchants. All services have completely recovered. We apologize for any disruption this may have caused.

Resolvedresolved 22 d ago
C

Chargebee·API Service Degradation - EU Region

This incident has been resolved.

Resolvedresolved 22 d ago
C

Chargebee·API Service Degradation

We experienced a brief service interruption in the EU region between 09:14 UTC and 09:20 UTC that resulted in failed API requests for some merchants. Services have recovered. We apologize for any disruption this may have caused.

Resolvedresolved 32 d ago

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.cc/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.cc/feed.xml?providers=chargebee
Slack
/feed subscribe https://outages.cc/feed.xml?providers=chargebee

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane