Historial de interrupciones de Klaviyo

1. 27 de agosto de 2026 a las 0:09 UTCinvestigating

   A las 3:25 p.m. EE.UU./Este el 26 de agosto de 2026, comenzamos a experimentar un problema en el que algunos perfiles no están progresando más allá de las medidas de demora en los flujos como se esperaba. Esto está afectando el flujo enviando a través de todos los canales de mensajería, incluyendo correo electrónico, mensajería de texto, empuje y WhatsApp. Mensaje enviado de campañas, y flujos que no incluyen las acciones de retraso del tiempo no se impactan. Estamos trabajando activamente en una solución. Seguiremos proporcionando actualizaciones a medida que se disponga de más información.

2. 27 de agosto de 2026 a las 1:15 UTCidentified

   Nuestro equipo de ingeniería ha identificado la causa de este problema y está trabajando para implementar una solución para resolver el impacto restante en el envío de los flujos afectados por el problema de retraso de tiempo. Una vez que la solución sea lanzada, revisaremos y repararemos cualquier flujo impactado. Estamos trabajando para resolver esto lo más rápido posible y compartiremos otra actualización en breve.

3. 27 de agosto de 2026 a las 1:51 UTCmonitoring

   A las 9:30PM EE.UU./Este, los flujos han reanudado el envío como se esperaba en todos los canales de mensajería afectados. Estamos procesando el atraso de los mensajes de flujo afectados. Se ha implementado una solución y el rendimiento del sistema está mejorando. Seguimos monitoreando de cerca y apreciamos su paciencia durante todo este incidente.

4. 27 de agosto de 2026 a las 3:42 UTCresolved

   A las 11:26 PM EE.UU./Este el 26 de agosto de 2026, se ha completado la reparación para procesar los mensajes de flujo afectados desde la ventana de impacto, y el envío de flujo se ha reanudado según se espera en todos los canales. Nos disculpamos por la perturbación que esto causó. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 19 de agosto de 2026 a las 17:15 UTCidentified

   Actualmente estamos experimentando retrasos de hasta aproximadamente 3 horas en lo rápido que las actualizaciones recientes de propiedades de perfil se reflejan en segmentos en tiempo real. Esto significa que los cambios en los perfiles pueden llevar más tiempo de lo habitual para actualizar la composición de los segmentos, lo que puede afectar la segmentación basada en segmentos. El envío de correo electrónico y SMS y otras funciones básicas funcionan normalmente. Estamos trabajando activamente para resolver esto y compartiremos otra actualización tan pronto como tengamos más información.

2. 19 de agosto de 2026 a las 18:13 UTCmonitoring

   Se ha implementado una solución y el rendimiento del sistema está mejorando. Las actualizaciones recientes de propiedades de perfil se reflejan ahora en segmentos en tiempo real más rápidamente, y el retraso ha mejorado a aproximadamente 2,5 horas. Los cambios en los perfiles pueden tardar un poco más de lo habitual para actualizar la composición de los segmentos, ya que el sistema sigue al día. El envío de correo electrónico y SMS y otras funciones básicas siguen sin afectar. Seguimos monitoreando de cerca y apreciamos su paciencia durante todo este incidente.

3. 19 de agosto de 2026 a las 18:38 UTCresolved

   Las actualizaciones de propiedades del perfil se están reflejando ahora en segmentos en tiempo real a velocidad normal. Cualquier cambio de propiedad del perfil realizado durante la ventana del incidente se ha reflejado en la composición del segmento como se espera, y no se requiere ninguna acción por su parte. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 12 de agosto de 2026 a las 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 de agosto de 2026 a las 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.

Traducido automáticamente desde la actualización oficial del incidente.

1. 5 de agosto de 2026 a las 16:47 UTCinvestigating

   Comenzando alrededor de las 12:00 PM US/Este el 5 de agosto de 2026, comenzamos a investigar un problema que afecta a algunas funciones de suscripción y campaña de correo electrónico. Los clientes que utilizan doble opción pueden encontrar que los nuevos suscriptores no reciben emails de confirmación como se espera. Algunos usuarios pueden encontrar errores cuando envían emails de vista previa, campañas de programación, o comprueban los recuentos estimados del receptor. Nuestro equipo está trabajando para resolver esto. Compartiremos otra actualización tan pronto como tengamos más información.

2. 5 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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.

Traducido automáticamente desde la actualización oficial del incidente.

1. 23 de julio de 2026 a las 14:35 UTCidentified

   A partir de las 8:09 AM EE.UU./Este el 23 de julio de 2026, las importaciones de perfiles iniciadas a través de la API, carga CSV o SFTP pueden no completarse, y los perfiles importados pueden no ser creados. Las nuevas integraciones relacionadas durante este período también pueden retrasarse al iniciar su sincronización inicial. Hemos identificado la causa y estamos implementando una solución. Estamos trabajando para resolver esto lo más rápido posible y compartiremos otra actualización en breve.

