Klaviyo Outage History

Started Oct 17, 2026, 05:01 PM UTC· resolved Oct 17, 2026, 09:51 PM UTC

1. investigating Oct 17, 2026, 05:01 PM UTC

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

2. investigating Oct 17, 2026, 05:31 PM UTC

   We are continuing to investigate delays affecting some flow email sending. Immediate sends remain unaffected. We will share another update as soon as we have more information.

3. identified Oct 17, 2026, 05:35 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.

4. identified Oct 17, 2026, 06:06 PM UTC

   We are continuing to work on the fix for this issue. Some customers may continue to see flow emails send later than expected while we resolve this. Immediate sends remain unaffected. We will share another update shortly.

5. identified Oct 17, 2026, 06:31 PM UTC

   We are actively working to clear the delayed flow emails and restore normal flow email sending. Some customers may still see flow emails send later than expected while this work completes. Immediate sends remain unaffected. We will share another update shortly.

6. identified Oct 17, 2026, 07:04 PM UTC

   We are still working to clear the delayed flow execution, and flow sending has not yet returned to normal. Some customers may continue to see messages send later than expected while we complete this work. Immediate sends remain unaffected. We will share another update shortly.

7. identified Oct 17, 2026, 07:42 PM UTC

   We are continuing to work on the fix for this issue. Some customers may continue to experience delays in flow processing while we resolve this. Immediate sends remain unaffected. We will share another update shortly.

8. identified Oct 17, 2026, 08:22 PM UTC

   We are continuing to work on resolving the delays affecting flow processing. Some customers may continue to experience delays in their flows while we work through this. Immediate sends remain unaffected, and delayed messages remain queued while we work to process them. We will share another update shortly.

9. monitoring Oct 17, 2026, 08:59 PM UTC

   Flow processing has resumed and the delayed backlog is actively clearing. This incident affected all flow processing - including flow-triggered email, SMS, WhatsApp and push messages, as well as flow updates to profiles and lists. Some customers may continue to see delays until the backlog fully catches up. Immediate sends were not affected. We continue to monitor closely and appreciate your patience throughout this incident.

10. monitoring Oct 17, 2026, 09:34 PM UTC

    Delays have now largely cleared, though some customers may still see flow messages send later than expected. We continue to monitor closely and appreciate your patience throughout this incident.

11. resolved Oct 17, 2026, 09: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.

Read the full incident report →

Started Oct 09, 2026, 12:10 AM UTC· resolved Oct 09, 2026, 02:16 AM UTC

1. identified Oct 09, 2026, 12:10 AM UTC

   All customers are experiencing delays of up to an hour in analytics events, so Sent and Delivered reporting and received profile events may temporarily appear missing. Campaign and flow sending, along with open and click events, are not affected. We have identified the cause of the delays. We are working to resolve this as quickly as possible and will share another update shortly.

2. identified Oct 09, 2026, 01:21 AM UTC

   Delays in analytics events have increased and now reach up to 1 hour and 45 minutes for all customers. Segments that rely on these events may not be up to date while our Engineering team actively processes the backlog. Campaign and flow sending, along with open and click events, remain unaffected. We are working to resolve this as quickly as possible and will share another update shortly.

3. monitoring Oct 09, 2026, 02:09 AM UTC

   Delays have now largely cleared. We continue to monitor closely and will share another update shortly.

4. resolved Oct 09, 2026, 02: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.

Read the full incident report →

Started Oct 08, 2026, 03:00 PM UTC· resolved Oct 08, 2026, 04:13 PM UTC

1. investigating Oct 08, 2026, 03:00 PM UTC

   We are investigating reports that some customers are unable to log in to Klaviyo or are seeing pages load slowly or not at all. Our team is actively working to restore normal access. We will share another update as soon as we have more information.

2. investigating Oct 08, 2026, 03:29 PM UTC

   We are continuing to investigate issues preventing some customers from logging in to Klaviyo or loading pages in the app. We have not seen any impact to campaign or flow sending. We will share another update as soon as we have more information.

