Klaviyo incident

Disrupted Event Processing for All Customers

Critical Resolved View vendor source →

Klaviyo experienced a critical incident on April 23, 2025 affecting Klaviyo API, lasting 1d 4h. The incident has been resolved; the full update timeline is below.

Started
Apr 23, 2025, 06:50 PM UTC
Resolved
Apr 24, 2025, 11:13 PM UTC
Duration
1d 4h
Detected by Pingoru
Apr 23, 2025, 06:50 PM UTC

Affected components

Klaviyo API

Update timeline

  1. investigating Apr 23, 2025, 06:50 PM UTC

    We are experiencing disruption in event processing since 2pm EST. Customers may see high error rates with APIs, missing metrics, and delayed sending. We are investigating the issue and working to mitigate it currently.

  2. identified Apr 23, 2025, 07:41 PM UTC

    We have addressed the underlying issue. We are seeing improvement in event processing, API responses and latency, email sending, and other areas. We are continuing to work on fully restoring normal operations.

  3. monitoring Apr 23, 2025, 10:01 PM UTC

    We have observed recovery of affected systems. We are in the process of replaying affected unsubscribe events, and other remaining queued events have been processed. Event processing, API responses, and latency are all up-to-date. Unfortunately, inbound subscriptions during the affected period can not be replayed. We will provide another update once unsubscribe events have been replayed.

  4. resolved Apr 24, 2025, 11:13 PM UTC

    This incident has been resolved. Affected unsubscribe events have been replayed. And as noted before, inbound subscriptions during the incident period can not be replayed.