Is Klaviyo down?

Last checked 8m ago
Current status
Klaviyo is up

No incidents right now.

Official status page: https://status.klaviyo.com · Polled every 5 minutes · 40 components tracked

Klaviyo is operational right now. Last checked 8m ago; the most recent incident resolved 16h ago.

Real-time Klaviyo status, recent outages, and incident history — pulled directly from Klaviyo's official status page at https://status.klaviyo.com every 5 minutes. Pingoru tracks 40 Klaviyo services and has captured 16 incidents in the last 90 days (98.37% uptime). Get email, Slack, Discord, or webhook alerts the moment Klaviyo reports a new incident — free for 5 monitors, no credit card.

Users who monitor Klaviyo also follow these Marketing services: Mailgun Iterable Braze Brevo Customer.io ZoomInfo Optimizely SurveyMonkey Yotpo Litmus View all 6,000+ providers
Klaviyo uptime 98.37% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 35m
    Started Sep 17, 2026, 05:10 PM UTC · Resolved Sep 17, 2026, 07:46 PM UTC
    Email SendingProcessingWhatsApp SendingText Message SendingMobile Push Sending
    Timeline · 5 updates
    • investigating · Sep 17, 2026, 05:10 PM UTC

      We are investigating reports of delays affecting flow message sending. Some customers may see flow messages send later than expected. We will share another update as soon as we have more information.

    • identified · Sep 17, 2026, 05:31 PM UTC

      We have identified the cause of the delays affecting flow message sending and are working on a fix. Some customers may continue to see flow messages send later than expected while we resolve this. We will share another update shortly.

    • identified · Sep 17, 2026, 06:30 PM UTC

      We are seeing early signs of improvement and continue to work towards full recovery. Customers may still see flow messages send later than expected. We will share another update shortly.

    • monitoring · Sep 17, 2026, 07:21 PM UTC

      Flow message sending is recovering, and delays are continuing to clear. Some customers may still see flow messages send later than expected as remaining processing catches up. We continue to monitor closely and appreciate your patience throughout this incident.

    • resolved · Sep 17, 2026, 07: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.

    Latest: 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.

  2. Resolved 4h 21m
    Started Sep 14, 2026, 09:30 PM UTC · Resolved Sep 15, 2026, 01:51 AM UTC
    Email SendingProcessingWhatsApp SendingText Message SendingMobile Push Sending
    Timeline · 6 updates
    • investigating · Sep 14, 2026, 09:30 PM UTC

      We are currently investigating a delay in the sending of event-triggered flows. Some customers may see these flows send later than expected. Scheduled campaigns and other areas of Klaviyo are not affected. We will share another update as soon as we have more information.

    • investigating · Sep 14, 2026, 10:22 PM UTC

      We are continuing to investigate the delays affecting event-triggered flows. Some customers may see these flows send with delays of approximately 90 minutes while we work to restore normal performance. We will provide another update shortly.

    • identified · Sep 14, 2026, 11:18 PM UTC

      We have identified the cause of the delays affecting event-triggered flows. Affected flows may see delays of approximately 2 hours. Our team is now working on a fix to restore processing back to normal speed. We are working to resolve this as quickly as possible and will share another update shortly.

    • identified · Sep 15, 2026, 12:25 AM UTC

      Our team is continuing to implement a fix to mitigate the delays affecting event-triggered flows. Delays to affected flows remain at approximately 2 hours. We are working to resolve this as quickly as possible and will share another update shortly.

    • monitoring · Sep 15, 2026, 01:07 AM UTC

      Event-triggered flow processing is recovering, and our systems are now working through the backlog of delayed messages. Delayed messages will continue to send automatically as the backlog clears. A fix has been deployed and system performance is improving. We continue to monitor closely and appreciate your patience throughout this incident.

    • resolved · Sep 15, 2026, 01: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.

    Latest: 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 bee…

  3. Resolved 3h 33m
    Started Aug 27, 2026, 12:09 AM UTC · Resolved Aug 27, 2026, 03:42 AM UTC
    Email SendingProcessingWhatsApp SendingText Message SendingMobile Push Sending
    Timeline · 4 updates
    • investigating · Aug 27, 2026, 12:09 AM UTC

      At 3:25 PM US/Eastern on August 26, 2026, we began experiencing an issue affecting where profiles are not progressing past a time delay action in flows as expected. This is affecting flow sending across all messaging channels, including email, text messaging, push, and WhatsApp. Message sending from campaigns and flows that do not include time delay actions are not impacted. We are actively working on a fix. We will share another update as soon as we have more information.

    • identified · Aug 27, 2026, 01:15 AM UTC

      Our Engineering team has identified the cause of this issue and is working to implement a fix to resolve the remaining impact on sending for flows affected by the time delay issue. Once the fix is rolled out, we will review and repair any impacted flows. We are working to resolve this as quickly as possible and will share another update shortly.

    • monitoring · Aug 27, 2026, 01:51 AM UTC

      As of 9:30PM US/Eastern, flows have resumed sending as expected across all affected messaging channels. We are processing the backlog of affected flow messages. A fix has been deployed and system performance is improving. We continue to monitor closely and appreciate your patience throughout this incident.

    • resolved · Aug 27, 2026, 03:42 AM UTC

      As of 11:26 PM US/Eastern on August 26, 2026, the repair to process affected flow messages from the window of impact has been completed, and flow sending has resumed as expected across all channels. We apologize for the disruption this caused. This incident has been resolved.

    Latest: As of 11:26 PM US/Eastern on August 26, 2026, the repair to process affected flow messages from the window of impact has been completed, and flow sending has resumed as expected ac…

  4. Resolved 1h 23m
    Started Aug 19, 2026, 05:15 PM UTC · Resolved Aug 19, 2026, 06:38 PM UTC
    SegmentsProfiles
    Timeline · 3 updates
    • identified · Aug 19, 2026, 05:15 PM UTC

      We are currently experiencing delays of up to approximately 3 hours in how quickly recent profile property updates are reflected in real-time segments. This means changes to profiles may take longer than usual to update segment membership, which can affect segment-based targeting. Email and SMS sending and other core functions are operating normally. We are actively working to resolve this and will share another update as soon as we have more information.

    • monitoring · Aug 19, 2026, 06:13 PM UTC

      A fix has been deployed and system performance is improving. Recent profile property updates are now being reflected in real-time segments more quickly, and the delay has improved to approximately 2.5 hours. Changes to profiles may still take slightly longer than usual to update segment membership as the system continues to catch up. Email and SMS sending and other core functions remain unaffected. We continue to monitor closely and appreciate your patience throughout this incident.

    • resolved · Aug 19, 2026, 06:38 PM UTC

      Profile property updates are now being reflected in real-time segments at normal speed. Any profile property changes made during the incident window have been reflected in segment membership as expected, and no action is required on your part. This incident has been resolved.

    Latest: Profile property updates are now being reflected in real-time segments at normal speed. Any profile property changes made during the incident window have been reflected in segment …

  5. Resolved 9m
    Started Aug 12, 2026, 06:04 PM UTC · Resolved Aug 12, 2026, 06:14 PM UTC
    Email SendingText Message SendingMobile Push SendingWhatsApp Sending
    Timeline · 2 updates
    • monitoring · Aug 12, 2026, 06:04 PM UTC

      Between 1:15 PM and 2:00 PM US/Eastern on August 12, 2026, some customers experienced errors when scheduling campaigns, and some scheduled campaigns were canceled. If you scheduled a campaign during this window, we recommend checking its status in your account. A fix has been deployed and system performance is improving. We continue to monitor closely and will confirm once fully resolved.

    • resolved · Aug 12, 2026, 06:14 PM UTC

      Campaign scheduling has returned to normal operation. If you scheduled a campaign between 1:15 PM and 2:00 PM US/Eastern on August 12, 2026, we recommend checking its status and rescheduling if needed. This incident has been resolved.

    Latest: Campaign scheduling has returned to normal operation. If you scheduled a campaign between 1:15 PM and 2:00 PM US/Eastern on August 12, 2026, we recommend checking its status and re…

See the full Klaviyo outage history

6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Klaviyo outage history →

Or sign up free to get alerts when Klaviyo breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 11 incidents View full outage history →