3. identified Oct 08, 2026, 03:49 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Oct 08, 2026, 04:06 PM UTC

   A fix has been deployed, and customers should now be able to log in to Klaviyo and load pages normally. If you were logged out during this incident, you may need to log in again. We continue to monitor closely and appreciate your patience throughout this incident.

5. resolved Oct 08, 2026, 04:13 PM UTC

   Customers can now log in to Klaviyo and load pages normally, and the system remains stable. This incident has been resolved.

Read the full incident report →

Started Sep 21, 2026, 03:56 PM UTC· resolved Sep 21, 2026, 05:58 PM UTC

1. investigating Sep 21, 2026, 03:56 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.

2. investigating Sep 21, 2026, 03:56 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 21, 2026, 04:26 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.

4. monitoring Sep 21, 2026, 04:42 PM UTC

   Flow message sending is recovering, and delays are clearing. 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.

5. monitoring Sep 21, 2026, 05:43 PM UTC

   Delays have now largely cleared but some customers may still see flow messages send later than expected. We continue to monitor closely and will share another update shortly.

6. resolved Sep 21, 2026, 05: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.

Read the full incident report →

Started Sep 14, 2026, 09:30 PM UTC· resolved Sep 15, 2026, 01:51 AM UTC

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

Read the full incident report →

Started Aug 27, 2026, 12:09 AM UTC· resolved Aug 27, 2026, 03:42 AM UTC

1. 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.

2. 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.

3. 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.

4. 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.

Read the full incident report →

Started Aug 19, 2026, 05:15 PM UTC· resolved Aug 19, 2026, 06:38 PM UTC

1. 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.

2. 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.

3. 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.

Read the full incident report →

Started Aug 12, 2026, 06:04 PM UTC· resolved Aug 12, 2026, 06:14 PM UTC

1. 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.

2. 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.

Read the full incident report →

Started Aug 05, 2026, 04:47 PM UTC· resolved Aug 05, 2026, 05:54 PM UTC

1. investigating Aug 05, 2026, 04:47 PM UTC

   Beginning around 12:00 PM US/Eastern on August 5, 2026, we began investigating an issue affecting some email subscription and campaign features. Customers using double opt-in may find that new subscribers are not receiving confirmation emails as expected. Some users may encounter errors when sending preview emails, scheduling campaigns, or checking estimated recipient counts. Our team is working to resolve this. We will share another update as soon as we have more information.

2. identified Aug 05, 2026, 05:26 PM UTC

   We have identified the source of the issue affecting some email subscription and campaign features. Customers may continue to see errors when sending preview emails and customers using double opt-in may find that new subscribers are not receiving confirmation emails. Campaign scheduling has recovered and is working as expected. We are working to resolve this as quickly as possible and will share another update shortly.

3. monitoring Aug 05, 2026, 05:36 PM UTC

   A fix has been deployed and the affected email subscription and campaign features have recovered. Double opt-in confirmation emails are sending again, and preview emails and estimated recipient counts are working as expected. We continue to monitor closely and appreciate your patience throughout this incident.

4. resolved Aug 05, 2026, 05:54 PM UTC

   The email subscription and campaign features affected by this incident remain stable and are operating normally. Double opt-in confirmation emails, preview emails, and estimated recipient counts have returned to normal operation. Confirmation emails that failed to send during the incident are being resent. This incident has been resolved.

Read the full incident report →

Started Jul 23, 2026, 02:35 PM UTC· resolved Jul 23, 2026, 04:01 PM UTC

1. identified Jul 23, 2026, 02:35 PM UTC

   Beginning around 8:09 AM US/Eastern on July 23, 2026, profile imports started through the API, CSV upload, or SFTP may fail to complete, and the imported profiles may not be created. New integrations connected during this period may also be delayed in starting their initial sync. We have identified the cause and are deploying a fix. We are working to resolve this as quickly as possible and will share another update shortly.

2. monitoring Jul 23, 2026, 03:16 PM UTC

   Profile imports have recovered, and imports through the API, CSV upload, or SFTP are processing normally again. Integrations connected during the impact window are also resuming their initial syncs. Our team is working to reprocess API imports that failed during the incident. We continue to monitor closely and appreciate your patience throughout this incident.

