outages.live
Live
C

Chargebee

Chargebee is operational

Checked 2 min ago Operational

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

History

90 days agoToday

Incidents in 90 days

14

Days with an incident

21

Median duration

22 min

Longest incident

42 h 53 min

Components

85

Chargebee UI

Admin Console (US) Operational
90 days ago1 day with an incidentToday
Admin Console (EU) Operational
90 days ago1 day with an incidentToday
Admin Console (AU) Operational
90 days ago1 day with an incidentToday

Email Notifications

Email Notifications (US) Operational
90 days agoNo incidentsToday
Email Notifications (EU) Operational
90 days agoNo incidentsToday
Email Notifications (AU) Operational
90 days agoNo incidentsToday

API Endpoints

API (US) Operational
90 days ago4 days with an incidentToday
API (EU) Operational
90 days ago6 days with an incidentToday
API (AU) Operational
90 days agoNo incidentsToday

Checkout

Checkout (US) Operational
90 days agoNo incidentsToday
Checkout (EU) Operational
90 days agoNo incidentsToday
Checkout (AU) Operational
90 days agoNo incidentsToday

Self-Serve Portal

Self-Serve Portal (US) Operational
90 days agoNo incidentsToday
Self-Serve Portal (EU) Operational
90 days ago1 day with an incidentToday
Self-Serve Portal (AU) Operational
90 days agoNo incidentsToday

Webhooks

Webhooks (US) Operational
90 days agoNo incidentsToday
Webhooks (EU) Operational
90 days agoNo incidentsToday
Webhooks (AU) Operational
90 days agoNo incidentsToday

Mobile Subscriptions

Apple Store Operational
90 days agoNo incidentsToday
Google Play Operational
90 days agoNo incidentsToday

Identity and Access Management

IAM (US) Operational
90 days agoNo incidentsToday
IAM (EU) Operational
90 days agoNo incidentsToday
IAM (AU) Operational
90 days agoNo incidentsToday

Reports And Analytics

Dashboard (US) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 28, 2026

Duration41 min08:15 to 08:56API Service Degradation - EU RegionPartial outage

This incident has been resolved.

Oct 10, 2026

Duration1 min09:34 to 09:34API Service DegradationDegraded

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.

Oct 8, 2026

Duration42 h 53 min14:31 to 09:24API Service Degradation - EU RegionDegraded

This incident has been resolved.

Sep 30, 2026

Duration1 min10:05 to 10:05API Service DegradationDegraded

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.

Sep 29, 2026

Duration2 h12:35 to 14:35API Service DegradationPartial outage

This incident has been resolved.

Sep 17, 2026

Duration1 min03:51 to 03:51API Service DegradationDegraded

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

Sep 3, 2026

Duration50 min19:03 to 19:53Signup DegradationDegraded

This incident has been resolved.

Duration1 h 4 min17:36 to 18:40Application Login IssuesDegraded

This incident has been resolved.

Duration22 min13:51 to 14:13API Service DegradationDegraded

We noticed API failures between 11:49 UTC and 12:01 UTC. While the overall incident window lasted for 12 minutes, the actual disruptions were limited to 4 minutes. Our systems remain fully stable, and we are resolving this incident.

Sep 2, 2026

Duration8 min13:28 to 13:35API Service DegradationPartial outage

This incident has been resolved.

Duration1 min05:47 to 05:47QuickBooks Online Service DegradationDegraded

We experienced intermittent login and functionality issues due to an external service disruption at QuickBooks Online. QuickBooks has confirmed that the root cause has been fixed and all systems are fully restored. We apologize for any inconvenience this caused. Incident Reference - https://quickbooks.statuspage.io/incidents/vkntw55njz2z

Aug 24, 2026

Duration1 h 48 min15:59 to 17:47Avalara Service DegradationDegraded

This incident has been resolved.

Aug 7, 2026

Duration1 min15:58 to 15:58Self-Serve Portal Intermittent IssuesDegraded

Some users may have experienced intermittent issues managing subscriptions, invoices, or payment methods in the Self-Serve Portal. Service has been fully restored. We apologize for any inconvenience 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.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane