- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Segments
- Regions
- us
- Down Index
- 30of 100
What to do
Check whether you use Klaviyo Segments 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 30m it lasted.
Anything that failed between 2026-03-27 04:46 UTC and 2026-03-27 05:15 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 2
- monitoring
Starting around 8:15 PM US Eastern 26th March, we began seeing delays in real-time segment processing for a subset of customers. Segments may be out of date by up to 2.5 hours. Engineering have identified a solution and are working to implement the fix shortly. We will continue to provide updates as real-time segmentation functionality is restored.
provider
- resolved
Real-time segmentation is processing in real-time, and this incident has been resolved.
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-aeb6ed40b9
Is Klaviyo still down?
No, this incident was resolved 2026-03-27 05:15 UTC. For Klaviyo's live state, see https://down.guide/klaviyo.
How long did it last?
30m, from 2026-03-27 04:46 UTC to 2026-03-27 05:15 UTC, by the times Klaviyo posted.
What was affected?
Klaviyo named Segments 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.