Klaviyo 中断历史

1. 2026年8月27日 UTC 00:09investigating

   2026年8月26日下午3:25, 我们开始经历一个问题, 包括电子邮件、短信、推及WhatsApp。 从运动中发送的信息,以及不包括时间延迟行动的流动,均不受影响. 我们正在积极寻找解决办法。 我们将继续在获得更多信息后提供最新情况.

2. 2026年8月27日 UTC 01:15identified

   我们的工程小组已查明这一问题的原因,并正努力执行一个固定办法,以解决对运送受时间拖延问题所影响的流动的剩余影响。 一旦修复方案推出,我们将审查并修复任何受影响的流动。 我们正努力尽快解决这一问题,并将很快分享另一个最新情况.

3. 2026年8月27日 UTC 01:51monitoring

   截至9:30美国/东部, 我们正在处理积压的受影响流动信息。 已部署一个固定装置,系统性能正在改进。 我们继续密切监测并赞赏你在整个事件中的耐心.

4. 2026年8月27日 UTC 03:42resolved

   截至2026年8月26日11:26 PM US/Eastern,处理从撞击窗口发出的受影响流信息的修复工作已经完成,所有渠道的流量发送恢复到预期状态. 我们对此造成的破坏表示歉意。 这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月19日 UTC 17:15identified

   目前,在实时部分反映最新概况财产更新的速度方面,我们面临长达3小时的延误。 这意味着改变剖面图可能需要比通常更长的时间来更新分部成员,这可能影响基于分部的目标设定. 电子邮件和短信发送以及其他核心职能正常运行。 我们正在积极努力解决这一问题,一旦我们掌握了更多信息,我们将分享另一个最新情况.

2. 2026年8月19日 UTC 18:13monitoring

   已部署一个固定装置,系统性能正在改进。 近期的概况财产更新正在更快地反映在实时段,延迟时间已增至约2.5小时。 随着系统继续追赶,对概况的修改可能需要比通常的时间稍长一些才能更新部分成员。 电子邮件和短信发送及其他核心职能仍未受到影响。 我们继续密切监测并赞赏你在整个事件中的耐心.

3. 2026年8月19日 UTC 18:38resolved

   配置文件属性更新现以正常速度在实时段得到反映. 在事件窗口期间所做的任何配置属性改变都如所期望的那样反映在分部成员中,你无需采取任何行动。 这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月12日 UTC 18:04monitoring

   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日 UTC 18:14resolved

   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日 UTC 16:47investigating

   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日 UTC 17:26identified

   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日 UTC 17:36monitoring

   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日 UTC 17:54resolved

   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日 UTC 14:35identified

   2026年7月23日开始于8:09 AM US/Eastern左右,通过API,CSV上传,或SFTP可能无法完成配置文件的配置文件导入,而导入的配置文件可能无法创建. 在此期间连接的新集成也可能被推迟开始初始同步. 我们已经查明了原因,正在部署一个解决办法。 我们正努力尽快解决这一问题,并将很快分享另一个最新情况.

2. 2026年7月23日 UTC 15:16monitoring

   概况进口已恢复,通过API、CSV上传或SFTP的进口正在正常地进行处理。 在撞击窗口中连接的整合也恢复了初始同步. 我们的团队正在重新处理 API的进口 在事件中失败。 我们继续密切监测并赞赏你在整个事件中的耐心.

3. 2026年7月23日 UTC 16:01resolved

   系统保持稳定,通过API,CSV上传,或SFTP的导入正常进行处理. 事件中失败的导入没有自动进行再处理 。 如果您在2026年7月23日早上8点到11点之间开始进口, 请重新运行, 这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月21日 UTC 20:36investigating

   我们正在调查一个影响短信订阅、短信发送延误以及创建或安排短信和WhatsApp活动时出错的问题。 我们正在努力尽快恢复正常服务。 一旦我们掌握了更多信息,我们将分享另一个最新情况.

2. 2026年7月21日 UTC 20:47identified

   我们查明了问题的根源,并落实了一项解决办法。 我们开始看到系统性能的改善.

