Live / Klaviyo / Incident
Klaviyo: Flow Sending Delays
Klaviyo · klaviyo.comMajor incidentResolved2026-10-17 21:51 UTC
Public — what happened
Summary
Klaviyo said that starting at 17:01 UTC on 2026-10-17 some customers saw automated flow messages go out later than expected, while messages sent immediately were not affected. The company said it identified the cause at 17:35 UTC and spent the next several hours working on a fix while delayed messages stayed queued. By 20:59 UTC Klaviyo said flow processing had resumed and the backlog was clearing, and it described the problem as having touched all flow processing, including email, SMS, WhatsApp, push messages and flow updates to profiles and lists. The incident is still marked as monitoring, and Klaviyo said some customers may still see delays until the backlog catches up.
Affected
Email Sending, Text Message Sending, WhatsApp Sending, Mobile Push Sending, Flow Editor, Processing
Timeline
- Started — 2026-10-17 17:01 UTC
- Investigating — 2026-10-17 17:01 UTC (2 updates)
- Identified — 2026-10-17 17:35 UTC (6 updates)
- Monitoring — 2026-10-17 20:59 UTC (2 updates)
- Resolved — 2026-10-17 21:51 UTC · 4h 49m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Klaviyo against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Klaviyo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Klaviyo report →
More from Klaviyo
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.