Rewindex

CompaniesKlaviyoIncidents

Klaviyo: Cloudflare incident disrupting Klaviyo

No impact listedStatus: resolvedStarted Resolved (-102 min)1 updatestspg.io (opens in new tab)
Part of an outage event

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

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

“…Cloudflare incident disrupting Klaviyo Between 3:48am (US Eastern) and 4:10am (US Eastern) Cloudflare experienced an outage which affected Klaviyo. During this time, users were unable to access Klaviy…”

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 ComputingKlaviyo (this incident)posted +1 h 55 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 ComputingKlaviyo (this incident)posted +1 h 55 min
Klaviyo 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["Klaviyo (this incident)<br/>posted +1 h 55 min"]:::me
  h4 --- 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.

Timeline of updates

  1. resolved

    Between 3:48am (US Eastern) and 4:10am (US Eastern) Cloudflare experienced an outage which affected Klaviyo. During this time, users were unable to access Klaviyo.com and all Klaviyo APIs. During this window, a number of services were affected. Subscription events and click tracking events were lost. Outbound campaign message sending was not affected. Klaviyo is now fully operational and this incident has been resolved. https://www.cloudflarestatus.com/incidents/k9ppxftx8bs5

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

Klaviyo profileRecent Klaviyo incidentsMarkdownJSON