Istoricul incidentelor Klaviyo

1. 27 august 2026 la 00:09 UTCinvestigating

   La ora 3:25 PM SUA/Est pe 26 august 2026, am inceput sa ne confruntam cu o problema in care unele profile nu progreseaza cu actiunile de intarziere a timpului din trecut in fluxurile asteptate. Acest lucru afectează trimiterea fluxului prin toate canalele de mesagerie, inclusiv e-mail, mesaje text, împinge, și WhatsApp. Mesajele trimise din campanii și fluxurile care nu includ acțiuni de întârziere a timpului nu sunt afectate. Lucrăm activ la un fix. Vom continua să oferim actualizări pe măsură ce devin disponibile mai multe informații.

2. 27 august 2026 la 01:15 UTCidentified

   Echipa noastră de Inginerie a identificat cauza acestei probleme și lucrează la implementarea unui fix pentru a rezolva impactul rămas asupra trimiterii fluxurilor afectate de problema întârzierii în timp. Odată ce fix este lansat, vom revizui și repara orice fluxuri afectate. Ne străduim să rezolvăm acest lucru cât mai repede posibil și vom împărtăși o altă actualizare în curând.

3. 27 august 2026 la 01:51 UTCmonitoring

   De la ora 9:30 PM SUA/Est, fluxurile au reluat trimiterea aşa cum era de aşteptat pe toate canalele de mesagerie afectate. Procesăm istoricul mesajelor de flux afectate. A fost implementat un fix și performanța sistemului se îmbunătățește. Continuăm să monitorizăm îndeaproape și să apreciem răbdarea dumneavoastră pe parcursul acestui incident.

4. 27 august 2026 la 03:42 UTCresolved

   Începând cu ora 11:26 PM SUA/Est pe 26 august 2026, reparația pentru procesarea mesajelor de flux afectate din fereastra de impact a fost finalizată, iar trimiterea fluxului a fost reluată conform așteptărilor pe toate canalele. Ne cerem scuze pentru deranjul cauzat. Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 19 august 2026 la 17:15 UTCidentified

   În prezent, experimentăm întârzieri de până la aproximativ 3 ore în modul în care actualizările recente ale proprietății de profil se reflectă în segmente în timp real. Aceasta înseamnă că modificările profilurilor pot dura mai mult decât de obicei pentru a actualiza calitatea de membru al segmentelor, ceea ce poate afecta ţintirea pe segment. Trimiterea prin e-mail și SMS și alte funcții de bază funcționează normal. Lucrăm activ pentru a rezolva această problemă și vom împărtăși o altă actualizare de îndată ce vom avea mai multe informații.

2. 19 august 2026 la 18:13 UTCmonitoring

   A fost implementat un fix și performanța sistemului se îmbunătățește. Actualizările recente privind proprietatea de profil se reflectă în segmentele în timp real mai rapid, iar întârzierea s-a îmbunătățit la aproximativ 2,5 ore. Modificările profilurilor pot dura încă puțin mai mult decât de obicei pentru a actualiza calitatea de membru al segmentului pe măsură ce sistemul continuă să recupereze. Trimiterea prin e-mail și SMS și alte funcții de bază rămân neafectate. Continuăm să monitorizăm îndeaproape și să apreciem răbdarea dumneavoastră pe parcursul acestui incident.

3. 19 august 2026 la 18:38 UTCresolved

   Actualizările profilului de proprietate sunt acum reflectate în segmente în timp real la viteza normală. Orice modificări de proprietate profil efectuate în timpul ferestrei incidentului au fost reflectate în calitatea de membru al segmentului, așa cum se așteaptă, și nu este necesară nicio acțiune din partea ta. Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 12 august 2026 la 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 la 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 la 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 august 2026 la 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 la 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 la 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 iulie 2026 la 14:35 UTCidentified

   Începând cu ora 8:09 AM SUA/Est pe 23 iulie 2026, importurile de profil au început prin API, CSV upload, sau SFTP nu se pot finaliza, iar profilurile importate nu pot fi create. Noile integrări conectate în această perioadă pot fi, de asemenea, întârziate la pornirea sincronizării inițiale. Am identificat cauza și sunt implementarea unui fix. Ne străduim să rezolvăm acest lucru cât mai repede posibil și vom împărtăși o altă actualizare în curând.

