Clarification on recent customer communication regarding G2 certificate update

What to do

• Check whether you use Chargebee Email Notifications (US), Email Notifications (EU), Email Notifications (AU) in eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 38m it lasted.

  Anything that failed between 2025-10-24 03:39 UTC and 2025-10-24 04:17 UTC may need a replay.

• Subscribe to Chargebee's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=chargebee works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Chargebee 2

1. monitoringOct 24, 2025, 3:39 AM 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 to ensure that future communications reach only the intended recipients and are as relevant as possible. There is no security or phishing concern associated with this communication, all emails were sent from our verified Chargebee systems. We appreciate your understanding as we review this further.

   provider

2. resolvedOct 24, 2025, 4:17 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.