- Level
- confirmed
- Worst impact
- Operational
- Components
- Other
What to do
Check whether you use Klaviyo Other. 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 10h 38m it lasted.
Anything that failed between 2025-11-02 07:03 UTC and 2025-11-02 17:41 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 3
- identified
As of 1:00 AM ET (approximately one hour ago), our Facebook integration sync encountered a failure, resulting in a temporary delay in data sync. We have confirmed that no data has been lost, and the system failure is strictly impacting sync times. The root cause has been successfully identified, and our engineering team is actively working on deploying the necessary fix.
provider
- monitoring
A fix has been identified and we are monitoring the results.
provider
- resolved
The incident is now resolved. All delayed data for Facebook Integrations, which occurred between 1:00 AM and 2:00 AM, has been fully restored.
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-cb2781845c
Is Klaviyo still down?
No, this incident was resolved 2025-11-02 17:41 UTC. For Klaviyo's live state, see https://down.guide/klaviyo.
How long did it last?
10h 38m, from 2025-11-02 07:03 UTC to 2025-11-02 17:41 UTC, by the times Klaviyo posted.
What was affected?
Klaviyo named Other.
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.