3. resolved Jul 23, 2026, 04:01 PM UTC

   The system remains stable, and imports through the API, CSV upload, or SFTP are processing normally. Imports that failed during the incident were not reprocessed automatically. If an import you started between 8:00 AM and 11:00 AM US/Eastern on July 23, 2026 did not complete, please re-run it to ensure those profiles are imported. This incident has been resolved.

Read the full incident report →

Started Jul 21, 2026, 08:36 PM UTC· resolved Jul 21, 2026, 09:09 PM UTC

1. investigating Jul 21, 2026, 08:36 PM UTC

   We are currently investigating an issue impacting SMS subscriptions, delays in SMS sending, and errors when creating or scheduling SMS and WhatsApp campaigns. We are working to restore normal service as quickly as possible. We will share another update as soon as we have more information.

2. identified Jul 21, 2026, 08:47 PM UTC

   We have identified the cause of the issue and a fix has been implemented. We are starting to see improvements in system performance.

3. monitoring Jul 21, 2026, 08:57 PM UTC

   System performance for SMS opt-in forms, sending, and campaign creation and scheduling remains stable. We continue to monitor closely and appreciate your patience throughout this incident.

4. resolved Jul 21, 2026, 09:09 PM UTC

   SMS subscriptions, SMS sending, and the creation and scheduling of SMS and WhatsApp campaigns are operating as expected. This incident has been resolved.

Read the full incident report →

Started Jul 09, 2026, 01:52 AM UTC· resolved Jul 10, 2026, 09:01 PM UTC

1. investigating Jul 09, 2026, 01:52 AM UTC

   At 4:00 PM US/Eastern on July 8, 2026, we identified delays syncing product updates from integrations using webhooks. This is causing catalog data, including in Templates and the Customer Hub, to not update in real time. Customer may see product data being out of date by up to 4 hours. Sending is not impacted but the product data in templates may not reflect real-time information. We are working to resolve this as quickly as possible and will share another update shortly.

2. identified Jul 09, 2026, 03:14 AM UTC

   As of 9:45 PM US/Eastern on July 8, 2026, we paused processing new webhooks for product catalogs while we continue working on a fix. Catalog data, including in Templates and Customer Hub, will remain out of date until syncing resumes. Our engineering team is actively working to restore realtime catalog updates. We'll provide updates as soon as more information is available.

3. monitoring Jul 09, 2026, 04:34 AM UTC

   As of 11:13 PM US/Eastern on July 8, 2026, we have resumed processing webhooks. This means all new webhooks from integrations which use webhooks to update products are now syncing in real time. Our Engineering Team is working implement a repair to catch up on any product update webhooks from during window of impact (9:45 PM and 11:13 PM US/Eastern July 8, 2026). We will confirm once the repair has been complete and the incident has been fully resolved.

4. monitoring Jul 09, 2026, 04:13 PM UTC

   Product updates from ecommerce integrations are continuing to sync normally in real time. A background repair to fully update records from the earlier impact window (9:45 PM to 11:13 PM US/Eastern on July 8, 2026) is still in progress. We will confirm once this repair is complete.

5. resolved Jul 10, 2026, 09:01 PM UTC

   The repair to catch up on product update webhooks from the window of impact has been completed, and affected product data is up to date. This incident has been resolved.

Read the full incident report →

Started Jul 07, 2026, 03:33 PM UTC· resolved Jul 07, 2026, 04:56 PM UTC

1. investigating Jul 07, 2026, 03:33 PM UTC

   Customers may be experiencing slower than usual performance when loading or navigating Klaviyo, and some sends may be delayed. We are actively investigating. We will share another update as soon as we have more information.

2. identified Jul 07, 2026, 03:56 PM UTC

   Performance issues affecting login and general navigation in Klaviyo have recovered, and those areas are now operating normally. Some customers may still be experiencing delays with sends while we work to fully restore normal processing. We have identified the cause and are working to resolve the remaining impact as quickly as possible. We will share another update shortly.

3. identified Jul 07, 2026, 04:32 PM UTC

   Campaign and flow sends are now delayed by less than 30 minutes and are continuing to recover. Login and navigation are operating normally. We will share another update shortly.

4. monitoring Jul 07, 2026, 04:47 PM UTC

   Sending delays have recovered, and login and navigation are operating normally. We continue to monitor closely and appreciate your patience throughout this incident.

5. resolved Jul 07, 2026, 04:56 PM UTC

   All systems are operating normally. This incident has been resolved.

Read the full incident report →

Started Jul 02, 2026, 12:17 PM UTC· resolved Jul 02, 2026, 02:17 PM UTC

1. investigating Jul 02, 2026, 12:17 PM UTC

   Starting at 02:30AM US/Eastern on 07/02/2026, a subset of customers are currently experiencing an increase in bounced emails to Yahoo and AOL recipients with the reason of "554 Message not allowed - [PH01] Email not accepted for policy reasons.". Our Engineering and Deliverability teams are actively investigating and working with Yahoo to resolve the issue. We do not recommend resending to those bounced recipients at this moment in time. CCP: https://docs.google.com/document/d/1YdH_E0iEhH_GkCjVoxBJ2-y32iPKf5JnrANic-R_s7k/edit?tab=t.0

2. resolved Jul 02, 2026, 02:17 PM UTC

   The block within the Yahoo infrastructure that resulted in these elevated bounces has been resolved. Customers can safely resend to bounced recipients from this time period. This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 02:49 PM UTC· resolved Jun 12, 2026, 05:30 PM UTC

1. investigating Jun 12, 2026, 02:49 PM UTC

   Customers are currently experiencing issues with Meta-connected features in Klaviyo, including WhatsApp messaging, Meta integrations, and Instagram connectivity. We are investigating a disruption with an upstream provider and will share another update as soon as we have more information.

2. identified Jun 12, 2026, 03:48 PM UTC

   Customers may continue to experience issues with Meta-connected features in Klaviyo, including WhatsApp messaging, Meta integrations, and Instagram connectivity. This is caused by a disruption at an upstream provider that affects connections to these features. We have begun to see partial recovery, and some messages are now sending successfully. We are working to resolve this quickly and will share another update as soon as more information is available.

3. monitoring Jun 12, 2026, 05:19 PM UTC

   We are seeing further recovery with WhatsApp messaging, Meta integrations, and Instagram connectivity. WhatsApp messaging should no longer encounter failures. We've replayed all failed messages during this time period. We continue to monitor and will confirm once recovery has completed.

4. resolved Jun 12, 2026, 05:30 PM UTC

   Meta-connected features in Klaviyo, including WhatsApp messaging, Meta integrations, and Instagram connectivity, have returned to normal. Messages that failed during the disruption were reprocessed, though a small number that did not reach Klaviyo could not be recovered. This incident has been resolved.

Read the full incident report →

Started Jun 10, 2026, 06:47 PM UTC· resolved Jun 10, 2026, 07:46 PM UTC

1. investigating Jun 10, 2026, 06:47 PM UTC

   Customers may be experiencing an error when selecting a template while creating or editing a campaign. Our team is actively investigating and will share another update as soon as we have more information.

2. identified Jun 10, 2026, 07:02 PM UTC

   We have identified the root cause and are working on a fix. We will share another update shortly.

3. monitoring Jun 10, 2026, 07:23 PM UTC

   A fix has been deployed and system performance is improving. Customers should start to be able to successfully select a template. We continue to monitor closely and appreciate your patience throughout this incident.

4. resolved Jun 10, 2026, 07:46 PM UTC

   Customers should no longer see any errors when selecting a template while creating or editing a campaign. This incident has been resolved.

Read the full incident report →

Started Jun 08, 2026, 09:10 PM UTC· resolved Jun 09, 2026, 12:49 AM UTC

1. investigating Jun 08, 2026, 09:10 PM UTC

   Some customers may be experiencing delays with campaign sending, where sends are currently stuck in processing. We are investigating the issue and will provide an update as soon as we have more information.

2. identified Jun 08, 2026, 09:19 PM UTC

   We have identified the root cause and are working on a fix. We will share another update shortly.

3. identified Jun 08, 2026, 11:20 PM UTC

   We are continuing to work through the fix for this issue. We are working to resolve this as quickly as possible and will share another update shortly.

4. monitoring Jun 08, 2026, 11:54 PM UTC

   We have deployed a fix and campaign sending is recovering. We are processing the backlog of delayed campaigns and expect to deliver them shortly. We continue to monitor closely and appreciate your patience throughout this incident.

5. resolved Jun 09, 2026, 12:49 AM UTC

   Campaign sending has been restored and the backlog of delayed campaigns has completed sending. This incident has been resolved.

Read the full incident report →

Started Jun 06, 2026, 05:18 PM UTC· resolved Jun 06, 2026, 11:05 PM UTC

1. investigating Jun 06, 2026, 05:18 PM UTC

   All WhatsApp functionality is currently unavailable for customers due to an upstream provider outage (including sending, integration setup and template editing). The Engineering team is actively investigating and will share more information as soon as it becomes available.

2. resolved Jun 06, 2026, 11:05 PM UTC

   The issue affecting WhatsApp features within Klaviyo has been resolved as of 6:45 PM US/Eastern on June 6, 2026. Our Engineering team has monitored performance and see that WhatsApp services have been restored including message sending, integration setup and template editing. This incident has been resolved.

Read the full incident report →

Started Jun 03, 2026, 02:23 PM UTC· resolved Jun 03, 2026, 05:16 PM UTC

1. investigating Jun 03, 2026, 02:23 PM UTC

   Klaviyo is aware of an issue affecting the Shopify integration. Some customers attempting to set up a new Shopify integration, or performing actions that depend on the Shopify API, may be encountering errors. Customers with existing integrations may experience delays in Shopify data syncing. The issue is caused by a partial outage affecting an upstream service, and our team is actively monitoring the situation while automated retry processes work to recover affected requests. You can follow the external incident here: https://www.shopifystatus.com/incidents/gbqcx5fk01gz We will share more as soon as the situation is understood.

2. identified Jun 03, 2026, 02:46 PM UTC

   The issue has been identified and we are seeing early signs of recovery. We are continuing to monitor the situation closely and will share another update shortly.

3. monitoring Jun 03, 2026, 03:06 PM UTC

   We're seeing further recovery for Shopify integrations, and Shopify data syncing is returning to normal. Automated retry processes are working through the backlog of affected requests. No action is required for customers with existing integrations. Customers who saw errors while setting up a new Shopify integration can retry that setup. We continue to monitor closely and appreciate your patience throughout this incident.

4. resolved Jun 03, 2026, 05:16 PM UTC

   The issue affecting Shopify integrations has been resolved, and Shopify data syncing has returned to normal. Automated retry processes will continue to work through the backlog of affected requests. Some customers may see their integration in a failed state, but the retry processes will automatically fix this. Customers who saw errors while setting up a new Shopify integration can retry. This incident has been resolved.

Read the full incident report →

Started May 19, 2026, 08:36 PM UTC· resolved May 20, 2026, 12:30 AM UTC

1. investigating May 19, 2026, 08:36 PM UTC

   SMS event processing is delayed by approximately 2–3 hours. SMS sending is not impacted and recipients are receiving messages at the expected send times. This is impacting when SMS-related events appear in customer accounts, which may cause a delay in SMS event-triggered flows, real-time segments built on SMS event data, and reporting. Our team is actively investigating and we'll provide updates as soon as more information is available.

2. identified May 19, 2026, 10:21 PM UTC

   We have identified the cause of the issue and SMS event processing is recovering. Delays in processing SMS events are currently around 3 hours and continue to decrease. SMS campaign sending continues to be unaffected and recipients are continuing to receive messages at the expected send times. Customers may continue to see downstream delay in SMS event-triggered flow sending, real-time segments built on SMS event data, and reporting until processing has fully caught up. Customers may also encounter errors when creating and registering RCS agents, and when viewing videos within the platform. We'll provide updates as soon as more information is available.

3. resolved May 20, 2026, 12:30 AM UTC

   SMS events have been restored to real time processing as of 6:38 PM ET on May 19, 2026. Our Engineering team has monitored performance and see that systems have fully recovered. This incident has been resolved.

Read the full incident report →

Started May 19, 2026, 04:11 PM UTC· resolved May 19, 2026, 05:38 PM UTC

1. investigating May 19, 2026, 04:11 PM UTC

   Customers may be experiencing intermittent errors and slow page loads in the Klaviyo app. Our engineering team is actively investigating. We'll provide updates as soon as more information is available.

2. identified May 19, 2026, 04:46 PM UTC

   We have identified the cause of the intermittent errors and slow page loads some customers are experiencing in the Klaviyo app. Some customers may also be experiencing delays of up to 20 minutes for email and SMS sends, as well as delays in flows that send push notifications. Our engineering team is deploying a fix.

3. monitoring May 19, 2026, 05:17 PM UTC

   A fix has been deployed and system performance is improving. Intermittent errors, slow page loads, and delays for email and SMS sends are recovering. We continue to monitor closely.

4. resolved May 19, 2026, 05:38 PM UTC

   The intermittent errors, slow page loads, and delays for email and SMS sends have been resolved. A small number of push notifications from impacted flows are being replayed and will deliver shortly. This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 03:02 PM UTC· resolved May 09, 2026, 12:31 AM UTC

1. investigating May 08, 2026, 03:02 PM UTC

   We are currently investigating reports of errors loading campaign and flow pages within Klaviyo. Campaign and flow sending is not impacted. Our engineering team is actively working to identify and resolve the issue. We'll provide updates as soon as more information is available.

2. identified May 08, 2026, 05:10 PM UTC

   We have identified the root cause of the errors and our engineering team is actively working toward a resolution. We'll provide updates as soon as more information is available.

3. identified May 08, 2026, 06:37 PM UTC

   System performance is improving, and users can now access campaigns pages to complete scheduling. We determined these errors resulted from a combination of instability with an upstream infrastructure provider (AWS) and a significant increase in retry traffic. We continue to monitor closely and appreciate your patience throughout this incident.

4. identified May 08, 2026, 08:19 PM UTC

   Sending, scheduling, and other core functions are operating normally. Analytics for campaigns and flows are currently delayed by approximately 2 hours. These issues are tied to instability with an upstream infrastructure provider (AWS) and we are continuing to work through them. We'll provide updates as soon as we have more to share.

5. monitoring May 08, 2026, 11:13 PM UTC

   Analytics processing for campaigns and flows is recovering and the delay is decreasing. Sending, scheduling, and other core functions remain fully operational. We're monitoring closely and will confirm once analytics return to normal operation.

6. resolved May 09, 2026, 12:31 AM UTC

   Analytics processing for campaigns and flows is fully caught up and operating normally. We appreciate your patience throughout this incident. This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 01:32 AM UTC· resolved May 08, 2026, 07:05 PM UTC

1. investigating May 08, 2026, 01:32 AM UTC

   We are currently investigating an issue affecting analytics and reporting, flows, campaigns, and segmentation. This issue appears to be related to a disruption with an upstream service provider. Customers may experience errors or be unable to load flows and campaigns pages, see delays in real-time segmentation updates, and find analytics data temporarily unavailable. Our team is actively working to resolve this. We'll provide updates as soon as more information is available.

2. identified May 08, 2026, 02:22 AM UTC

   Our engineering team is continuing to monitor areas affected by the upstream service provider. At this stage, event processing has recovered and is working as expected. There remains processing delays for segmentation and analytics. There may be sending delays with Campaigns & Flows that rely include impacted segments and loading issues with reporting pages. We will provide updates as soon as more information is available.

3. identified May 08, 2026, 03:46 AM UTC

   A subset of customers are currently experiencing segmentation processing delays of approximately 1.5 hours and may find that analytics data is not fully up to date. Access to reporting pages has been restored and our engineering team is actively working to bring segmentation and analytics back to real time. We'll provide updates as soon as more information is available.

4. identified May 08, 2026, 07:08 AM UTC

   Segmentation has been restored to realtime processing. Our engineering team continues to restore the remaining affected analytics. We will continue to provide updates as real-time analytics functionality resumes.

