- Level
- confirmed
- Worst impact
- Degraded
- Components
- Server-side, Segments, Processing, Analytics
- Down Index
- 25of 100
What to do
Check whether you use Klaviyo Server-side, Segments, Processing, Analytics. 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 17h 33m it lasted.
Anything that failed between 2026-05-08 01:32 UTC and 2026-05-08 19:05 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 6
- investigating
We are currently investigating an issue affecting analytics and reporting, flows, campaigns, and segmentation. This issue appears to be related to a disruption with an upstream service provider. Customers may experience errors or be unable to load flows and campaigns pages, see delays in real-time segmentation updates, and find analytics data temporarily unavailable. Our team is actively working to resolve this. We'll provide updates as soon as more information is available.
provider
- identified
Our engineering team continues to investigate areas affected by an upstream service provider. Customers may experience processing delays for segmentation and analytics, and loading issues with reporting pages. For campaigns, sends may not reach the most up-to-date audience due to segmentation delays. Segment-triggered flows may also fail to trigger correctly as profiles may not be added to or removed from segments as expected. We'll provide updates as soon as more information is available.
provider
- identified
A subset of customers are currently experiencing segmentation processing delays of approximately 1.5 hours and may find that analytics data is not fully up to date. Access to reporting pages has been restored and our engineering team is actively working to bring segmentation and analytics back to real time. We'll provide updates as soon as more information is available.
provider
- identified
Segmentation has been restored to realtime processing. Our engineering team continues to restore the remaining affected analytics. We will continue to provide updates as real-time analytics functionality resumes.
provider
- monitoring
Segmentation has been restored to real-time processing, and campaign and forms analytics have now recovered. This was a reporting UI display issue only, no data was lost. Our engineering team continues to monitor closely until our upstream service provider has confirmed full recovery.
provider
- resolved
Segmentation continues to process in real-time and is fully recovered. We determined the delays resulted from instability with an upstream infrastructure provider (AWS). This incident is now 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-6f7d55da63
Is Klaviyo still down?
No, this incident was resolved 2026-05-08 19:05 UTC. For Klaviyo's live state, see https://down.guide/klaviyo.
How long did it last?
17h 33m, from 2026-05-08 01:32 UTC to 2026-05-08 19:05 UTC, by the times Klaviyo posted.
What was affected?
Klaviyo named Server-side, Segments, Processing, Analytics.
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.