Is Klaviyo Down?

No — Klaviyo is up

Reachable from all 8 checked regions

Average response time: 406ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.klaviyo.com

Klaviyo uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

409ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad

256ms

DNS 0ms TCP 1ms TLS 7ms TTFB 254ms

jnb

494ms

DNS 0ms TCP 1ms TLS 5ms TTFB 491ms

lax

322ms

DNS 0ms TCP 1ms TLS 8ms TTFB 319ms

lhr

369ms

DNS 0ms TCP 2ms TLS 8ms TTFB 366ms

nrt

442ms

DNS 0ms TCP 1ms TLS 7ms TTFB 439ms

ord

331ms

DNS 0ms TCP 2ms TLS 11ms TTFB 329ms

sin

490ms

DNS 0ms TCP 1ms TLS 7ms TTFB 486ms

sjc

332ms

DNS 0ms TCP 4ms TLS 9ms TTFB 330ms

syd

471ms

DNS 0ms TCP 1ms TLS 6ms TTFB 468ms

What Klaviyo does

Klaviyo is a marketing automation platform built around ecommerce customer data. It stores customer profiles and purchase events, then sends email, SMS, WhatsApp and mobile push messages from flows triggered by that behaviour. Online stores wire it into checkout and browse tracking, so it sits between a storefront and most of the automated messages a customer receives after buying.

What an outage looks like

Campaigns and flows stop sending, or send late once a backlog clears. The Klaviyo app fails to load dashboards and reporting. Sign-up forms embedded on a storefront may not render, or may accept an address without recording it. Server-side and client-side event tracking can drop, so abandoned-cart and browse-abandonment flows never fire because the trigger event never arrives.

What to do about it

Check status.klaviyo.com, which separates Email Sending, Text Message Sending, WhatsApp Sending and Mobile Push Sending from the Klaviyo App itself, so a sending incident and a dashboard incident look different there. Processing, the Campaign Editor and the Flow Editor are listed as their own components. Before resending a campaign, confirm whether the original eventually went out, because a duplicate send to a large list cannot be recalled.

Is it down for everyone, or just you?

If this page says Klaviyo is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Klaviyo outage FAQ

Is Klaviyo down, or is my store integration broken?

Check the Klaviyo App component on status.klaviyo.com first, then the Server-side and Client-side tracking components. If all three are green and your events still do not arrive, the problem is more likely your API key, the store plugin or a tracking snippet than Klaviyo. The status page lists sending and tracking separately, so one can fail while the other keeps working.

Will a scheduled campaign still send during a Klaviyo outage?

It depends which component is affected. Klaviyo lists Processing separately from each sending channel, so a campaign can be built and scheduled while sending is degraded, or queue up behind a processing incident. Check the specific channel component for your campaign rather than the overall banner, and avoid rescheduling until you can confirm the original did not send.

Does a Klaviyo outage stop my store from taking orders?

No. Klaviyo sits alongside your storefront rather than inside the payment path, so checkout on Shopify or another platform continues while Klaviyo is unavailable. What you lose is the messaging layer: order confirmations sent through Klaviyo, post-purchase flows and sign-up form captures. Orders placed during the incident still exist in your store platform and can be reconciled afterwards.

Do abandoned-cart flows recover events missed during an outage?

Not reliably, because the flow depends on a tracking event that was never recorded. If Server-side or Client-side tracking dropped during the incident, those browse and cart events are gone rather than delayed, so the flow has nothing to trigger from. After a tracking incident it is worth sampling a few known sessions to see whether the events landed before assuming the flows simply ran late.

How we measure this

We request Klaviyo's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Klaviyo publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Klaviyo goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required