5. monitoring May 08, 2026, 04:59 PM UTC

   Segmentation has been restored to real-time processing, and campaign and forms analytics have now recovered. This was a reporting UI display issue only, no data was lost. Our engineering team continues to monitor closely until our upstream service provider has confirmed full recovery.

6. resolved May 08, 2026, 07:05 PM UTC

   Segmentation continues to process in real-time and is fully recovered. We determined the delays resulted from instability with an upstream infrastructure provider (AWS). This incident is now resolved.

Read the full incident report →

Started May 05, 2026, 09:24 PM UTC· resolved May 07, 2026, 11:02 PM UTC

1. investigating May 05, 2026, 09:24 PM UTC

   Klaviyo is currently experiencing a service disruption affecting access to klaviyo.com, our APIs, and message sending. Customers may be unable to log in, send campaigns or flows, or have their events processed during this time. Our engineering team is actively investigating the root cause. We'll provide updates as soon as more information is available.

2. investigating May 05, 2026, 10:33 PM UTC

   Our engineering team is continuing to investigate the disruption affecting klaviyo.com, our APIs, and message sending. We will provide updates as more information is available.

3. investigating May 05, 2026, 11:40 PM UTC

   We are continuing to investigate the issue affecting access to klaviyo.com and all associated services. Our engineering team is actively working to restore affected services. We will provide updates as soon as more information is available.

4. identified May 06, 2026, 12:25 AM UTC

   Access to klaviyo.com has been restored, and dependent services are progressively coming back online. Our team continues to work toward full recovery, which we expect within the next hour. We'll provide another update in 30 minutes.

5. identified May 06, 2026, 12:57 AM UTC

   Recovery is continuing to progress, and additional services are coming back online. Our team remains actively engaged, and we'll provide another update shortly.

6. identified May 06, 2026, 01:38 AM UTC

   We are seeing recovery across APIs, event ingestion, and subscriptions. Our team continues to work toward restoring full functionality.

7. monitoring May 06, 2026, 02:53 AM UTC

   Our engineering team has restored the impacted services and confirmed that systems have resumed functioning as intended. All Campaign/Flow messages impacted which are able to be replayed are currently sending. We're currently monitoring performance and will continue to update as incident is resolved.

8. monitoring May 06, 2026, 05:59 AM UTC

   Access to klaviyo.com and core platform services has been restored. The majority of platform areas have returned to normal operation, with many affected services recovering automatically as infrastructure came back online. Our team is continuing to monitor platform stability and is actively working through remaining data repairs, including unsubscribe processing and analytics recovery. We will share further updates as this work progresses.

9. monitoring May 06, 2026, 03:59 PM UTC

   Klaviyo services have been restored. Some background data reconciliation and recovery work is still in progress. This is not affecting overall system availability or customer use of the platform. Our team is continuing to monitor closely as we complete final repair efforts.

10. monitoring May 06, 2026, 09:30 PM UTC

    Klaviyo services remain restored and operating as expected. Final background recovery and repair work is ongoing, but is not affecting customer use of the platform. Our team is continuing to monitor closely.

11. monitoring May 07, 2026, 03:48 PM UTC

    Klaviyo services remain restored and operating as expected. Most recovery and repair work is now complete. Remaining work is focused on restoring webhook connections for a subset of WooCommerce and Eventbrite integrations and a subset of campaign analytics repairs, neither of which is affecting customer use of the platform. Our team is continuing to monitor closely.

12. resolved May 07, 2026, 11:02 PM UTC

    All Klaviyo services have been fully restored and final recovery work is complete. We appreciate your patience throughout this incident. This incident has been resolved.

Read the full incident report →

Started Apr 26, 2026, 07:24 AM UTC· resolved Apr 26, 2026, 08:11 AM UTC

1. identified Apr 26, 2026, 07:24 AM UTC

   Starting 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.

2. monitoring Apr 26, 2026, 07:43 AM UTC

   We successfully implemented a fix as of 3:20 AM US/Eastern that restored all API activity. We are continuing to monitor the results.

3. resolved Apr 26, 2026, 08:11 AM UTC

   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.

Read the full incident report →