Klaviyo Incident History

1. resolvedOct 29 · 17:05 UTC

   Campaign sending has returned to normal, and all affected campaigns have been repaired and sent. Between approximately 7:59 AM and 11:45 AM US/Eastern on October 29, 2026, some customers experienced delays sending campaigns, and some scheduled campaigns may have appeared stuck or shown no recipients while they processed. We're sorry for the disruption this caused. This incident has been resolved.

Reported by Klaviyo on their status page.

1. resolvedOct 29 · 21:32 UTC

   Flows are no longer skipping profiles with the skip reason "Incorrectly Triggered." As of 1:22 PM US/Eastern on October 29, 2026, we have finished reprocessing the impacted profiles so that eligible messages were sent. We apologize for any disruption this may have caused. This incident has been resolved.

Reported by Klaviyo on their status page.

1. MonitoringOct 28 · 21:49 UTC

   Between 11:00 AM US/Eastern and 5:00 PM US/Eastern on October 28, 2026, some customers may have seen flows skip profiles with the skip reason "Incorrectly Triggered," shown in flow and profile activity. Flows are no longer skipping profiles for this reason, and we are reprocessing impacted profiles. No action is needed from customers, and we will confirm once reprocessing is complete. We continue to monitor closely.

Reported by Klaviyo on their status page.

1. resolvedOct 23 · 13:06 UTC

   Event webhook delivery was fully restored at 2:40 AM US/Eastern on October 23, 2026 after the backlog was processed. Webhook data was retained, and webhook actions in flows were not affected. We apologize for the disruption this caused. This incident has been resolved.

Reported by Klaviyo on their status page.

1. ResolvedOct 23 · 13:06 UTC

   Event webhook delivery was fully restored at 2:40 AM US/Eastern on October 23, 2026 after the backlog was processed. Webhook data was retained, and webhook actions in flows were not affected. We apologize for the disruption this caused. This incident has been resolved.

Reported by Klaviyo on their status page.

1. resolvedOct 17 · 21:51 UTC

   Flow processing has returned to normal, and delayed flow actions - including email, SMS, and push messages, as well as profile and list updates - have fully caught up. Immediate sends were not affected. We apologize for the disruption this caused. This incident has been resolved.

Reported by Klaviyo on their status page.

1. ResolvedOct 17 · 21:51 UTC

   Flow processing has returned to normal, and delayed flow actions - including email, SMS, and push messages, as well as profile and list updates - have fully caught up. Immediate sends were not affected. We apologize for the disruption this caused. This incident has been resolved.

Reported by Klaviyo on their status page.

1. resolvedOct 9 · 02:16 UTC

   As of 10:10 pm Eastern Time on Oct 8th, all delayed analytics have been processed and new analytics are processing in real time. This incident is now resolved.

Reported by Klaviyo on their status page.

1. ResolvedOct 9 · 02:16 UTC

   As of 10:10 pm Eastern Time on Oct 8th, all delayed analytics have been processed and new analytics are processing in real time. This incident is now resolved.

Reported by Klaviyo on their status page.

1. resolvedOct 8 · 16:13 UTC

   Customers can now log in to Klaviyo and load pages normally, and the system remains stable. This incident has been resolved.

Reported by Klaviyo on their status page.

1. ResolvedOct 8 · 16:13 UTC

   Customers can now log in to Klaviyo and load pages normally, and the system remains stable. This incident has been resolved.

Reported by Klaviyo on their status page.