API Service Degradation
Between 01:59 UTC and 02:09 UTC, we experienced a brief service interruption in the EU region due to an AWS platform issue, which led to failed API requests for some users. All services have fully recovered. We apologize for any disruption this may have caused
The latest update from Chargebee.
State
Resolved
Started
46 d ago
2026-09-17 03:51 UTC
Lasted
1 min
until 2026-09-17 03:51 UTC
Worst impact
Degraded
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by Chargebee
Between 01:59 UTC and 02:09 UTC, we experienced a brief service interruption in the EU region due to an AWS platform issue, which led to failed API requests for some users. All services have fully recovered. We apologize for any disruption this may have caused
Affected components
2Chargebee in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
22
Median duration
22 min
This incident
100% shorter than the median
Other Chargebee incidents
All incidents
Chargebee·API Service Degradation - EU Region
This incident has been resolved.
Chargebee·Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability
Chargebee reports no impact on its services or customer integrations from the PHPshell zero-day vulnerability. The affected component is Product Security. Chargebee continues to monitor the situation and will give an update if its assessment changes.
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.
Chargebee·API Service Degradation - EU Region
This incident has been resolved.
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.
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.
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.
https://outages.live/feed.xml?providers=chargebee/feed subscribe https://outages.live/feed.xml?providers=chargebeeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane