Klaviyo 장애 기록

1. 2026년 8월 27일 AM 12:09 UTCinvestigating

   에 3:25 오후 미국/동부 에 8월 26, 2026, 우리는 일부 프로파일이 예상대로 흐름에 과거 시간 지연 작업을 진행하지 않는 문제가 발생하기 시작했다. 이것은 이메일, 텍스트 메시징, 푸시 및 WhatsApp을 포함하여 모든 메시징 채널을 통해 흐르는 영향을받습니다. 캠페인에서 보내는 메시지, 시간 지연 작업을 포함하지 않는 흐름은 영향을받지 않습니다. 우리는 해결에 적극적으로 노력하고 있습니다. 더 많은 정보로 업데이트를 계속 제공 할 것입니다.

2. 2026년 8월 27일 AM 1:15 UTCidentified

   우리의 엔지니어링 팀은이 문제점의 원인을 확인하고 시간 지연 문제점에 의해 영향을받는 교류를 위해 전달에 남아있는 충격을 해결하기 위해 수정을 시행하기 위해 노력하고 있습니다. 수정이 압연되면, 우리는 어떤 영향을 미치는 흐름을 검토하고 수리합니다. 우리는 가능한 한 빨리 해결하기 위해 노력하고 다른 업데이트를 곧 공유 할 것입니다.

3. 2026년 8월 27일 AM 1:51 UTCmonitoring

   오전 9시 30분부터 미국/동부, 흐름은 모든 영향 받은 메시징 채널을 통해 예상대로 재송을 하였습니다. 우리는 영향을받은 흐름 메시지의 backlog를 처리하고 있습니다. 수정 및 시스템 성능이 향상되었습니다. 우리는 이 사건을 통해 밀접하고 감사를 계속합니다.

4. 2026년 8월 27일 AM 3:42 UTCresolved

   8월 26일 오후 11시 26분 미국/동부로 2026년 8월 26일, 영향의 창에서 영향을 받은 흐름 메시지를 처리하고, 흐름 전송은 모든 채널을 통해 예상대로 재개했습니다. 우리는 이 기인한 붕괴를 위해 사과합니다. 이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 19일 PM 5:15 UTCidentified

   최근 프로필 속성 업데이트가 실시간 세그먼트에 반영되는 방법에 대해 최대 3시간의 지연을 경험하고 있습니다. 이 프로파일의 변경은 세그먼트 기반 타겟팅에 영향을 미칠 수있는 세그먼트 회원을 업데이트하기 위해 평소보다 오래 걸릴 수 있습니다. 이메일 및 SMS 전송 및 기타 핵심 기능은 일반적으로 작동합니다. 우리는 적극적으로이를 해결하고 우리가 더 많은 정보가 있기 때문에 다른 업데이트를 공유합니다.

2. 2026년 8월 19일 PM 6:13 UTCmonitoring

   수정 및 시스템 성능이 향상되었습니다. 최근 프로필 속성 업데이트는 이제 실시간으로 반영되고, 지연은 약 2.5 시간으로 개선되었습니다. 단면도에 변화는 아직도 체계가 계속 붙잡기 때문에 세그먼트 회원을 새롭게 하기 위하여 평소보다 약간 오래 걸릴지도 모릅니다. 이메일 및 SMS 전송 및 기타 핵심 기능은 필수입니다. 우리는 이 사건을 통해 밀접하고 감사를 계속합니다.

3. 2026년 8월 19일 PM 6:38 UTCresolved

   프로필 속성 업데이트는 현재 정상적인 속도로 실시간 세그먼트에 반영됩니다. 모든 프로필 속성은 사건 창에 반영되어 세그먼트 멤버쉽에서 예상대로 반영되었으며, 해당 부분에서 동작이 필요하지 않습니다. 이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 12일 PM 6: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. 2026년 8월 12일 PM 6: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. 2026년 8월 5일 PM 4: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. 2026년 8월 5일 PM 5: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. 2026년 8월 5일 PM 5: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. 2026년 8월 5일 PM 5: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. 2026년 7월 23일 PM 2:35 UTCidentified

   7월 23, 2026일 오전 8시 9분 미국/동부를 시작으로 API, CSV 업로드 또는 SFTP를 통해 시작된 프로파일 가져오기가 완료되지 않을 수 있으며, 수입된 프로파일을 만들 수 없습니다. 이 기간 동안 연결된 새로운 통합은 초기 동기화를 시작할 수 있습니다. 우리는 원인을 확인하고 수정을 배포합니다. 우리는 가능한 한 빨리 해결하기 위해 노력하고 다른 업데이트를 곧 공유 할 것입니다.

2. 2026년 7월 23일 PM 3:16 UTCmonitoring

   API, CSV 업로드 또는 SFTP를 통한 프로파일 가져 오기가 정상적으로 처리됩니다. 영향 창에서 연결되는 통합은 또한 초기 동기화를 재작성합니다. 우리의 팀은 사건 도중 실패한 API 수입품을 재처리하기 위하여 일하고 있습니다. 우리는이 사건을 통해 밀접하고 감사를 계속합니다.

3. 2026년 7월 23일 PM 4:01 UTCresolved

   시스템은 안정적이며 API, CSV 업로드 또는 SFTP를 통해 가져올 수 있습니다. 사고에 실패한 수입은 자동으로 처리되지 않았습니다. 7월 23, 2026일 오전 8시와 오전 11시 사이에 시작된 수입이 완료되지 않았다면, 그 프로파일을 수입하기 위해 다시 실행하십시오. 이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 21일 PM 8:36 UTCinvestigating

   SMS 구독, SMS 전송 지연, SMS 및 WhatsApp 캠페인 생성 또는 스케줄링 할 때 오류에 대한 문제의 영향을 조사하고 있습니다. 우리는 가능한 한 빨리 정상적인 서비스를 복원하기 위해 노력하고 있습니다. 우리는 더 많은 정보가 있기 때문에 또 다른 업데이트를 공유 할 것입니다.

2. 2026년 7월 21일 PM 8:47 UTCidentified

   우리는 문제의 원인을 확인하고 수정이 구현되었습니다. 시스템 성능 향상을 시작으로.

3. 2026년 7월 21일 PM 8:57 UTCmonitoring

   SMS opt-in 형태, 전송 및 캠페인 생성 및 스케줄링에 대한 시스템 성능은 안정적입니다. 우리는 이 사건을 통해 밀접하고 감사를 계속합니다.

4. 2026년 7월 21일 PM 9:09 UTCresolved

   SMS 구독, SMS 전송 및 SMS 및 WhatsApp 캠페인의 생성 및 스케줄은 예상대로 작동합니다. 이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 9일 AM 1:52 UTCinvestigating

   4:00 PM US/Eastern on July 8, 2026, webhooks를 사용하여 통합에서 제품 업데이트 동기화를 확인했습니다. 템플릿과 고객 허브를 포함한 카탈로그 데이터를 실시간으로 업데이트하지 않습니다. 고객은 최대 4 시간까지 날짜의 제품 데이터를 볼 수 있습니다. Sending은 영향을받지 않지만 템플릿의 제품 데이터는 실시간 정보를 반영할 수 없습니다. 우리는 가능한 한 빨리 해결하기 위해 노력하고 다른 업데이트를 곧 공유 할 것입니다.

2. 2026년 7월 9일 AM 3:14 UTCidentified

   7월 8일 오후 9시 45분 미국/동부, 2026년, 우리는 제품 카탈로그에 대한 새로운 webhooks를 처리하고 수정을 계속합니다. 템플릿 및 고객 허브를 포함한 카탈로그 데이터는 이력서를 동기화 할 때까지 날짜를 남길 것입니다. 엔지니어링 팀은 실시간 카탈로그 업데이트를 복원하는 데 적극적으로 노력하고 있습니다. 더 많은 정보를 사용할 수 있도록 업데이트하겠습니다.