2. 23 de julio de 2026 a las 15:16 UTCmonitoring

   Las importaciones de perfiles se han recuperado, y las importaciones a través de la API, carga CSV o SFTP se están procesando normalmente de nuevo. Las integraciones conectadas durante la ventana de impacto también están resumiendo sus sincronizaciones iniciales. Nuestro equipo está trabajando para reprocesar las importaciones de API que fallaron durante el incidente. Seguimos monitoreando de cerca y apreciamos su paciencia durante todo este incidente.

3. 23 de julio de 2026 a las 16:01 UTCresolved

   El sistema sigue siendo estable, y las importaciones a través de la API, la carga CSV o SFTP se procesan normalmente. Las importaciones que fallaron durante el incidente no fueron reprocesadas automáticamente. Si una importación iniciada entre las 8:00 AM y las 11:00 AM US/Este el 23 de julio de 2026 no se completó, por favor vuelva a ejecutarla para asegurar que esos perfiles sean importados. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de julio de 2026 a las 20:36 UTCinvestigating

   Actualmente estamos investigando un problema que impacta las suscripciones de SMS, retrasos en el envío de SMS y errores al crear o programar campañas SMS y WhatsApp. Estamos trabajando para restaurar el servicio normal lo más rápido posible. Compartiremos otra actualización tan pronto como tengamos más información.

2. 21 de julio de 2026 a las 20:47 UTCidentified

   Hemos identificado la causa de la cuestión y se ha aplicado una solución. Estamos empezando a ver mejoras en el rendimiento del sistema.

3. 21 de julio de 2026 a las 20:57 UTCmonitoring

   El rendimiento del sistema para los formularios SMS opt-in, el envío y la creación y programación de campañas sigue siendo estable. Seguimos monitoreando de cerca y apreciamos su paciencia durante todo este incidente.

4. 21 de julio de 2026 a las 21:09 UTCresolved

   Suscripciones de SMS, envío de SMS y la creación y programación de campañas de SMS y WhatsApp están operando como se espera. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 9 de julio de 2026 a las 1:52 UTCinvestigating

   A las 4:00 PM EE.UU./Este el 8 de julio de 2026, identificamos retrasos sincronizando actualizaciones de productos de las integraciones utilizando webhooks. Esto está causando que los datos de catálogo, incluyendo en Plantillas y el Centro de Clientes, no se actualicen en tiempo real. El cliente puede ver que los datos del producto no están actualizados hasta 4 horas. El envío no se impacta, pero los datos del producto en plantillas pueden no reflejar información en tiempo real. Estamos trabajando para resolver esto lo más rápido posible y compartiremos otra actualización en breve.

2. 9 de julio de 2026 a las 3:14 UTCidentified

   A las 9:45 p.m. EE.UU./Este el 8 de julio de 2026, detuvimos el procesamiento de nuevos webhooks para catálogos de productos mientras seguimos trabajando en una solución. Los datos del catálogo, incluso en Plantillas y Centro de Clientes, permanecerán fuera de la fecha hasta que se reanude la sincronización. Nuestro equipo de ingeniería está trabajando activamente para restaurar actualizaciones de catálogo en tiempo real. Proporcionaremos actualizaciones tan pronto como esté disponible más información.

3. 9 de julio de 2026 a las 4:34 UTCmonitoring

   A partir de las 11:13 p.m. EE.UU./Este el 8 de julio de 2026, hemos reanudado los juegos web de procesamiento. Esto significa que todos los nuevos webhooks de las integraciones que utilizan webhooks para actualizar los productos ahora están sincronizando en tiempo real. Nuestro equipo de ingeniería está trabajando en la implementación de una reparación para ponerse al día en cualquier actualización de productos webhooks desde la ventana de impacto (9:45 PM y 11:13 PM US/Este 8 de julio de 2026). Confirmaremos una vez que la reparación haya sido completa y el incidente haya sido resuelto completamente.

4. 9 de julio de 2026 a las 16:13 UTCmonitoring

   Las actualizaciones de productos de las integraciones del comercio electrónico continúan sincronizando normalmente en tiempo real. Todavía está en curso una reparación de antecedentes para actualizar los registros desde la ventana de impacto anterior (9:45 PM a 11:13 PM US/Este el 8 de julio de 2026). Confirmaremos una vez que esta reparación esté completa.

5. 10 de julio de 2026 a las 21:01 UTCresolved

   Se ha completado la reparación para ponerse al día en la actualización de productos webhooks desde la ventana de impacto, y los datos de productos afectados están al día. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 7 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 16:56 UTCresolved

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

1. 2 de julio de 2026 a las 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 de julio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 19:02 UTCidentified

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

3. 10 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 21:19 UTCidentified

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

3. 8 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 0:49 UTCresolved

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

1. 6 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 0: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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 0: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 de mayo de 2026 a las 1: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 de mayo de 2026 a las 2: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 de mayo de 2026 a las 3: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 de mayo de 2026 a las 7: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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 0: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 de mayo de 2026 a las 0: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 de mayo de 2026 a las 1:38 UTCidentified

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

7. 6 de mayo de 2026 a las 2: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 de mayo de 2026 a las 5: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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de abril de 2026 a las 7: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 de abril de 2026 a las 7: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 de abril de 2026 a las 8: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.