Historique des pannes de Klaviyo

1. 27 août 2026 à 00:09 UTCinvestigating

   À 15 h 25, le 26 août 2026, les États-Unis et l'Est ont commencé à faire face à un problème où certains profils ne progressent pas dans le temps. Cela affecte l'envoi de flux sur tous les canaux de messagerie, y compris les courriels, les messages texte, les push et WhatsApp. Les messages envoyés par les campagnes et les flux qui n'incluent pas les mesures de retard ne sont pas touchés. Nous travaillons activement sur une solution. Nous continuerons de fournir des mises à jour à mesure que de plus amples renseignements seront disponibles.

2. 27 août 2026 à 01:15 UTCidentified

   Notre équipe d'ingénierie a identifié la cause de ce problème et s'emploie à mettre en place un correctif pour résoudre le reste de l'impact sur l'envoi des flux touchés par le problème des délais. Une fois la correction déployée, nous examinerons et réparerons tous les flux touchés. Nous nous efforçons de résoudre ce problème le plus rapidement possible et nous partagerons une autre mise à jour sous peu.

3. 27 août 2026 à 01:51 UTCmonitoring

   À 21h30, les flux ont repris comme prévu sur tous les canaux de messagerie touchés. Nous traitons l'arriéré des messages de flux touchés. Un correctif a été déployé et la performance du système s'améliore. Nous continuons à surveiller de près et à apprécier votre patience tout au long de cet incident.

4. 27 août 2026 à 03:42 UTCresolved

   À 11 h 26, heure des États-Unis et de l'Est, le 26 août 2026, la réparation des messages d'écoulement affectés par le traitement de la fenêtre d'impact a été achevée et l'envoi des flux a repris comme prévu dans tous les canaux. Nous nous excusons pour la perturbation que cela a causé. Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 19 août 2026 à 17:15 UTCidentified

   Nous connaissons actuellement des retards allant jusqu'à environ 3 heures dans la rapidité avec laquelle les mises à jour récentes des propriétés de profil se reflètent dans les segments en temps réel. Cela signifie que les changements aux profils peuvent prendre plus de temps que d'habitude pour mettre à jour l'adhésion au segment, ce qui peut affecter le ciblage par segment. L'envoi de courriels et de SMS et d'autres fonctions de base fonctionnent normalement. Nous travaillons activement à résoudre ce problème et partagerons une autre mise à jour dès que nous aurons plus d'informations.

2. 19 août 2026 à 18:13 UTCmonitoring

   Un correctif a été déployé et la performance du système s'améliore. Les mises à jour récentes des propriétés de profil sont maintenant reflétées dans les segments en temps réel plus rapidement, et le délai s'est amélioré à environ 2,5 heures. Les changements aux profils peuvent encore prendre un peu plus de temps que d'habitude pour mettre à jour l'adhésion au segment au fur et à mesure que le système continue de rattraper son retard. L'envoi de courriels et de SMS et d'autres fonctions de base restent inchangés. Nous continuons à surveiller de près et à apprécier votre patience tout au long de cet incident.

3. 19 août 2026 à 18:38 UTCresolved

   Les mises à jour des propriétés de profil sont maintenant reflétées dans des segments en temps réel à vitesse normale. Tout changement de propriété de profil effectué pendant la fenêtre d'incident a été reflété dans l'adhésion au segment comme prévu, et aucune action n'est requise de votre part. Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 12 août 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 août 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 août 2026 à 16:47 UTCinvestigating

   À partir du 5 août 2026 vers 12h00, nous avons commencé à enquêter sur une question touchant certains abonnements par courriel et certaines fonctions de campagne. Les clients qui utilisent le double opt-in peuvent trouver que les nouveaux abonnés ne reçoivent pas les courriels de confirmation comme prévu. Certains utilisateurs peuvent rencontrer des erreurs lors de l'envoi de courriels de prévisualisation, de campagnes de planification ou de la vérification du nombre de destinataires estimés. Notre équipe s'efforce de résoudre ce problème. Nous partagerons une autre mise à jour dès que nous aurons plus d'informations.

2. 5 août 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 août 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 août 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.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 23 juillet 2026 à 14:35 UTCidentified

   Dès le 23 juillet 2026, vers 8 h 09, les importations de profil ont commencé par l'API, le téléchargement de CSV ou le SFTP. Les nouvelles intégrations connectées pendant cette période peuvent également être retardées dans le démarrage de leur synchronisation initiale. Nous avons identifié la cause et déployons une solution. Nous nous efforçons de résoudre ce problème le plus rapidement possible et nous partagerons une autre mise à jour sous peu.

2. 23 juillet 2026 à 15:16 UTCmonitoring

   Les importations de profil se sont rétablies, et les importations par l'intermédiaire de l'API, du téléchargement CSV ou du SFTP sont traitées à nouveau normalement. Les intégrations connectées pendant la fenêtre d'impact reprennent également leur synchronisation initiale. Notre équipe travaille au retraitement des importations d'API qui ont échoué pendant l'incident. Nous continuons à surveiller de près et à apprécier votre patience tout au long de cet incident.

3. 23 juillet 2026 à 16:01 UTCresolved

   Le système reste stable, et les importations via l'API, le téléchargement CSV ou le SFTP sont traitées normalement. Les importations qui ont échoué pendant l'incident n'ont pas été traitées automatiquement. Si une importation que vous avez commencée entre 8h00 et 11h00 US/Eastern le 23 juillet 2026 n'a pas été terminée, veuillez la réutiliser pour s'assurer que ces profils sont importés. Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 21 juillet 2026 à 20:36 UTCinvestigating

   Nous enquêtons actuellement sur un problème touchant les abonnements SMS, les retards dans l'envoi de SMS, et les erreurs lors de la création ou de la programmation de campagnes SMS et WhatsApp. Nous travaillons à rétablir le service normal le plus rapidement possible. Nous partagerons une autre mise à jour dès que nous aurons plus d'informations.

2. 21 juillet 2026 à 20:47 UTCidentified

   Nous avons identifié la cause du problème et un correctif a été mis en œuvre. Nous commençons à voir des améliorations dans la performance du système.

3. 21 juillet 2026 à 20:57 UTCmonitoring

   La performance du système pour les formulaires d'opt-in SMS, l'envoi et la création et la programmation de campagne reste stable. Nous continuons à surveiller de près et à apprécier votre patience tout au long de cet incident.

4. 21 juillet 2026 à 21:09 UTCresolved

   Les abonnements SMS, l'envoi de SMS, ainsi que la création et la programmation des campagnes SMS et WhatsApp fonctionnent comme prévu. Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 9 juillet 2026 à 01:52 UTCinvestigating

   À 16h00 US/Eastern le 8 juillet 2026, nous avons identifié des retards dans la synchronisation des mises à jour de produits des intégrations à l'aide de webhooks. Cela provoque des données de catalogue, y compris dans Templates et le Customer Hub, à ne pas mettre à jour en temps réel. Le client peut voir les données du produit périmées de 4 heures au maximum. L'envoi n'est pas affecté, mais les données du produit dans les modèles peuvent ne pas refléter les informations en temps réel. Nous nous efforçons de résoudre ce problème le plus rapidement possible et nous partagerons une autre mise à jour sous peu.

2. 9 juillet 2026 à 03:14 UTCidentified

   À partir de 21h45 US/Eastern le 8 juillet 2026, nous avons interrompu le traitement de nouveaux webhooks pour les catalogues de produits pendant que nous continuons à travailler sur un correctif. Les données du catalogue, y compris dans Templates et Customer Hub, resteront obsolètes jusqu'à ce que la synchronisation reprenne. Notre équipe d'ingénierie travaille activement à restaurer les mises à jour de catalogue en temps réel. Nous fournirons des mises à jour dès que plus d'informations seront disponibles.

3. 9 juillet 2026 à 04:34 UTCmonitoring

   Le 8 juillet 2026, à 23 h 13, nous avons repris le traitement des webhooks. Cela signifie que tous les nouveaux webhooks d'intégrations qui utilisent webhooks pour mettre à jour des produits sont maintenant synchronisés en temps réel. Notre équipe d'ingénierie travaille à mettre en œuvre une réparation pour rattraper sur n'importe quel webhooks de mise à jour de produit lors de la fenêtre d'impact (9:45 PM et 23:13 PM US/Eastern 8 juillet 2026). Nous confirmerons une fois la réparation terminée et l'incident résolu.

4. 9 juillet 2026 à 16:13 UTCmonitoring

   Les mises à jour des produits des intégrations ecommerce continuent à se synchroniser normalement en temps réel. Une réparation de fond pour mettre à jour les dossiers de la fenêtre d'impact précédente (9h45 à 23h13 US/Eastern le 8 juillet 2026) est toujours en cours. Nous confirmerons une fois cette réparation terminée.

5. 10 juillet 2026 à 21:01 UTCresolved

   La réparation pour rattraper le retard sur les webhooks de mise à jour de produits à partir de la fenêtre de l'impact a été terminée, et les données de produits touchés sont à jour. Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

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

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

1. 2 juillet 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 juillet 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 juin 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 juin 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 juin 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 juin 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 juin 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 juin 2026 à 19:02 UTCidentified

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

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

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

3. 8 juin 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 juin 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 juin 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 juin 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 juin 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 juin 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 juin 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 juin 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 juin 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 mai 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 avril 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 avril 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 avril 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.