2. 23 iulie 2026 la 15:16 UTCmonitoring

   Importurile de profile s-au redresat, iar importurile prin API, CSV încarcă sau SFTP se prelucrează în mod normal din nou. Integrarile conectate în timpul ferestrei de impact sunt, de asemenea, reluarea sincronizărilor lor inițiale. Echipa noastră lucrează la reprocesarea importurilor API care au eşuat în timpul incidentului. Continuăm să monitorizăm îndeaproape și să apreciem răbdarea dumneavoastră pe parcursul acestui incident.

3. 23 iulie 2026 la 16:01 UTCresolved

   Sistemul rămâne stabil, iar importurile prin API, CSV upload, sau SFTP sunt de prelucrare în mod normal. Importurile care au eșuat în timpul incidentului nu au fost reprelucrate automat. Dacă un import pe care l-aţi început între orele 8:00 şi 11:00 AM SUA/Est pe 23 iulie 2026 nu s-a încheiat, vă rugăm să-l rerulaţi pentru a vă asigura că aceste profile sunt importate. Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 20:36 UTCinvestigating

   Investigăm în prezent o problemă care afectează abonamentele la SMS, întârzierile în trimiterea SMS-urilor și erorile la crearea sau programarea campaniilor SMS și WhatsApp. Lucrăm pentru a restabili serviciul normal cât mai repede posibil. Vom împărtăși o altă actualizare de îndată ce vom avea mai multe informații.

2. 21 iulie 2026 la 20:47 UTCidentified

   Am identificat cauza problemei și a fost pusă în aplicare o soluție. Începem să vedem îmbunătăţiri ale performanţei sistemului.

3. 21 iulie 2026 la 20:57 UTCmonitoring

   Performanțele sistemului pentru formularele opt-in SMS, trimiterea și crearea și programarea campaniilor rămân stabile. Continuăm să monitorizăm îndeaproape și să apreciem răbdarea dumneavoastră pe parcursul acestui incident.

4. 21 iulie 2026 la 21:09 UTCresolved

   Abonamentele SMS, trimiterea SMS-urilor şi crearea şi programarea campaniilor SMS şi WhatsApp funcţionează conform aşteptărilor. Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 9 iulie 2026 la 01:52 UTCinvestigating

   La ora 4:00 PM US/East pe 8 iulie 2026, am identificat întârzieri în sincronizarea actualizărilor de produs de la integrări folosind site-uri web. Acest lucru provoacă date de catalog, inclusiv în șabloane și Hubul Client, pentru a nu actualiza în timp real. Clientul poate vedea că datele produsului sunt expirate până la 4 ore. Trimiterea nu este afectată, dar datele privind produsul din machete pot să nu reflecte informații în timp real. Ne străduim să rezolvăm acest lucru cât mai repede posibil și vom împărtăși o altă actualizare în curând.

2. 9 iulie 2026 la 03:14 UTCidentified

   La 9:45 PM US/East pe 8 iulie 2026, am oprit procesarea de noi site-uri web pentru cataloagele de produse în timp ce continuăm să lucrăm la un fix. Datele de catalog, inclusiv în șabloane și Hub de clienți, vor rămâne expirate până la sincronizarea CV-urilor. Echipa noastră de inginerie este activ de lucru pentru a restabili actualizări catalog în timp real. Vom oferi actualizări de îndată ce mai multe informații sunt disponibile.

3. 9 iulie 2026 la 04:34 UTCmonitoring

   Începând cu ora 11:13 PM US/East pe 8 iulie 2026, am reluat procesarea de site-uri web. Acest lucru înseamnă toate noile site-uri web din integrări care utilizează site-uri web pentru a actualiza produsele sunt acum sincronizare în timp real. Echipa noastra de Inginerie lucreaza la implementarea unei reparatii pentru a prinde din urma orice actualizare a produselor din timpul ferestrei de impact (9:45 PM si 11:13 PM US/East 8, 2026). Vom confirma o dată reparația a fost completă și incidentul a fost complet rezolvat.

4. 9 iulie 2026 la 16:13 UTCmonitoring

   Actualizările produselor de la integrarea în comerțul electronic continuă să se sincronizeze în mod normal în timp real. O reparaţie de fundal pentru actualizarea completă a înregistrărilor de la fereastra de impact anterioară (9:45 PM până la 11:13 PM SUA/Est pe 8 iulie 2026) este încă în desfăşurare. Vom confirma odată ce această reparație este completă.

5. 10 iulie 2026 la 21:01 UTCresolved

   Reparația pentru a prinde din urmă pe site-ul de actualizare a produsului din fereastra de impact a fost finalizată, și datele de produs afectate este la zi. Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

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

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

1. 2 iulie 2026 la 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 iulie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 19:02 UTCidentified

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

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

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

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

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

1. 6 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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.