Chargebee Incident History

1. monitoringOct 22 · 15:43 UTC

   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.

Reported by Chargebee on their status page.

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

Reported by Chargebee on their status page.

1. resolvedOct 10 · 09:24 UTC

   This incident has been resolved.

Reported by Chargebee on their status page.

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

Reported by Chargebee on their status page.

1. resolvedSep 29 · 14:35 UTC

   This incident has been resolved.

Reported by Chargebee on their status page.