Historia awarii Klaviyo

1. 27 sierpnia 2026 00:09 UTCinvestigating

   26 sierpnia 2026 r., o godz. 15.25, zaczęliśmy doświadczać problemu, w którym niektóre profile nie postępują zgodnie z oczekiwaniami w czasie przeszłym. To wpływa na przepływ wysyłania przez wszystkie kanały wiadomości, w tym e-mail, wiadomości tekstowych, push, i WhatsApp. Wiadomość wysyłana z kampanii i przepływy, które nie obejmują działań z opóźnieniem czasowym, nie mają wpływu. Aktywnie pracujemy nad naprawą. Będziemy nadal dostarczać aktualizacje w miarę dostępności większej ilości informacji.

2. 27 sierpnia 2026 01:15 UTCidentified

   Nasz zespół inżynieryjny zidentyfikował przyczynę tego problemu i pracuje nad wdrożeniem rozwiązania w celu rozwiązania pozostałego wpływu na wysyłanie przepływów dotkniętych problemem opóźnienia czasowego. Gdy naprawimy problem, będziemy przeglądać i naprawiać wszelkie wpływające przepływy. Pracujemy nad jak najszybszym rozwiązaniem tego problemu i wkrótce podzielimy się kolejną aktualizacją.

3. 27 sierpnia 2026 01:51 UTCmonitoring

   Począwszy od 9: 30 w Stanach Zjednoczonych / Wschodnich, przepływy wznowiły wysyłanie zgodnie z oczekiwaniami przez wszystkie zainteresowane kanały wiadomości. Przetwarzamy zaległości wpływających komunikatów przepływu. Zastosowano rozwiązanie i wydajność systemu się poprawia. Kontynuujemy ścisłą obserwację i doceniamy twoją cierpliwość podczas tego incydentu.

4. 27 sierpnia 2026 03:42 UTCresolved

   Począwszy od 23: 26 PM US / Eastern 26 sierpnia 2026 roku, zakończono naprawę komunikatów dotyczących przepływu z okna uderzenia, a przesyłka została wznowiona zgodnie z oczekiwaniami we wszystkich kanałach. Przepraszamy za to zakłócenie. Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 19 sierpnia 2026 17:15 UTCidentified

   Obecnie mamy do czynienia z opóźnieniami do około 3 godzin w tym, jak szybko najnowsze aktualizacje właściwości profilu są odzwierciedlone w segmentach czasu rzeczywistego. Oznacza to, że zmiany w profilach mogą trwać dłużej niż zwykle, aby zaktualizować członkostwo w segmencie, co może mieć wpływ na ukierunkowanie segmentów. Wysyłanie wiadomości e-mail i SMS oraz inne funkcje podstawowe działają normalnie. Aktywnie pracujemy nad rozwiązaniem tego problemu i udostępnimy kolejną aktualizację, gdy tylko będziemy mieli więcej informacji.

2. 19 sierpnia 2026 18:13 UTCmonitoring

   Zastosowano rozwiązanie i wydajność systemu się poprawia. Ostatnie aktualizacje właściwości profilu są teraz odzwierciedlone w segmentach czasu rzeczywistego szybciej, a opóźnienie poprawiło się do około 2,5 godziny. Zmiany w profilach mogą trwać nieco dłużej niż zwykle, aby zaktualizować członkostwo w segmencie w miarę dalszego nadrabiania zaległości. Wysyłanie wiadomości e-mail i SMS oraz inne funkcje podstawowe pozostają nienaruszone. Kontynuujemy ścisłą obserwację i doceniamy twoją cierpliwość podczas tego incydentu.

3. 19 sierpnia 2026 18:38 UTCresolved

   Aktualizacje właściwości profilu znajdują odzwierciedlenie w segmentach czasu rzeczywistego przy normalnej prędkości. Wszelkie zmiany właściwości profilu dokonane podczas okna incydentu zostały odzwierciedlone w składzie segmentu zgodnie z oczekiwaniami, i nie jest wymagane działanie z Twojej strony. Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 12 sierpnia 2026 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 sierpnia 2026 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 sierpnia 2026 16:47 UTCinvestigating

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

2. 5 sierpnia 2026 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 sierpnia 2026 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 sierpnia 2026 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.

1. 23 lipca 2026 14:35 UTCidentified

   Począwszy od około 8: 09 AM US / Eastern 23 lipca 2026, importowanie profili rozpoczęło się poprzez API, CSV wysłanie lub SFTP może nie zakończyć, a importowane profile mogą nie być tworzone. Nowe integracje połączone w tym okresie mogą być również opóźnione w rozpoczęciu ich początkowej synchronizacji. Zidentyfikowaliśmy przyczynę i ustaliliśmy przyczynę. Pracujemy nad jak najszybszym rozwiązaniem tego problemu i wkrótce podzielimy się kolejną aktualizacją.

2. 23 lipca 2026 15:16 UTCmonitoring

   Import profili odzyskał, a import za pośrednictwem API, CSV wysyłka lub SFTP są normalnie ponownie przetwarzane. Integracje połączone w oknie zderzeniowym również wznawiają swoje początkowe synchronizacje. Nasz zespół pracuje nad przetworzeniem importu API, który zawiódł podczas incydentu. Kontynuujemy ścisłą obserwację i doceniamy twoją cierpliwość podczas tego incydentu.

3. 23 lipca 2026 16:01 UTCresolved

   System pozostaje stabilny, a import za pośrednictwem API, CSV wysyłania lub SFTP są przetwarzane normalnie. Przywóz, który nie powiódł się w trakcie incydentu, nie został poddany automatycznemu przetworzeniu. Jeżeli import rozpoczęty między 8: 00 a 11: 00 w USA / na wschodzie 23 lipca 2026 roku nie został zakończony, proszę go ponownie uruchomić, aby upewnić się, że profile są importowane. Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 21 lipca 2026 20:36 UTCinvestigating

   Obecnie badamy problem wpływający na subskrypcje SMS, opóźnienia w wysyłaniu SMS i błędy podczas tworzenia lub planowania kampanii SMS i WhatsApp. Pracujemy nad jak najszybszym przywróceniem normalnej obsługi. Będziemy dzielić się kolejną aktualizacją, jak tylko będziemy mieć więcej informacji.

2. 21 lipca 2026 20:47 UTCidentified

   Zidentyfikowaliśmy przyczynę problemu i wprowadzono rozwiązanie. Zaczynamy dostrzegać poprawę wydajności systemu.

3. 21 lipca 2026 20:57 UTCmonitoring

   Wydajność systemu dla SMS opt- w formach, wysyłanie i tworzenie kampanii i harmonogramowanie pozostaje stabilna. Kontynuujemy ścisłą obserwację i doceniamy twoją cierpliwość podczas tego incydentu.

4. 21 lipca 2026 21:09 UTCresolved

   Subskrypcje SMS, wysyłanie SMS oraz tworzenie i planowanie kampanii SMS i WhatsApp działają zgodnie z oczekiwaniami. Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 9 lipca 2026 01:52 UTCinvestigating

   O 16: 00 USA / Wschód 8 lipca 2026 roku, zidentyfikowaliśmy opóźnienia synchronizacji aktualizacji produktów z integracjami za pomocą haczyków. Powoduje to, że dane katalogowe, w tym w szablonach i w centrum obsługi klienta, nie mogą być aktualizowane w czasie rzeczywistym. Klient może zobaczyć nieaktualne dane produktu do 4 godzin. Wysyłanie nie ma wpływu, ale dane produktu w szablonach mogą nie odzwierciedlać informacji w czasie rzeczywistym. Pracujemy nad jak najszybszym rozwiązaniem tego problemu i wkrótce podzielimy się kolejną aktualizacją.

2. 9 lipca 2026 03:14 UTCidentified

   Od 9: 45 PM US / Eastern 8 lipca 2026, wstrzymaliśmy przetwarzanie nowych haczyków do katalogów produktów, podczas gdy nadal pracujemy nad naprawą. Dane katalogowe, w tym szablony i hub klienta, pozostaną nieaktualne do czasu ponownego synchronizacji. Nasz zespół inżynieryjny aktywnie pracuje nad przywróceniem aktualizacji katalogu w czasie rzeczywistym. Dostarczymy aktualizacje, jak tylko będzie więcej informacji.

3. 9 lipca 2026 04:34 UTCmonitoring

   Od 11: 13 PM US / Eastern 8 lipca 2026, wznowiliśmy przetwarzanie haczyków. Oznacza to, że wszystkie nowe haki webowe z integracji, które używają haków webowych do aktualizacji produktów, są teraz synchronizowane w czasie rzeczywistym. Nasz zespół inżynieryjny pracuje nad naprawą każdej aktualizacji haczyków webhaków z czasów uderzenia (9: 45 PM i 11: 13 PM US / Eastern Lipiec 8, 2026). Potwierdzimy, że po zakończeniu naprawy i zakończeniu incydentu.

4. 9 lipca 2026 16:13 UTCmonitoring

   Aktualizacje produktów z integracji ecommerce nadal synchronizują się normalnie w czasie rzeczywistym. Naprawa tła w celu pełnej aktualizacji rekordów z wcześniejszego okna uderzenia (9: 45 PM do 11: 13 PM USA / Wschód w dniu 8 lipca 2026) jest nadal w toku. Potwierdzimy to po zakończeniu naprawy.

5. 10 lipca 2026 21:01 UTCresolved

   Naprawa w celu dogonienia aktualizacji produktu haki internetowe z okna uderzenia została zakończona, a dane dotyczące produktu są aktualne. Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 7 lipca 2026 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 lipca 2026 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 lipca 2026 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 lipca 2026 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 lipca 2026 16:56 UTCresolved

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

1. 2 lipca 2026 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 lipca 2026 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 czerwca 2026 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 czerwca 2026 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 czerwca 2026 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 czerwca 2026 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 czerwca 2026 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 czerwca 2026 19:02 UTCidentified

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

3. 10 czerwca 2026 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 czerwca 2026 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 czerwca 2026 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 czerwca 2026 21:19 UTCidentified

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

3. 8 czerwca 2026 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 czerwca 2026 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 czerwca 2026 00:49 UTCresolved

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

1. 6 czerwca 2026 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 czerwca 2026 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 czerwca 2026 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 czerwca 2026 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 czerwca 2026 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 czerwca 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 01:38 UTCidentified

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

7. 6 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 maja 2026 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 kwietnia 2026 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 kwietnia 2026 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 kwietnia 2026 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.