3. 2026年7月21日 UTC 20:57monitoring

   短信选择表、发送、创建和时间安排的系统性能保持稳定。 我们继续密切监测并赞赏你在整个事件中的耐心.

4. 2026年7月21日 UTC 21:09resolved

   短消息订阅、短消息发送以及短消息和WhatsApp运动的创建和时间安排正在按预期进行。 这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月9日 UTC 01:52investigating

   2026年7月8日下午4点, 这导致包括模板和客户枢纽在内的目录数据不能实时更新. 客户可能看到产品数据在4小时内过时。 发送不受影响,但模板中的产品数据可能不反映实时信息。 我们正努力尽快解决这一问题,并将很快分享另一个最新情况.

2. 2026年7月9日 UTC 03:14identified

   从2026年7月8日晚上9点45分起, 包括模板和客户枢纽在内的目录数据将保持过时,直至恢复同步。 我们的工程团队正积极恢复实时目录更新. 一旦获得更多信息,我们将提供最新资料.

3. 2026年7月9日 UTC 04:34monitoring

   2026年7月8日, 这意味着所有来自集成的新网络用户使用网络用户更新产品,现在正在实时同步。 我们的工程团队正在着手进行修复,以赶上撞击窗口期间(2026年7月8日晚上9点45分和11点13分)的任何产品更新。 一旦修复完成,事故得到彻底解决,我们将确认.

4. 2026年7月9日 UTC 16:13monitoring

   电子商务一体化的产品更新继续实时同步。 2026年7月8日, 为全面更新早期撞击窗口(9:45 PM至11:13 PM US/Eastern)的记录, 修复完成后我们会确认.

5. 2026年7月10日 UTC 21:01resolved

   从冲击窗口获取产品更新的修复工作已经完成,受影响的产品数据是最新的。 这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月7日 UTC 15:33investigating

   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日 UTC 15:56identified

   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日 UTC 16:32identified

   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日 UTC 16:47monitoring

   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日 UTC 16:56resolved

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

1. 2026年7月2日 UTC 12:17investigating

   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日 UTC 14:17resolved

   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日 UTC 14:49investigating

   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日 UTC 15:48identified

   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日 UTC 17:19monitoring

   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日 UTC 17:30resolved

   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日 UTC 18:47investigating

   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日 UTC 19:02identified

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

3. 2026年6月10日 UTC 19:23monitoring

   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日 UTC 19:46resolved

   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日 UTC 21:10investigating

   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日 UTC 21:19identified

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

3. 2026年6月8日 UTC 23:20identified

   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日 UTC 23:54monitoring

   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日 UTC 00:49resolved

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

1. 2026年6月6日 UTC 17:18investigating

   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日 UTC 23:05resolved

   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日 UTC 14:23investigating

   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日 UTC 14:46identified

   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日 UTC 15:06monitoring

   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日 UTC 17:16resolved

   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日 UTC 20:36investigating

   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日 UTC 22:21identified

   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日 UTC 00:30resolved

   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日 UTC 16:11investigating

   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日 UTC 16:46identified

   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日 UTC 17:17monitoring

   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日 UTC 17:38resolved

   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日 UTC 15:02investigating

   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日 UTC 17:10identified

   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日 UTC 18:37identified

   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日 UTC 20:19identified

   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日 UTC 23:13monitoring

   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日 UTC 00:31resolved

   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日 UTC 01:32investigating

   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日 UTC 02:22identified

   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日 UTC 03:46identified

   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日 UTC 07:08identified

   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日 UTC 16:59monitoring

   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日 UTC 19:05resolved

   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日 UTC 21:24investigating

   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日 UTC 22:33investigating

   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日 UTC 23:40investigating

   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日 UTC 00:25identified

   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日 UTC 00:57identified

   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日 UTC 01:38identified

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

7. 2026年5月6日 UTC 02:53monitoring

   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日 UTC 05:59monitoring

   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日 UTC 15:59monitoring

   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日 UTC 21:30monitoring

    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日 UTC 15:48monitoring

    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日 UTC 23:02resolved

    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日 UTC 07:24identified

   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日 UTC 07:43monitoring

   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日 UTC 08:11resolved

   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.