API Service Degradation
The API in the US region has intermittent failures. Chargebee reports that services have recovered and that it is monitoring them for stability.
State
Monitoring
Started
Ongoing for
1 h 1 min
Worst impact
Degraded
Timeline
1 updateMonitoring
1 h 1 min 100%
Updates
Times in UTCAs posted by Chargebee
We experienced intermittent API failures in the US region. Services have recovered, and we are monitoring them for ongoing stability.
Affected components
2Chargebee in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
26
Median duration
46 min
This incident
1.3× the median
Other Chargebee incidents
All incidents
Chargebee·Microsoft 365 Service Degradation
Chargebee reports degraded email notifications for Microsoft 365 and Email & SMTP Services - Microsoft 365. Chargebee later confirmed that Microsoft restored the Microsoft 365 services and that custom SMTP email notifications work again. The incident is resolved and lasted about 29 hours.
Chargebee·Partially Degraded Service
Chargebee reports that the Slack Apps/Integrations/APIs component did not work correctly. Chargebee reports that this problem is resolved. The problem lasted 3 minutes.
Chargebee·Partially Degraded Service
Chargebee reported partially degraded service on Slack Apps/Integrations/APIs. Chargebee reports that the incident is resolved. The incident lasted 213 minutes.
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 to its services or customer integrations from the PHPshell zero-day vulnerability. This affects Product Security. Chargebee marked the incident resolved on 3 November 2026, about 11 days after it started.
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