We started checking Klaviyo on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Klaviyo reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Klaviyo's own status page declared. Below it, any public chatter we saw about Klaviyo and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Klaviyo's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Klaviyo in the last 24 hours, which is not evidence that nothing is wrong.
Klaviyo's status page
Klaviyo app slowness: partial outage
Klaviyo app slowness: partial outage, from before this window to 17:45 UTC.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Klaviyo's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Klaviyo next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
Bluesky posts1 in the last hour
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
448
US-West
100.00%
347
Europe
100.00%
316
Asia-Pacific
100.00%
193
Their declared record
Klaviyo's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Klaviyo app slownessPartial outage
Nov 4, 2026, 4:17 PM UTC to Nov 5, 2026, 5:31 PM UTC (1d 1h)resolved
their latest update (Nov 5, 2026, 5:31 PM UTC): Reporting, metrics, and page load times remain stable, and attribution settings changes are processing normally again. We apologize for the disruption this caused. This incident has been resolved.
Campaign Sending DelaysPartial outage
Oct 29, 2026, 2:55 PM UTC to Oct 29, 2026, 5:05 PM UTC (2h 10m)resolved
their latest update (Oct 29, 2026, 5:05 PM 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…
Elevated flow recipient skipsAll systems operational
Oct 28, 2026, 9:49 PM UTC to Oct 29, 2026, 9:32 PM UTC (23h 43m)resolved
their latest update (Oct 29, 2026, 9:32 PM 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 in…
Outbound Webhook DelaysPartial outage
Oct 22, 2026, 10:20 PM UTC to Oct 23, 2026, 1:06 PM UTC (14h 47m)resolved
their latest update (Oct 23, 2026, 1:06 PM 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.
Flow Sending DelaysPartial outage
Oct 17, 2026, 5:01 PM UTC to Oct 17, 2026, 9:51 PM UTC (4h 49m)resolved
their latest update (Oct 17, 2026, 9:51 PM 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.
Analytics Events Processing DelaysMinor incident
Oct 9, 2026, 12:10 AM UTC to Oct 9, 2026, 2:16 AM UTC (2h 6m)resolved
their latest update (Oct 9, 2026, 2:16 AM 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.
Login and page loading issuesMajor outage
Oct 8, 2026, 3:00 PM UTC to Oct 8, 2026, 4:13 PM UTC (1h 13m)resolved
their latest update (Oct 8, 2026, 4:13 PM UTC): Customers can now log in to Klaviyo and load pages normally, and the system remains stable. This incident has been resolved.
Flow sending delaysMinor incident
Sep 21, 2026, 3:56 PM UTC to Sep 21, 2026, 5:58 PM UTC (2h 3m)resolved
their latest update (Sep 21, 2026, 5:58 PM UTC): Flow message sending has fully recovered and is processing at normal speeds. Delayed messages were not lost and have since been delivered. This incident has been resolved.
Flow sending delaysMinor incident
Sep 17, 2026, 5:10 PM UTC to Sep 17, 2026, 7:46 PM UTC (2h 35m)resolved
their latest update (Sep 17, 2026, 7:46 PM UTC): Flow message sending has fully recovered and is processing at normal speeds. Delayed messages were not lost and have since been delivered. This incident has been resolved.
Sending delays for event-triggered flowsMinor incident
Sep 14, 2026, 9:30 PM UTC to Sep 15, 2026, 1:51 AM UTC (4h 21m)resolved
their latest update (Sep 15, 2026, 1:51 AM UTC): The backlog of delayed event-triggered flows has been fully processed and all systems are now operating normally. We apologize for the disruption this caused. This incident has been resolved.
Showing the 10 most recent of 51 incidents Klaviyo has declared in the history we hold.
These entries are Klaviyo's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Klaviyo's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.