Klaviyo Status · History · Incident #145
RESOLVEDAPI 503 Errors
Minor · Started Apr 26, 2026 · 3:24 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Klaviyo Status · History · Incident #145
RESOLVEDMinor · Started Apr 26, 2026 · 3:24 AM
Duration
46m
Severity
Minor
Detection lead
—
User reports
—
Summary
We confirmed that all API activity has been stable since the fix was released. Any requests that returned 503 errors during the outage window will need to be retried. This incident has been resolved.
Started
Apr 26, 2026 · 3:24 AM
Resolved
Apr 26, 2026 · 4:11 AM
Duration
46m
Severity
Minor
Event timeline
Identified
Apr 26 · 3:24 AM KlaviyoStarting at approximately 2:27 AM US/Eastern on 04/25/2026, we began experiencing intermittent elevated errors across our APIs. Some customers may experience 503 errors when trying to log into Klaviyo, load certain pages or make API requests. Our Engineering Team has identified the root cause and has implemented mitigations. We'll provide updates as soon as more information is available.
Monitoring
Apr 26 · 3:43 AM KlaviyoWe successfully implemented a fix as of 3:20 AM US/Eastern that restored all API activity. We are continuing to monitor the results.
Resolved
Apr 26 · 4:11 AM KlaviyoWe confirmed that all API activity has been stable since the fix was released. Any requests that returned 503 errors during the outage window will need to be retried. This incident has been resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT