Klaviyo experienced a minor incident on May 8, 2026 affecting Klaviyo API and Analytics and 1 more component, lasting 17h 32m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2026, 01:32 AM UTC
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.
- identified May 08, 2026, 02:22 AM UTC
Our engineering team is continuing to monitor areas affected by the upstream service provider. At this stage, event processing has recovered and is working as expected. There remains processing delays for segmentation and analytics. There may be sending delays with Campaigns & Flows that rely include impacted segments and loading issues with reporting pages. We will provide updates as soon as more information is available.
- identified May 08, 2026, 03:46 AM UTC
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.
- identified May 08, 2026, 07:08 AM UTC
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.
- monitoring May 08, 2026, 04:59 PM UTC
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.
- resolved May 08, 2026, 07:05 PM UTC
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.