Chargebee outage history

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.

We experienced 2 minutes of intermittent API request timeouts in the US region during the window from 05-06-2026 22:16 UTC to 22:22 UTC. The issue has since been resolved, and services are operating normally.

We are investigating an issue with our email provider that is causing delays in system notifications for test sites. Live sites are not impacted and remain fully operational. We are working with the provider to restore normal email functionality for our test environments. We will keep you posted as we progress.

We have restored outbound email functionality for test environments. This incident has been resolved. -- Live sites were not impacted during this service window.

We experienced intermittent API request timeouts in the EU region between 15:02 UTC and 15:16 UTC. The issue has since been resolved, and services are operating normally.

We experienced an issue causing intermittent 5xx errors across all regions, which was traced back to an internal change. We have reverted it to restore full stability. We apologize for any inconvenience this may have caused. Update: Impact Window: 10:06 UTC to 10:17 UTC

We are experiencing login issues with the RevRec portal. We will share an update as we progress.

We have identified the root cause and implemented a fix. Our team is continuing to monitor the services to ensure ongoing stability.

This incident has been resolved.

Between May 7, 23:35 UTC and May 8, 00:55 UTC, we experienced intermittent API request timeouts in the US region due to an AWS platform issue. We are monitoring the systems to ensure continued stability.

Our team is working with AWS to assess the impact. We will share an update as we progress.

We are continuing to monitor the services. The incident remains open as we verify full system recovery. We will share an update as we progress.

We have verified that the intermittent API latency has been fully resolved. Our monitoring confirms all systems have fully recovered.

### **Intermittent API Errors and Background Processing Delays** **Incident Overview** On May 7, 2026, an infrastructure event in [AWS US-EAST-1](https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_FFA94_A4DC515D30F) \(availability zone use1-az4\) caused degraded performance in Amazon DynamoDB, a component of Chargebee’s infrastructure. Rather than a sustained outage, this manifested as two brief windows of elevated API errors — approximately 3:00–3:15 AM UTC and 4:15–4:50 AM UTC on May 8, 2026, while the rest of the period remained largely stable. Approximately 1.5% of active sites experienced intermittent API failures or background job delays during these windows, with actual impact limited to approximately 15 minutes across the event. All affected background jobs were successfully rescheduled and completed. **What Happened** AWS experienced a thermal event in a single availability zone \(use1-az4\) in US-EAST-1, which impaired a subset of DynamoDB storage partitions. While the AWS-side infrastructure recovery took several hours, the customer-visible impact on Chargebee was limited to intermittent error spikes rather than continuous degradation, reflecting our platform’s ability to absorb partial infrastructure failures. **What We Are Doing** All API errors during this incident were traced to DynamoDB latency caused by the AWS internal AZ-level impairment. Given DynamoDB’s role in our business-critical workflows, we are evaluating highly available alternatives and fallback architectures to reduce the impact of similar infrastructure events. --- We recognise that even intermittent disruption has real consequences for your operations. The errors that spiked during this incident were brief, and our systems absorbed the majority of the AWS recovery window. We remain committed to further reducing Chargebee’s exposure to external infrastructure events