- Level
- confirmed
- Worst impact
- Operational
- Regions
- us
What to do
Check whether you use Klaviyo in 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 0m it lasted.
Anything that failed between 2025-12-05 10:42 UTC and 2025-12-05 09:00 UTC may need a replay.Subscribe to Klaviyo's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=klaviyo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Klaviyo 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
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b8e9a1c40e
Is Klaviyo still down?
No, this incident was resolved 2025-12-05 09:00 UTC. For Klaviyo's live state, see https://down.guide/klaviyo.
How long did it last?
0m, from 2025-12-05 10:42 UTC to 2025-12-05 09:00 UTC, by the times Klaviyo posted.
What was affected?
Klaviyo named in us.
What caused it?
Klaviyo hasn't published a root cause. If it does, it shows here.
Where does this come from?
Klaviyo's official status page, https://status.klaviyo.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.