3. 2026년 7월 9일 AM 4:34 UTCmonitoring

   오후 11시 13분 / 7월 8일 동부 표준시, 2026년, 우리는 webhooks를 처리했습니다. 이것은 웹훅을 사용하여 제품을 업데이트하는 통합의 모든 새 웹훅이 실제 시간에 동기화하는 것을 의미합니다. 우리의 공학 팀은 충격 (9:45 PM 및 11:13 PM 미국 / 동부 7 월 8, 2026)의 창에서 모든 제품 업데이트 webhooks에 잡는 수리를 실시하고 있습니다. 수리가 완료되면 수리가 완료되고 사고가 완전히 해결되었습니다.

4. 2026년 7월 9일 PM 4:13 UTCmonitoring

   전자 상거래 통합의 제품 업데이트는 일반적으로 실시간으로 동기화됩니다. 이전 충격 창에서 완전히 업데이트 레코드에 대한 배경 수리 (9:45 PM에서 11:13 PM 미국 / 동부 7 월 8, 2026)는 여전히 진행 중입니다. 우리는 일단이 수리가 완료되면 확인합니다.

5. 2026년 7월 10일 PM 9:01 UTCresolved

   충격의 창에서 제품 업데이트 webhooks에 잡는 수리가 완료되었으며, 영향을받는 제품 데이터는 현재까지입니다. 이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 7일 PM 3: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. 2026년 7월 7일 PM 3: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. 2026년 7월 7일 PM 4: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. 2026년 7월 7일 PM 4: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. 2026년 7월 7일 PM 4:56 UTCresolved

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

1. 2026년 7월 2일 PM 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. 2026년 7월 2일 PM 2: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. 2026년 6월 12일 PM 2: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. 2026년 6월 12일 PM 3: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. 2026년 6월 12일 PM 5: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. 2026년 6월 12일 PM 5: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. 2026년 6월 10일 PM 6: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. 2026년 6월 10일 PM 7:02 UTCidentified

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

3. 2026년 6월 10일 PM 7: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. 2026년 6월 10일 PM 7: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. 2026년 6월 8일 PM 9: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. 2026년 6월 8일 PM 9:19 UTCidentified

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

3. 2026년 6월 8일 PM 11: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. 2026년 6월 8일 PM 11: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. 2026년 6월 9일 AM 12:49 UTCresolved

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

1. 2026년 6월 6일 PM 5: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. 2026년 6월 6일 PM 11: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. 2026년 6월 3일 PM 2: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. 2026년 6월 3일 PM 2: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. 2026년 6월 3일 PM 3: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. 2026년 6월 3일 PM 5: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. 2026년 5월 19일 PM 8: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. 2026년 5월 19일 PM 10: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. 2026년 5월 20일 AM 12: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. 2026년 5월 19일 PM 4: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. 2026년 5월 19일 PM 4: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. 2026년 5월 19일 PM 5: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. 2026년 5월 19일 PM 5: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. 2026년 5월 8일 PM 3: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. 2026년 5월 8일 PM 5: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. 2026년 5월 8일 PM 6: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. 2026년 5월 8일 PM 8: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. 2026년 5월 8일 PM 11: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. 2026년 5월 9일 AM 12: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. 2026년 5월 8일 AM 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. 2026년 5월 8일 AM 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. 2026년 5월 8일 AM 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. 2026년 5월 8일 AM 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. 2026년 5월 8일 PM 4: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. 2026년 5월 8일 PM 7: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. 2026년 5월 5일 PM 9: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. 2026년 5월 5일 PM 10: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. 2026년 5월 5일 PM 11: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. 2026년 5월 6일 AM 12: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. 2026년 5월 6일 AM 12: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. 2026년 5월 6일 AM 1:38 UTCidentified

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

7. 2026년 5월 6일 AM 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. 2026년 5월 6일 AM 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. 2026년 5월 6일 PM 3: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. 2026년 5월 6일 PM 9: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. 2026년 5월 7일 PM 3: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. 2026년 5월 7일 PM 11: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. 2026년 4월 26일 AM 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. 2026년 4월 26일 AM 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. 2026년 4월 26일 AM 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.