Klaviyo

Affected: Email Sending, Text Message Sending, WhatsApp Sending, Mobile Push Sending, Flow Editor, Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-17 17:01 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 2026-10-17 17:31 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 2026-10-17 17:35 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 2026-10-17 18:06 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 2026-10-17 18:31 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 2026-10-17 19:04 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 2026-10-17 19:42 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 2026-10-17 20:22 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...

9. monitoring 2026-10-17 20:59 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...

10. monitoring 2026-10-17 21:34 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 2026-10-17 21:51 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Segments, Profiles, Analytics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-09 00:10 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...

2. identified 2026-10-09 01:21 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,...

3. monitoring 2026-10-09 02:09 UTC

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

4. resolved 2026-10-09 02:16 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Klaviyo App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 15:00 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 2026-10-08 15:29 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 2026-10-08 15:49 UTC

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

4. monitoring 2026-10-08 16:06 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 2026-10-08 16:13 UTC

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

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending, Text Message Sending, WhatsApp Sending, Mobile Push Sending, Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-21 15:56 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 2026-09-21 15:56 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-21 16:26 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 2026-09-21 16:42 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 2026-09-21 17:43 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 2026-09-21 17:58 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending, Text Message Sending, WhatsApp Sending, Mobile Push Sending, Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 17:10 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. identified 2026-09-17 17:31 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.

3. identified 2026-09-17 18:30 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.

4. monitoring 2026-09-17 19:21 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.

5. resolved 2026-09-17 19:46 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending, Text Message Sending, WhatsApp Sending, Mobile Push Sending, Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-14 21:30 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 2026-09-14 22:22 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 2026-09-14 23:18 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...

4. identified 2026-09-15 00:25 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 2026-09-15 01:07 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...

6. resolved 2026-09-15 01:51 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending, Text Message Sending, WhatsApp Sending, Mobile Push Sending, Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 00:09 UTC

   At 3:25 PM US/Eastern on August 26, 2026, we began experiencing an issue where some profiles are not progressing past time delay actions in flows as expected. This is affecting flow sending across all messaging channels, including email, text messaging, push, and WhatsApp....

2. identified 2026-08-27 01:15 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...

3. monitoring 2026-08-27 01:51 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...

4. resolved 2026-08-27 03:42 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Segments, Profiles

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-19 17:15 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...

2. monitoring 2026-08-19 18:13 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...

3. resolved 2026-08-19 18:38 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending, Text Message Sending, WhatsApp Sending, Mobile Push Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-12 18:04 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...

2. resolved 2026-08-12 18:14 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending, Profiles, Campaign Editor

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 16:47 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...

2. identified 2026-08-05 17:26 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...

3. monitoring 2026-08-05 17:36 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...

4. resolved 2026-08-05 17:54 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...

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Server-side, Lists, WooCommerce, Profiles, Magento, Other

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-23 14:35 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...

2. monitoring 2026-07-23 15:16 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...

3. resolved 2026-07-23 16:01 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,...

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Text Message Sending, WhatsApp Sending

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-21 20:36 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...

2. identified 2026-07-21 20:47 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 2026-07-21 20:57 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 2026-07-21 21:09 UTC

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

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Shopify, WooCommerce, BigCommerce, Customer Hub, Magento, Other

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-09 01:52 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...

2. identified 2026-07-09 03:14 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...

3. monitoring 2026-07-09 04:34 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...

4. monitoring 2026-07-09 16:13 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...

5. resolved 2026-07-10 21:01 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Klaviyo App, Email Sending, Email Sending

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-07 15:33 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 2026-07-07 15:56 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...

3. identified 2026-07-07 16:32 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 2026-07-07 16:47 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 2026-07-07 16:56 UTC

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

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Deliverability

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-02 12:17 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...

2. resolved 2026-07-02 14:17 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Customer Agent, Helpdesk, WhatsApp Sending, Other

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-12 14:49 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...

2. identified 2026-06-12 15:48 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...

3. monitoring 2026-06-12 17:19 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...

4. resolved 2026-06-12 17:30 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...

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 18:47 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 2026-06-10 19:02 UTC

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

3. monitoring 2026-06-10 19:23 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 2026-06-10 19:46 UTC

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

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-08 21:10 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 2026-06-08 21:19 UTC

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

3. identified 2026-06-08 23:20 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 2026-06-08 23:54 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 2026-06-09 00:49 UTC

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

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: WhatsApp Sending

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-06 17:18 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 2026-06-06 23:05 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....

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Shopify

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-03 14:23 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...

2. identified 2026-06-03 14:46 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 2026-06-03 15:06 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...

4. resolved 2026-06-03 17:16 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...

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Segments, Text Message Sending, Processing, Analytics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-19 20:36 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,...

2. identified 2026-05-19 22:21 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...

3. resolved 2026-05-20 00:30 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Klaviyo App, Email Sending, Email Sending, Text Message Sending, Mobile Push Sending

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-19 16:11 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 2026-05-19 16:46 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....

3. monitoring 2026-05-19 17:17 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 2026-05-19 17:38 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Klaviyo App, Analytics

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 15:02 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 2026-05-08 17:10 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 2026-05-08 18:37 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...

4. identified 2026-05-08 20:19 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....

5. monitoring 2026-05-08 23:13 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 2026-05-09 00:31 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Server-side, Segments, Processing, Analytics

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 01:32 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...

2. identified 2026-05-08 02:22 UTC

   Our engineering team continues to investigate areas affected by an upstream service provider. Customers may experience processing delays for segmentation and analytics, and loading issues with reporting pages. For campaigns, sends may not reach the most up-to-date audience due...

3. identified 2026-05-08 03:46 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...

4. identified 2026-05-08 07:08 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 2026-05-08 16:59 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...

6. resolved 2026-05-08 19:05 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Klaviyo App, Email Sending, Email Sending, Sign-up Forms, Email Deliverability, Lists, Segments, Customer Agent, Consent Pages, Profiles, Helpdesk, Mobile Push Sending, Customer Hub, Reviews, Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-05 21:24 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...

2. investigating 2026-05-05 22:33 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 2026-05-05 23:40 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 2026-05-06 00:25 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 2026-05-06 00:57 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 2026-05-06 01:38 UTC

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

7. monitoring 2026-05-06 02:53 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...

8. monitoring 2026-05-06 05:59 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...

9. monitoring 2026-05-06 15:59 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 2026-05-06 21:30 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 2026-05-07 15:48 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...

12. resolved 2026-05-07 23:02 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Server-side

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-26 07:24 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...

2. monitoring 2026-04-26 07:43 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 2026-04-26 08:11 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.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Segments

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-03-27 04:46 UTC

   Starting around 8:15 PM US Eastern 26th March, we began seeing delays in real-time segment processing for a subset of customers. Segments may be out of date by up to 2.5 hours. Engineering have identified a solution and are working to implement the fix shortly. We will continue...

2. resolved 2026-03-27 05:15 UTC

   Real-time segmentation is processing in real-time, and this incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending, Text Message Sending, Mobile Push Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-12 11:12 UTC

   Beginning around 5am US Eastern time, we began observing delays in campaign scheduling and sending. New campaigns, and scheduled RAST (calculate Recipient at Send Times) campaigns, are unable to send. However non-RAST campaigns that were scheduled prior to 5am US Eastern Time...

2. identified 2026-01-12 11:51 UTC

   As of 6:45am US Eastern, the issue has been identified and a fix implemented. Any new scheduled or sent campaigns should process, with slight delays. We are actively replaying any campaigns that were delayed.

3. monitoring 2026-01-12 12:05 UTC

   A fix has been implemented and we are monitoring results. Campaign sending and scheduling is back to normal, and all delayed campaigns have been replayed.

4. resolved 2026-01-12 12:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-22 22:37 UTC

   We are investigating reports of users unable to switch accounts once logged into Klaviyo

2. investigating 2025-12-22 23:37 UTC

   We identified broader service disruption across the Klaviyo app between 5:55 pm and approximately 6:10 pm ET. While initial reports were limited to account switching, we have since confirmed additional impact to app availability and functionality. The underlying issue has been...

3. monitoring 2025-12-22 23:58 UTC

   We have confirmed the app is now widely available and are moving the incident to monitoring. 10% of accounts experienced messaging delays during this window. We are working to replay any impacted messages, including unsubscribes, inbound SMS, and flows. Any campaigns that failed...

4. resolved 2025-12-23 00:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Klaviyo App, Email Sending, Server-side, Email Sending, Segments, Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-18 04:10 UTC

   Starting around 9:52pm US Eastern, a database upgrade failure caused data processing delays in-app. As a result, we are experiencing delays in event processing, flows, unsubscribes, segmentation, sending for certain campaigns, and v3 APIs. No data loss is expected. We are...

2. identified 2025-12-18 05:12 UTC

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

3. monitoring 2025-12-18 06:06 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-12-18 06:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-12-17 01:11 UTC

   Beginning around 6:42 PM US/Eastern on 12/16/2025, customers may have noticed an issue with cloning templates from the Template Library. Our engineering team has identified the cause of this issue and is implementing a fix to restore functionality. We'll provide updates as soon...

2. resolved 2025-12-17 01:49 UTC

   As of 8:23 PM US/Eastern on 12/16/2025, this incident has been resolved and template cloning functionality has been fully restored.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. resolved 2025-12-05 09:00 UTC

   Between 3:48am (US Eastern) and 4:10am (US Eastern) Cloudflare experienced an outage which affected Klaviyo. During this time, users were unable to access Klaviyo.com and all Klaviyo APIs. During this window, a number of services were affected. Subscription events and click...

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Customer Agent

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-03 19:57 UTC

   We are currently investigating an issue impacting Customer Agent follow-up prompts beginning around 11:20 AM US/Eastern. Follow-up prompts are not appearing after replies from the AI Agent. This prevents end users from continuing the conversation or escalating to a human agent....

2. identified 2025-12-03 20:08 UTC

   As of 3:00 PM US/Eastern, we confirmed this issue is only impacted Web Chat. Customer Agent via SMS chat is not impacted. We have identified a recent change as the root cause and will be reverting this shortly. We continue to monitor closely and appreciate your patience...

3. monitoring 2025-12-03 20:21 UTC

   We successfully reverted the change and have confirmed that Customer Agent Web Chat follow-up prompts are sending as expected. We will continue to monitor to ensure there is no further impact.

4. resolved 2025-12-03 20:36 UTC

   Monitoring is complete, and this incident has been resolved. We appreciate your patience throughout this incident.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Customer Agent, Helpdesk, Customer Hub

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-28 20:27 UTC

   Starting at 3:00pm (US Eastern), Klaviyo Helpdesk, Customer Hub, and the onsite web chat functionality of Customer Agent are unavailable. Our team is investigating the issue and will update with progress as soon as possible.

2. identified 2025-11-28 20:46 UTC

   Starting at 3:40pm (US Eastern), we have restored access to these services (Customer Hub, Helpdesk, and Customer Agent). We continue to closely monitor these systems.

3. monitoring 2025-11-28 21:11 UTC

   Access to these services (Customer Hub, Helpdesk, and Customer Agent) remains stable. We are continuing to closely monitor these systems.

4. resolved 2025-11-28 22:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Server-side, Sign-up Forms, Lists, Consent Pages

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 13:58 UTC

   Cloudflare declared an incident around 6:30 am US Eastern causing all onsite activities, such as unsubscribe and subscribe preference pages and onsite form submissions to error out. Forms appear, but no requests or related events or subscriptions are processing. API calls are...

2. monitoring 2025-11-18 14:34 UTC

   Fixes have been implemented for some services and we are monitoring the issues.

3. resolved 2025-11-18 19:06 UTC

   This incident has been resolved, as of 2 pm US eastern. All affected components are operational.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Other

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-02 07:03 UTC

   As of 1:00 AM ET (approximately one hour ago), our Facebook integration sync encountered a failure, resulting in a temporary delay in data sync. We have confirmed that no data has been lost, and the system failure is strictly impacting sync times. The root cause has been...

2. monitoring 2025-11-02 13:13 UTC

   A fix has been identified and we are monitoring the results.

3. resolved 2025-11-02 17:41 UTC

   The incident is now resolved. All delayed data for Facebook Integrations, which occurred between 1:00 AM and 2:00 AM, has been fully restored.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Segments, Processing, Analytics

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-29 18:16 UTC

   Starting at 1:00 PM US/Eastern, we began experiencing delays of up to 40 minutes for SMS events processing. SMS Sending is not impacted. We have identified the issue and are in the process of reverting a change to restore normal processing. We'll provide updates as soon as more...

2. identified 2025-10-29 18:27 UTC

   We want to acknowledge that downstream services (Segments and Flows) relying on the SMS events will also be impacted, until the event processing has caught up, which we expect to happen shortly. We'll continue to provide updates as they are available.

3. identified 2025-10-29 19:12 UTC

   We are still working to restore normal processing of SMS events. A subset of customers may see delays of up to 90 minutes at this time. SMS Sending remains unaffected.

4. monitoring 2025-10-29 19:27 UTC

   We have mitigated the delays and we expect SMS event processing to be fully caught up within the next 20 minutes. There was no data loss as a result of this incident.

5. resolved 2025-10-29 19:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Consent Pages

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-10-24 00:23 UTC

   Between 3:46pm EST and 7:29pm EST on 23rd Oct 2025, customers may have noticed an issue causing web view & unsubscribe tags to redirect to incorrect Template previews or broken pages. This may have affected some customers' ability to view or test templates as expected. The...

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Shopify, Klaviyo App, Email Sending, Server-side, Email Sending, Sign-up Forms, Email Deliverability, Lists, Segments, Text Message Deliverability, Text Message Sending, WooCommerce, Consent Pages, Profiles, BigCommerce, Mobile Push Sending, Magento, Reviews, Klaviyo Marketing, Processing, Other, Analytics

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 08:58 UTC

   Starting around 2:50am EST, due to outages with an upstream provider, several services in Klaviyo including log-in and sending are inaccessible. We'll provide updates as soon as more information is available.

2. monitoring 2025-10-20 09:58 UTC

   As of 5:30am EST, the ability to log in and access the Klaviyo app has been restored. Restoration of all functionality and services is in progress. We are actively investigating the state of sending (campaigns, flows). We will continue to monitor services as functionality is...

3. monitoring 2025-10-20 10:41 UTC

   As of 6:15am EST, we are continuing to stabilize our systems and process any actions that were affected by the provider outage, which lasted from approximately 2:50 to 5:30am EST. We are attempting to send any campaigns and flows messages that couldn't be sent during that time....

4. monitoring 2025-10-20 12:39 UTC

   As of 8:30am EST, we have successfully sent the delayed campaign and flow messages. Over the next several hours, we will process delayed conversion attribution analytics and delayed profile unsubscribes. We continue to closely monitor our systems.

5. monitoring 2025-10-20 15:09 UTC

   We continue to process delayed conversion attribution analytics and delayed profile unsubscribes. We are currently experiencing delays in segmentation processing for a subset of users by up to 60 minutes. We’re working to mitigate these processing delays as quickly as possible.

6. monitoring 2025-10-20 15:26 UTC

   Segmentation processing has been restored. We continue to work through processing for the delayed analytics and unsubscribes.

7. investigating 2025-10-20 16:46 UTC

   We are currently investigating an issue impacting flow sending beginning around 12:00 PM US/Eastern. We’ll provide updates as soon as more information is available.

8. investigating 2025-10-20 17:37 UTC

   We are currently experiencing delays in segmentation processing for a subset of users by up to 2.5 hours. We’re working to mitigate these processing delays as quickly as possible.

9. identified 2025-10-20 18:55 UTC

   A mitigation has been deployed for the issue impacting flow sending. Any delayed messages are now being replayed and flow performance is improving. We will confirm once this has been fully restored. The team continues to work through the segmentation processing delays. We...

10. monitoring 2025-10-20 20:21 UTC

    Segmentation processing has been restored to real-time. Segments relying on custom object properties remain delayed and we're continuing to restore normal processing for these. We expect flow sending to be fully caught up within the next hour. We continue to process delayed...

11. monitoring 2025-10-20 20:45 UTC

    Flow sending is fully caught up and restored to real-time. We continue to process delayed conversion attribution analytics and delayed profile unsubscribes.

12. monitoring 2025-10-21 00:31 UTC

    As of 7:32pm EST, we have successfully processed the delayed unsubscribe events and conversion attribution analytics has been restored. We continue to monitor service functionality as repairs have been completed.

13. resolved 2025-10-21 17:06 UTC

    All services have been restored and are operating normally. Monitoring is complete, and this incident has been resolved. We appreciate your patience throughout this incident.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Klaviyo App, Server-side, Sign-up Forms, Lists

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-10-02 17:43 UTC

   From 1:17 PM to 1:32 PM US/Eastern on 10/2/25, we experienced an issue that resulted in errors accessing the Klaviyo app, disruption in event ingestion, and issues submitting signup forms. A fix has been deployed and system performance is improving. We continue to monitor...

2. resolved 2025-10-02 17:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Consent Pages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-10-01 02:16 UTC

   We are currently monitoring an issue that was impacting subscribe and unsubscribe pages for all profiles. This may have prevented profiles from opting in or out of marketing communications. We'll provide updates as soon as more information is available.

2. resolved 2025-10-01 02:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Segments, Profiles, Analytics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-19 14:38 UTC

   At around 7 AM Eastern time, we began experiencing delays in real-time event processing. Events may be out of date by up to 3 hours. Flows, Segments, Profiles, Reporting, as well as segment-targeted forms, may be impacted. We are actively working to restore real-time processing...

2. identified 2025-09-19 17:07 UTC

   A fix has been implemented and we are monitoring the results. We expect real time event processing to be fully restored within 1 hour.

3. monitoring 2025-09-19 18:42 UTC

   Event processing has been restored to real-time. There was no data loss as a result of this incident. We’re continuing to monitor and will post another update once we have fully cleared any backlog of processing data.

4. resolved 2025-09-19 20:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-19 13:38 UTC

   We are currently investigating an issue where a subset of scheduled and draft campaigns may not be appearing in the campaign list view as expected. We are actively investigating. We’ll provide updates as soon as more information is available.

2. identified 2025-09-19 21:50 UTC

   We're continuing to work through repairs for this subset of campaigns. We'll provide updates as soon as more information is available. We appreciate your patience throughout this incident.

3. monitoring 2025-09-22 19:43 UTC

   We have concluded our repairs and these campaigns should now show in the campaign list view as expected. We continue to monitor closely and appreciate your patience throughout this incident.

4. resolved 2025-09-29 13:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-16 21:05 UTC

   Starting 3:50pm US/Eastern on 9/16/25, we began observing delays in event-triggered flows. Users may see delays of up to 60 minutes. We're currently working on a fix. We’ll provide updates as soon as more information is available.

2. monitoring 2025-09-16 21:17 UTC

   A fix has been deployed and system performance is improving. We continue to monitor closely and appreciate your patience throughout this incident.

3. resolved 2025-09-16 21:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-03 21:32 UTC

   We are currently investigating an issue where omnichannel campaigns were resent unexpectedly. We'll provide updates as soon as more information is available.

2. monitoring 2025-09-03 22:41 UTC

   We have identified the root cause and have mitigated any further incorrect resends of omnichannel campaigns. We continue to monitor closely and appreciate your patience throughout this incident.

3. resolved 2025-09-03 22:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Segments

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-03 09:53 UTC

   We are currently experiencing delays in real-time segment processing. Segments may be out of date by up to 3 hours. Flows triggered by segments, as well as segment-targeted forms, may be impacted. We are actively working to restore real-time processing and will continue to...

2. identified 2025-09-03 12:46 UTC

   We have identified a root cause and are implementing a fix. We do not currently have an estimate for when processing will be back to real-time. We will post another update once a timeline is available.

3. resolved 2025-09-03 13:08 UTC

   Real-time segmentation is processing in real-time, and the incident has been resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Klaviyo App, Server-side

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-08-27 15:26 UTC

   Between 10:50am - 11:03am US/Eastern on 8/27/25, we experienced an issue that resulted in errors accessing the Klaviyo app, disruption in event ingestion, and issues submitting signup forms. We have resolved the issue.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-12 16:39 UTC

   We are currently investigating delays in the triggering of event-based flows, which began around 08/12/2025 at 11:45 US/Eastern. Our team is actively working to resolve the issue. Further updates will be provided as soon as new information is available.

2. monitoring 2025-08-12 17:05 UTC

   Triggering of event-based flows is now back to real-time. We're continuing to monitor and will provide an additional confirmation of full recovery.

3. resolved 2025-08-12 17:14 UTC

   This is now resolved, triggering is back to real-time.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Segments, Processing, Analytics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-08 19:20 UTC

   We are currently experiencing delays in event processing. Customers may see delays in event data syncing, event-triggered flows sending, and real-time segmentation. We are in the process of restoring normal operations and will continue to provide updates here.

2. monitoring 2025-07-08 19:44 UTC

   We have mitigated the delays and event-processing has been restored to real-time. There was no data loss as a result of this incident. We’re continuing to monitor and will post another update once we have fully cleared any backlog of processing data.

3. resolved 2025-07-08 19:50 UTC

   Event processing has been fully restored. This incident is now resolved.

Excerpts are shortened. Read the full incident on Klaviyo's status page.

Affected: Email Sending, Text Message Sending

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-07-02 19:41 UTC

   From 1:39-2:47PM US/Eastern on 7/2/25, Klaviyo users may have had duplicate flow messages sent to their profiles. Customers received the original message as expected, but may have received duplicate versions in the minutes to follow. Duplicate sending is no longer occurring. Our...

2. identified 2025-07-02 22:58 UTC

   We're continuing to work through repairs to billing as a result of the duplicate sends and will provide credits to the impacted accounts. We'll provide another update once we have more information to share.

3. resolved 2025-07-03 18:29 UTC

   The team continues to work through the appropriate adjustments to billing as a result of these duplicate sends. We expect to follow up with impacted customers early next week with more information once this work has been completed.

Excerpts are shortened. Read the full incident on Klaviyo's status page.