Chargebee outage history

Chargebee is aware of the recently reported PHPshell zero-day vulnerability and has completed an initial assessment of its potential impact on our services. Chargebee does not use PHP in its customer-facing workflows. Based on our assessment, this vulnerability does not affect Chargebee’s services or customer integrations, and no action is required by our customers at this time. As an additional precaution, we are verifying with our subprocessors to confirm they are unaffected and to ensure appropriate safeguards remain in place across our service ecosystem. We will continue to monitor relevant security developments and provide updates if our assessment changes. If you have any questions, please contact Chargebee Support.

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.

We are investigating a service interruption affecting our API. We will provide updates as we progress.

We experienced intermittent API errors between 12:50 UTC and 14:26 UTC. Services have recovered, and we are monitoring them for ongoing stability.

This incident has been resolved.

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.

Between 11:58 UTC and 12:08 UTC, we experienced a brief service interruption in the US region that resulted in failed API requests for some merchants. Services have recovered, and we are currently monitoring the systems for continued stability.

This incident has been resolved.

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

We are investigating an issue that is preventing new users from signing up. We will provide an update as soon as we have more information.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating login issues when accessing the Chargebee Admin Portal (https://app.chargebee.com) using email and password; there are no issues with Single Sign-On. We will keep you posted as we progress.

The issue has been fixed, and we are monitoring our systems to ensure ongoing stability. We apologize for any disruption this may have caused.

This incident has been resolved.

We experienced a brief service interruption that resulted in a small number of failed API requests. All services have completely recovered, and we are monitoring our systems to ensure ongoing stability. We apologize for any disruption this may have caused.

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.

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.

This incident has been resolved.

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

Between 14:54 UTC and 15:32 UTC, we experienced intermittent errors with our tax calculation provider, Avalara, which temporarily impacted a few API requests. The errors have stopped, and we are continuing to monitor services to ensure stability.

This incident has been resolved.

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.

Between 05:59 UTC and 06:01 UTC, some users may have experienced intermittent API failures in all 3 regions. The services have recovered and we are monitoring the situation for stability.

This incident has been resolved.

We are investigating a technical issue with our tax calculation provider, Avalara, that is impacting some subscription renewals and invoicing processes. We are following up with Avalara on this and will keep this incident updated as we progress.

The errors stopped as of 08:25 AM UTC, and we are monitoring the affected systems for stability.

This incident has been resolved.

We experienced intermittent API request timeouts in the US region between 12:38 UTC and 12:43 UTC. The issue has since been resolved, and services are operating normally.

We experienced a delay in webhook delivery for TEST sites during the window from July 19th 09:49 UTC to July 19th 12:12 UTC, and the services are functioning as expected. We apologize for any disruption this caused to your testing workflows.

We experienced intermittent API request timeouts in the EU region during the window from 15-7-2026 21:56:00 UTC to 16-07-2026 01:23:55 UTC. The issue has since been resolved, and services are operating normally.

We are aware of an issue causing server errors to appear in the Chargebee Copilot panel within the Growth application. Users may be unable to load or interact with the Copilot interface. All core billing functions are completely unaffected and operating normally.

We have confirmed that these alerts were false positive and no actual degradation of service occurred. We apologize for any confusion this may have caused.

We are investigating an issue with our email provider that is causing delays in system notifications. Our team is working with the email provider to restore normal functionality. We will keep you posted as we progress.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

A fix has been implemented. We are coordinating with our email provider to activate these changes and fully restore notification services.

Our team is following up with the email provider to expedite the restoration of notification services. We will keep you posted as we progress.

We are working with our email provider to expedite the resolution. We will provide another update as soon as notifications begin processing again.

Email service has been restored, and new notifications are now being delivered as expected. We will reprocess all queued emails to ensure that any messages delayed during this period are successfully delivered.

This incident has been resolved.