Störungsverlauf von Klaviyo

1. 27. August 2026 um 00:09 UTCinvestigating

   Um 15:25 Uhr US/Eastern am 26. August 2026 begannen wir, ein Problem zu erleben, bei dem einige Profile in den Flows nicht wie erwartet voranschreiten. Dies beeinflusst das Flow-Senden über alle Messaging-Kanäle, einschließlich E-Mail, Textnachrichten, Push und WhatsApp. Nachrichten, die von Kampagnen gesendet werden, und Datenflüsse, die keine Zeitverzögerungsaktionen enthalten, sind nicht betroffen. Wir arbeiten aktiv an einem Fix. Wir werden weiterhin Updates bereitstellen, sobald mehr Informationen verfügbar sind.

2. 27. August 2026 um 01:15 UTCidentified

   Unser Engineering-Team hat die Ursache dieses Problems identifiziert und arbeitet daran, einen Fix zu implementieren, um die verbleibenden Auswirkungen auf das Senden von Flüssen zu beheben, die von dem Zeitverzögerungsproblem betroffen sind. Sobald der Fix ausgerollt ist, werden wir alle betroffenen Flüsse überprüfen und reparieren. Wir arbeiten daran, dies so schnell wie möglich zu beheben und werden in Kürze ein weiteres Update veröffentlichen.

3. 27. August 2026 um 01:51 UTCmonitoring

   Ab 21:30 Uhr US/Eastern haben die Flows wie erwartet wieder über alle betroffenen Nachrichtenkanäle gesendet. Wir verarbeiten den Backlog der betroffenen Flow Messages. Ein Fix wurde bereitgestellt und die Systemleistung verbessert sich. Wir beobachten weiterhin genau und schätzen Ihre Geduld während dieses Vorfalls.

4. 27. August 2026 um 03:42 UTCresolved

   Ab 23:26 Uhr US/Eastern am 26. August 2026 wurde die Reparatur zur Verarbeitung der betroffenen Flow-Nachrichten aus dem Aufprallfenster abgeschlossen und das Flow-Senden wurde wie erwartet über alle Kanäle fortgesetzt. Wir entschuldigen uns für die Störung, die dadurch verursacht wurde. Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 19. August 2026 um 17:15 UTCidentified

   Wir erleben derzeit Verzögerungen von bis zu etwa 3 Stunden, wie schnell aktuelle Profil-Eigenschafts-Updates in Echtzeit-Segmenten reflektiert werden. Dies bedeutet, dass Änderungen an Profilen länger als üblich dauern können, um die Segmentmitgliedschaft zu aktualisieren, was sich auf das segmentbasierte Targeting auswirken kann. E-Mail- und SMS-Versand und andere Kernfunktionen funktionieren normal. Wir arbeiten aktiv daran, dies zu beheben und werden ein weiteres Update teilen, sobald wir weitere Informationen haben.

2. 19. August 2026 um 18:13 UTCmonitoring

   Ein Fix wurde bereitgestellt und die Systemleistung verbessert sich. Aktuelle Profil-Eigenschaftsupdates spiegeln sich nun schneller in Echtzeitsegmenten wider, und die Verzögerung hat sich auf etwa 2,5 Stunden verbessert. Änderungen an Profilen können immer noch etwas länger dauern als üblich, um die Segmentmitgliedschaft zu aktualisieren, da das System weiterhin aufholt. E-Mail- und SMS-Versand und andere Kernfunktionen bleiben unberührt. Wir beobachten weiterhin genau und schätzen Ihre Geduld während dieses Vorfalls.

3. 19. August 2026 um 18:38 UTCresolved

   Profileigenschaftsupdates werden jetzt in Echtzeitsegmenten mit normaler Geschwindigkeit reflektiert. Alle während des Incident-Fensters vorgenommenen Profileigenschaftenänderungen wurden wie erwartet in der Segmentmitgliedschaft berücksichtigt, und es sind keine Maßnahmen erforderlich. Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. August 2026 um 18:04 UTCmonitoring

   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. 12. August 2026 um 18:14 UTCresolved

   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.

1. 5. August 2026 um 16:47 UTCinvestigating

   Gegen 12:00 Uhr US/Eastern am 5. August 2026 begannen wir, ein Problem zu untersuchen, das einige E-Mail-Abonnements und Kampagnenfunktionen betraf. Kunden, die Double Opt-in verwenden, können feststellen, dass neue Abonnenten keine Bestätigungs-E-Mails wie erwartet erhalten. Einige Benutzer können Fehler beim Senden von Vorschau-E-Mails, beim Planen von Kampagnen oder beim Überprüfen der geschätzten Empfängerzahl feststellen. Unser Team arbeitet daran, dies zu lösen. Wir werden ein weiteres Update teilen, sobald wir mehr Informationen haben.

2. 5. August 2026 um 17:26 UTCidentified

   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. 5. August 2026 um 17:36 UTCmonitoring

   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. 5. August 2026 um 17:54 UTCresolved

   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.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juli 2026 um 14:35 UTCidentified

   Ab 8:09 Uhr US/Eastern am 23. Juli 2026 können Profilimporte, die über API, CSV-Upload oder SFTP gestartet wurden, möglicherweise nicht abgeschlossen werden und die importierten Profile können nicht erstellt werden. Neue Integrationen, die während dieses Zeitraums verbunden sind, können sich auch beim Starten ihrer anfänglichen Synchronisierung verzögern. Wir haben die Ursache identifiziert und setzen einen Fix ein. Wir arbeiten daran, dies so schnell wie möglich zu beheben und werden in Kürze ein weiteres Update veröffentlichen.

2. 23. Juli 2026 um 15:16 UTCmonitoring

   Profilimporte haben sich erholt, und Importe über API, CSV-Upload oder SFTP werden wieder normal verarbeitet. Integrationen, die während des Impact-Fensters verbunden sind, nehmen auch ihre anfänglichen Synchronisierungen wieder auf. Unser Team arbeitet daran, API-Importe, die während des Vorfalls fehlgeschlagen sind, neu zu verarbeiten. Wir beobachten weiterhin genau und schätzen Ihre Geduld während dieses Vorfalls.

3. 23. Juli 2026 um 16:01 UTCresolved

   Das System bleibt stabil und Importe über API, CSV-Upload oder SFTP werden normal verarbeitet. Importe, die während des Vorfalls fehlschlugen, wurden nicht automatisch aufgearbeitet. Wenn ein Import, den Sie zwischen 8:00 Uhr und 11:00 Uhr am 23. Juli 2026 begonnen haben, nicht abgeschlossen wurde, führen Sie ihn bitte erneut aus, um sicherzustellen, dass diese Profile importiert werden. Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 20:36 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das sich auf SMS-Abonnements, Verzögerungen beim SMS-Versand und Fehler beim Erstellen oder Planen von SMS- und WhatsApp-Kampagnen auswirkt. Wir arbeiten daran, den normalen Service so schnell wie möglich wiederherzustellen. Wir werden ein weiteres Update teilen, sobald wir mehr Informationen haben.

2. 21. Juli 2026 um 20:47 UTCidentified

   Wir haben die Ursache des Problems identifiziert und ein Fix wurde implementiert. Wir beginnen, Verbesserungen in der Systemleistung zu sehen.

3. 21. Juli 2026 um 20:57 UTCmonitoring

   Die Systemleistung für SMS-Anmeldeformulare, das Senden sowie die Erstellung und Planung von Kampagnen bleibt stabil. Wir beobachten weiterhin genau und schätzen Ihre Geduld während dieses Vorfalls.

4. 21. Juli 2026 um 21:09 UTCresolved

   SMS-Abonnements, SMS-Versand sowie die Erstellung und Planung von SMS- und WhatsApp-Kampagnen funktionieren wie erwartet. Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. Juli 2026 um 01:52 UTCinvestigating

   Um 16:00 Uhr US/Eastern am 8. Juli 2026 haben wir Verzögerungen bei der Synchronisierung von Produktupdates von Integrationen mit Webhooks festgestellt. Dies führt dazu, dass Katalogdaten, einschließlich Templates und Customer Hub, nicht in Echtzeit aktualisiert werden. Der Kunde kann sehen, dass Produktdaten bis zu 4 Stunden veraltet sind. Der Versand ist nicht betroffen, aber die Produktdaten in Vorlagen spiegeln möglicherweise keine Echtzeitinformationen wider. Wir arbeiten daran, dies so schnell wie möglich zu beheben und werden in Kürze ein weiteres Update veröffentlichen.

2. 9. Juli 2026 um 03:14 UTCidentified

   Ab 21.45 Uhr US/Eastern am 8. Juli 2026 haben wir die Verarbeitung neuer Webhooks für Produktkataloge angehalten, während wir weiter an einem Fix arbeiten. Katalogdaten, einschließlich Templates und Customer Hub, bleiben bis zur Synchronisierung veraltet. Unser Engineering-Team arbeitet aktiv daran, Echtzeit-Katalog-Updates wiederherzustellen. Wir werden Updates bereitstellen, sobald weitere Informationen verfügbar sind.

3. 9. Juli 2026 um 04:34 UTCmonitoring

   Ab 23:13 Uhr US/Eastern am 8. Juli 2026 haben wir die Verarbeitung von Webhooks wieder aufgenommen. Dies bedeutet, dass alle neuen Webhooks aus Integrationen, die Webhooks zum Aktualisieren von Produkten verwenden, jetzt in Echtzeit synchronisiert werden. Unser Engineering-Team arbeitet daran, eine Reparatur durchzuführen, um alle Produktupdate-Webhooks während des Aufprallfensters (21:45 Uhr und 23:13 Uhr US / Eastern 8. Juli 2026) nachzuholen. Wir werden dies bestätigen, sobald die Reparatur abgeschlossen und der Vorfall vollständig behoben ist.

4. 9. Juli 2026 um 16:13 UTCmonitoring

   Produktupdates aus E-Commerce-Integrationen synchronisieren sich weiterhin normal in Echtzeit. Eine Hintergrundreparatur zur vollständigen Aktualisierung der Aufzeichnungen aus dem früheren Aufprallfenster (21:45 Uhr bis 23:13 Uhr US/Eastern am 8. Juli 2026) ist noch im Gange. Wir werden es bestätigen, sobald diese Reparatur abgeschlossen ist.

5. 10. Juli 2026 um 21:01 UTCresolved

   Die Reparatur zum Aufholen von Produkt-Update-Webhooks aus dem Fenster der Auswirkungen wurde abgeschlossen und die betroffenen Produktdaten sind auf dem neuesten Stand. Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 7. Juli 2026 um 15:33 UTCinvestigating

   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. 7. Juli 2026 um 15:56 UTCidentified

   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. 7. Juli 2026 um 16:32 UTCidentified

   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. 7. Juli 2026 um 16:47 UTCmonitoring

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

5. 7. Juli 2026 um 16:56 UTCresolved

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

1. 2. Juli 2026 um 12:17 UTCinvestigating

   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.

2. 2. Juli 2026 um 14:17 UTCresolved

   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.

1. 12. Juni 2026 um 14:49 UTCinvestigating

   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. 12. Juni 2026 um 15:48 UTCidentified

   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. 12. Juni 2026 um 17:19 UTCmonitoring

   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. 12. Juni 2026 um 17:30 UTCresolved

   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.

1. 10. Juni 2026 um 18:47 UTCinvestigating

   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. 10. Juni 2026 um 19:02 UTCidentified

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

3. 10. Juni 2026 um 19:23 UTCmonitoring

   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. 10. Juni 2026 um 19:46 UTCresolved

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

1. 8. Juni 2026 um 21:10 UTCinvestigating

   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. 8. Juni 2026 um 21:19 UTCidentified

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

3. 8. Juni 2026 um 23:20 UTCidentified

   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. 8. Juni 2026 um 23:54 UTCmonitoring

   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. 9. Juni 2026 um 00:49 UTCresolved

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

1. 6. Juni 2026 um 17:18 UTCinvestigating

   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. 6. Juni 2026 um 23:05 UTCresolved

   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.

1. 3. Juni 2026 um 14:23 UTCinvestigating

   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. 3. Juni 2026 um 14:46 UTCidentified

   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. 3. Juni 2026 um 15:06 UTCmonitoring

   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. 3. Juni 2026 um 17:16 UTCresolved

   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.

1. 19. Mai 2026 um 20:36 UTCinvestigating

   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. 19. Mai 2026 um 22:21 UTCidentified

   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. 20. Mai 2026 um 00:30 UTCresolved

   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.

1. 19. Mai 2026 um 16:11 UTCinvestigating

   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. 19. Mai 2026 um 16:46 UTCidentified

   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. 19. Mai 2026 um 17:17 UTCmonitoring

   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. 19. Mai 2026 um 17:38 UTCresolved

   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.

1. 8. Mai 2026 um 15:02 UTCinvestigating

   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. 8. Mai 2026 um 17:10 UTCidentified

   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. 8. Mai 2026 um 18:37 UTCidentified

   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. 8. Mai 2026 um 20:19 UTCidentified

   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. 8. Mai 2026 um 23:13 UTCmonitoring

   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. 9. Mai 2026 um 00:31 UTCresolved

   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.

1. 8. Mai 2026 um 01:32 UTCinvestigating

   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. 8. Mai 2026 um 02:22 UTCidentified

   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 to segmentation delays. Segment-triggered flows may also fail to trigger correctly as profiles may not be added to or removed from segments as expected. We'll provide updates as soon as more information is available.

3. 8. Mai 2026 um 03:46 UTCidentified

   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. 8. Mai 2026 um 07:08 UTCidentified

   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. 8. Mai 2026 um 16:59 UTCmonitoring

   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. 8. Mai 2026 um 19:05 UTCresolved

   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.

1. 5. Mai 2026 um 21:24 UTCinvestigating

   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. 5. Mai 2026 um 22:33 UTCinvestigating

   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. 5. Mai 2026 um 23:40 UTCinvestigating

   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. 6. Mai 2026 um 00:25 UTCidentified

   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. 6. Mai 2026 um 00:57 UTCidentified

   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. 6. Mai 2026 um 01:38 UTCidentified

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

7. 6. Mai 2026 um 02:53 UTCmonitoring

   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. 6. Mai 2026 um 05:59 UTCmonitoring

   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. 6. Mai 2026 um 15:59 UTCmonitoring

   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. 6. Mai 2026 um 21:30 UTCmonitoring

    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. 7. Mai 2026 um 15:48 UTCmonitoring

    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. 7. Mai 2026 um 23:02 UTCresolved

    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.

1. 26. April 2026 um 07:24 UTCidentified

   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. 26. April 2026 um 07:43 UTCmonitoring

   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. 26. April 2026 um 08:11 UTCresolved

   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.