Chargebee

Affected: API (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-10-10 09:34 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-08 14:31 UTC

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

2. monitoring 2026-10-08 14:45 UTC

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

3. resolved 2026-10-10 09:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-30 10:05 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-29 12:35 UTC

   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.

2. resolved 2026-09-29 14:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-09-17 03:51 UTC

   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

Excerpts are shortened. Read the full incident on Chargebee's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-03 19:03 UTC

   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.

2. identified 2026-09-03 19:47 UTC

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

3. monitoring 2026-09-03 19:52 UTC

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

4. resolved 2026-09-03 19:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Admin Console (US), Admin Console (EU), Admin Console (AU)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 17:36 UTC

   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.

2. monitoring 2026-09-03 18:10 UTC

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

3. resolved 2026-09-03 18:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-09-03 13:51 UTC

   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.

2. resolved 2026-09-03 14:13 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-02 13:28 UTC

   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.

2. resolved 2026-09-02 13:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: QuickBooks

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-09-02 05:47 UTC

   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...

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Avalara

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-24 15:59 UTC

   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.

2. resolved 2026-08-24 17:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Self-Serve Portal (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-07 15:58 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US), API (EU), API (AU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-08-02 06:47 UTC

   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.

2. resolved 2026-08-02 06:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Avalara

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-21 07:52 UTC

   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.

2. monitoring 2026-07-21 09:24 UTC

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

3. resolved 2026-07-21 11:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-20 13:10 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-16 13:10 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-16 12:56 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Copilot Services

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-30 22:55 UTC

   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.

2. resolved 2026-07-01 00:00 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Email Notifications (US), Email Notifications (EU), Email Notifications (AU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-11 23:15 UTC

   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.

2. identified 2026-06-11 23:30 UTC

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

3. identified 2026-06-11 23:53 UTC

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

4. identified 2026-06-12 00:18 UTC

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

5. identified 2026-06-12 00:39 UTC

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

6. identified 2026-06-12 01:19 UTC

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

7. monitoring 2026-06-12 02:03 UTC

   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.

8. resolved 2026-06-12 02:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-06-05 23:00 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Sendgrid

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-29 11:40 UTC

   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...

2. resolved 2026-05-29 12:18 UTC

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

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (EU), Checkout (EU), hCaptcha

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-20 16:09 UTC

   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.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US), API (EU), API (AU)

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-18 11:05 UTC

   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

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: RevRec Portal

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-08 02:25 UTC

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

2. monitoring 2026-05-08 03:20 UTC

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

3. resolved 2026-05-08 03:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-05-08 00:29 UTC

   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.

2. monitoring 2026-05-08 00:57 UTC

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

3. monitoring 2026-05-08 04:08 UTC

   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.

4. resolved 2026-05-08 07:36 UTC

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

5. postmortem 2026-05-15 17:08 UTC

   ### **Intermittent API Errors and Background Processing Delays** **Incident Overview** On May 7, 2026, an infrastructure event in [AWS...

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: hCaptcha

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-05-05 15:48 UTC

   Between 14:15 UTC and 14:22 UTC, a brief degradation in the hCaptcha service caused intermittent API errors for some users. The upstream issue has been resolved, and our services are operating normally. -- For more details - https://www.hcaptchastatus.com/incidents/ztn3pw8tg2cv

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Webhooks (US), Webhooks (AU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-09 06:36 UTC

   We are currently monitoring an issue causing background processing delays. As a result, you may notice delays in payment status updates and slower sync times for third-party integrations. Core platform functionality remains completely unaffected, and we have implemented...

2. monitoring 2026-04-09 16:37 UTC

   We have successfully deployed a patch to address the underlying issue. We will continue to monitor the system to ensure ongoing stability. Thank you for your patience while we worked to resolve this issue.

3. resolved 2026-04-10 11:51 UTC

   We have concluded our monitoring period and observed no further issues. All systems are operating normally. Thank you for your continued patience.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-02-26 15:16 UTC

   We observed minor service degradation in API responses from 11:19 UTC to 11:23 UTC due to an internal server issue, which resulted in an unexpected increase in API failures in the US region. We apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-26 15:04 UTC

   We have noticed intermittent API failures in US Region, Our team is investigating the cause and will provide updates as soon as we have more information.

2. monitoring 2026-02-26 16:24 UTC

   We have not observed any errors since 14:46 UTC. We are monitoring the API responses.

3. resolved 2026-02-26 16:45 UTC

   We experienced intermittent API request timeouts during two brief one-minute windows between 14:23 and 14:46 UTC. The issue has since been resolved, and services are operating normally.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: GoCardless

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-24 14:36 UTC

   We have identified an issue outside of our platform resulting in an elevated error rate for transactions processed through GoCardless. GoCardless has confirmed that some users are experiencing a blank screen when accessing the GoCardless Dashboard. There have also been reports...

2. monitoring 2026-02-24 15:02 UTC

   GoCardless have identified the root cause and implemented a fix. Access to the GoCardless dashboard and APIs is recovering at the moment.

3. resolved 2026-02-24 15:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Webhooks (US), Webhooks (EU), Webhooks (AU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-19 13:28 UTC

   We are currently experiencing a delay in webhook delivery for TEST sites. Our team is investigating the cause and will provide updates as soon as we have more information.

2. identified 2026-02-19 13:36 UTC

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

3. resolved 2026-02-19 15:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-01-22 15:47 UTC

   Between 11:58 and 11:59 UTC, we experienced intermittent API request timeouts in the US region due to AWS platform issue. The impact was minimal, and the service has fully recovered. -- We apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US), API (EU), API (AU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-01-08 20:21 UTC

   We are investigating an issue affecting merchants who have Location Validation enabled in their Chargebee settings. Impacted users may experience 5xx errors or failures when attempting to create subscriptions and perform other related API operations. We are working with our...

2. resolved 2026-01-08 20:53 UTC

   The errors have stopped, and services are currently operational. We are coordinating with our vendor on a permanent fix. If you continue to experience any issues, please reach out to support@chargebee.com.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US), API (EU), API (AU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-12-10 04:08 UTC

   We are experiencing intermittent API timeouts in the US region due to an issue with our cloud service provider. We will share further updates as we make progress.

2. monitoring 2025-12-10 06:14 UTC

   Between 02:00 and 05:40 UTC, we experienced elevated error rates and increased latencies across all regions. During this period, customers may have encountered 5XX errors and slower response times when making API calls. The underlying issue has been resolved by AWS, and all...

3. resolved 2025-12-10 06:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: HubSpot

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-12-05 09:17 UTC

   We are currently experiencing disruptions to our support ticketing and chat systems. Certain integrations and workflows that depend on Cloudflare may experience delays or degraded performance. More details - https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q

2. monitoring 2025-12-05 09:40 UTC

   We are seeing recovery across our support and chat services. Integrations and workflows that rely on Cloudflare are also recovering. We will continue to monitor until all affected services are fully stable.

3. resolved 2025-12-05 10:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-12-04 04:51 UTC

   Between 01:30 to 02:54 UTC, a few customers in the US region experienced intermittent app latency and API timeouts due to an underlying issue with the AWS platform. Service has since stabilized. We will work with the service provider on a long-term fix. We are also implementing...

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-12-03 18:24 UTC

   We experienced a brief interruption to our API service due to an internal server issue, and we are analysing the impact.

2. monitoring 2025-12-03 19:33 UTC

   API timeouts were observed in the US region during two intervals: 17:44–17:54 UTC and 18:00–18:02 UTC. The services have fully recovered, and we are continuing to monitor system reliability.

3. resolved 2025-12-03 20:01 UTC

   We have identified that the issue was due to the AWS platform, leading to increased API timeouts. AWS has confirmed that the services have fully recovered. We apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US), API (EU), API (AU)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-12-03 08:46 UTC

   We experienced a brief interruption to our API service due to an internal server issue. The impact was minimal, and the service has fully recovered. We apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-11-29 10:10 UTC

   We experienced a brief interruption to our API service in the US region between 08:55 UTC and 08:56 UTC due to an issue at the AWS platform. The impact was very minimal. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-11-21 12:52 UTC

   We experienced a brief interruption to our API service in the US region between 11:07 UTC and 11:08 UTC due to an issue at the AWS platform. The impact was very minimal. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Braintree Gateway API, PayPal Payment Services, Adyen

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-18 12:31 UTC

   As of 11:32 UTC, PayPal is experiencing a system issue which is impacting multiple payment services. We are continuing to monitor and will post further updates. Status updates: https://paypal-status.com/incident/production

2. resolved 2025-11-18 13:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-11-14 08:21 UTC

   We experienced a brief API service interruption between 13:00 and 13:01 UTC due to an issue on the AWS platform. The impact was very minimal. We apologise for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Webhooks (US), Webhooks (EU), Webhooks (AU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-11-06 07:41 UTC

   We received reports that transactions processed through Checkout.com remained in the “In Progress” state in Chargebee, even after being successfully captured at the gateway. This resulted in a temporary delay in updating the payment status in Chargebee for a few merchants using...

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-11-05 10:28 UTC

   On Nov 5th, between 08:01 UTC and 08:03 UTC, we experienced intermittent API request timeouts in the EU region due to an internal server issue. The impact was minimal, and the service has fully recovered. We apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Adyen

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-24 20:00 UTC

   We have identified an issue outside of our platform resulting in higher error rates for transactions processed through Adyen. For more details - https://status.adyen.com/incident-history#2025

2. resolved 2025-10-24 21:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Email Notifications (US), Email Notifications (EU), Email Notifications (AU)

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-10-24 03:39 UTC

   We’re aware that Chargebee customers may have received a recent email from Chargebee (support@hey.chargebee.com) regarding a certificate update. We want to confirm that the email was an authentic communication from Chargebee. Our team is currently reviewing the distribution list...

2. resolved 2025-10-24 04:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Admin Console (US)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-22 07:05 UTC

   We faced temporary login issues while accessing the Chargebee Admin Portal, and the issue has now been resolved. We apologize for any disruption this may have caused.

2. resolved 2025-10-22 07:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: Admin Console (US), API (US), Checkout (US), Webhooks (US), Dashboard (US), API (EU), Checkout (EU), Webhooks (EU), Admin Console (EU), Dashboard (EU), API (AU), Checkout (AU), Webhooks (AU), Admin Console (AU), Dashboard (AU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 09:42 UTC

   We are currently experiencing a service interruption due to an ongoing AWS outage. Our team is working with AWS to restore full access as soon as possible. For more details - https://health.aws.amazon.com/health/status We sincerely appreciate your patience and understanding...

2. identified 2025-10-20 09:47 UTC

   We have an update from AWS, and we will continue to monitor: "We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information."

3. identified 2025-10-20 10:09 UTC

   Latest note from AWS: "We continue to observe recovery across most of the affected AWS Services. We can confirm global services and features that rely on US-EAST-1 have also recovered. We continue to work towards full resolution and will provide updates as we have more...

4. monitoring 2025-10-20 11:07 UTC

   Between 07:00 AM and 09:27 AM UTC, we experienced increased error rates and latency across multiple services due to an AWS outage specifically related to a DNS resolution issue impacting DynamoDB. Our systems have now recovered, and services are operating normally. We will...

5. monitoring 2025-10-20 14:07 UTC

   AWS has identified and mitigated the issue affecting multiple dependent services. Most AWS operations have recovered, but some residual latency may persist as backlogs clear. We continue to monitor our systems closely for any impact.

6. monitoring 2025-10-20 15:52 UTC

   Some dependent issues with AWS are still being addressed. We continue to monitor our systems closely for any impact.

7. resolved 2025-10-21 02:33 UTC

   AWS has implemented the necessary fix and confirmed that all affected services have been fully restored. Our systems have also been monitored and are now operating normally. We appreciate your patience while we worked with our provider to restore full functionality. AWS will...

8. postmortem 2025-10-30 07:43 UTC

   # **Incident Overview:** **On October 20, 2025**, a major outage in the [**AWS US-EAST-1**](https://aws.amazon.com/message/101925/) region impacted multiple global services, including components critical to our infrastructure. Between **06:46 AM UTC and 09:30 AM UTC**, we...

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-09-10 14:32 UTC

   On September 10th, between 09:17:39 and 09:17:50 UTC, we experienced intermittent API request timeouts in the US region due to an internal server issue. The impact was minimal, and the service has fully recovered. We apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Chargebee's status page.

Affected: API (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-09-10 09:50 UTC

   On September 9th, we experienced intermittent API service interruptions and request timeouts between 18:19 and 19:52 UTC in the US region. This disruption was due to an upstream networking configuration issue on the AWS platform. The service has fully recovered. We apologize for...

Excerpts are shortened. Read the full incident on Chargebee's status page.