Chargebee Outage History

Chargebee experienced degraded performance with outbound email notifications due to an issue with their email provider, causing delays in system notifications for test sites only. Live production sites remained fully operational and unaffected throughout the incident. The email functionality for test environments was restored after 40 minutes of investigation and coordination with the email provider.

Chargebee experienced login issues with their RevRec portal that prevented users from accessing the service for approximately 1.1 hours. The team identified the root cause and implemented a fix to restore login functionality. The incident was resolved after a brief monitoring period to ensure system stability.

Chargebee experienced intermittent API request timeouts in the US region between May 7, 23:35 UTC and May 8, 00:55 UTC due to an AWS platform issue. The incident affected API functionality for approximately 1 hour and 20 minutes. The team worked with AWS to resolve the underlying platform issue and confirmed full system recovery through monitoring.

Chargebee experienced background processing delays that caused payment status updates to be delayed and third-party integrations to sync more slowly, with webhooks being the primary affected component. The core platform functionality remained unaffected throughout the 29.3-hour incident. The issue was resolved with a deployed patch, followed by a monitoring period to ensure system stability.

Chargebee experienced intermittent API request timeouts in the US Region on February 26th, with failures occurring between 14:23-14:23 UTC and 14:46-14:46 UTC. The API service was affected for approximately 1.7 hours total. The issue was resolved and the team is investigating the root cause with their cloud provider.

A GoCardless API disruption caused elevated error rates for Chargebee transactions processed through GoCardless, with users experiencing blank screens when accessing the GoCardless Dashboard and API disruptions. GoCardless identified the root cause and implemented a fix, with services recovering normally. The incident was fully resolved after 48 minutes.