Rewindex

CompaniesChargebeeIncidents

Chargebee: Cloudflare Service Impact

MinorStatus: resolvedStarted Resolved (43 min)3 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Dec 5, 2025 · 46 vendors, 46 incidents

Chargebee’s incident blames Cloudflare as the cause. (hop 1, posted +30 min vs the first vendor naming Cloudflare)

“…Cloudflare Service Impact This incident has been resolved. This incident has been resolved. We are currently experiencing disruptions to our support ticketing and chat systems. Certain integrations an…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamed CloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingChargebee (this incident)posted +30 min
Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamedCloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingChargebee (this incident)posted +30 min
Chargebee is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>18 vendors, 18 blamed Cloudflare<br/>Unbounce, Expo, GitLab +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Klaviyo"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed Cloudflare<br/>Bitrise, Sigma Computing"]:::blames
  root --> later
  me["Chargebee (this incident)<br/>posted +30 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: HubSpotThird Party Integrations - HubSpot

Timeline of updates

  1. identified

    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

    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

    This incident has been resolved.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Chargebee profileRecent Chargebee incidentsMarkdownJSON