Klaviyo の障害履歴

1. 2026年8月27日 0:09 UTCinvestigating

   2026年8月26日午後3時25分にアメリカ/東日本では、過去のタイムディレイアクションが予想通りに進行していない問題が発生し始めました。 これは、電子メール、テキストメッセージング、プッシュ、およびWhatsAppを含むすべてのメッセージングチャネル間で送信するフローに影響を与えます。 キャンペーンからのメッセージ送信や、時間遅れのアクションを含まない流れは影響しません。 修正に積極的に取り組んでいます。 今後も、より一層の最新情報をお届けしてまいります.

2. 2026年8月27日 1:15 UTCidentified

   当社のエンジニアリングチームは、この問題の原因を特定し、時間遅延の問題の影響を受けるフローの送信に対する残りの影響を解決するために修正を実施するに取り組んでいます。 修正がロールアウトされると、衝撃的な流れを見直し、修理します。 可能な限り迅速に解決し、別のアップデートを短時間で共有します.

3. 2026年8月27日 1:51 UTCmonitoring

   米国東部の午後9時30分頃に、影響を受けたメッセージングチャネル全体で期待通り、流れを再開しました。 影響を受けるフローメッセージのバックログを処理します。 修正が展開され、システム性能が向上しました。 今後も、この事件を通じて、皆様のお越しをお待ちしております.

4. 2026年8月27日 3:42 UTCresolved

   2026年8月26日に米国東部午後11時26分頃に、衝撃の窓から影響を受けたフローメッセージを処理する修理が完成し、すべてのチャネルで期待通りフロー送信が再開しました。 弊社は、この原因の混乱を申し受けます。 この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月19日 17:15 UTCidentified

   現在、プロファイルプロパティの更新がリアルタイムセグメントに反映されるまで約3時間遅れが発生しています。 これは、プロファイルの変更は、セグメントベースのターゲティングに影響を与えることができるセグメントメンバーシップを更新するために、通常よりも時間がかかる場合があります。 電子メールおよびSMSの送信および他の中心機能は通常作動しています。 弊社では、この解決に積極的に取り組んでおり、情報が増えるとすぐに別のアップデートを共有します.

2. 2026年8月19日 18:13 UTCmonitoring

   修正が展開され、システム性能が向上しました。 最近のプロファイルプロパティの更新がリアルタイムセグメントに反映され、約2.5時間に遅延が改善されました。 プロファイルの変更は、システムが追いつくように、セグメントのメンバーシップを更新するために、通常よりも少し時間がかかることがあります。 電子メールおよびSMSの送信および他の中心機能はunaffected残ります。 今後も、この事件を通じて、皆様のお越しをお待ちしております.

3. 2026年8月19日 18:38 UTCresolved

   プロファイルプロパティの更新は、通常の速度でリアルタイムセグメントに反映されています。 インシデントウィンドウで行われたプロファイルプロパティの変更は、セグメントのメンバーシップに期待どおり反映され、その部分にアクションは必要ありません。 この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月12日 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. 2026年8月12日 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. 2026年8月5日 16:47 UTCinvestigating

   Beginning around 12:00 PM US/Eastern on August 5, 2026, we began investigating an issue affecting some email subscription and campaign features. Customers using double opt-in may find that new subscribers are not receiving confirmation emails as expected. Some users may encounter errors when sending preview emails, scheduling campaigns, or checking estimated recipient counts. Our team is working to resolve this. We will share another update as soon as we have more information.

2. 2026年8月5日 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. 2026年8月5日 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. 2026年8月5日 17:54 UTCresolved

   The email subscription and campaign features affected by this incident remain stable and are operating normally. Double opt-in confirmation emails, preview emails, and estimated recipient counts have returned to normal operation. Confirmation emails that failed to send during the incident are being resent. This incident has been resolved.

1. 2026年7月23日 14:35 UTCidentified

   2026年7月23日の午前8時09分頃から、API、CSVアップロード、SFTPでプロファイルインポートが始まり、インポートされたプロファイルが作成できないことがあります。 この期間中に接続された新しい統合は、初期同期を開始する際にも遅延することがあります。 原因を特定し、修正を展開しています。 可能な限り迅速に解決し、別のアップデートを短時間で共有します.

2. 2026年7月23日 15:16 UTCmonitoring

   プロファイルのインポートは、API、CSVのアップロード、またはSFTPを介して復元され、正常に処理されます。 インパクトウィンドウ内でのインテグレーションも初期同期を再開します。 当社のチームは、インシデント中に失敗したAPIインポートを再処理するために取り組んでいます。 今後も、この事件を通じて、皆様のお越しをお待ちしております.

3. 2026年7月23日 16:01 UTCresolved

   システムは、API、CSVのアップロード、またはSFTPで正常に処理されます。 インシデント中に失敗したインポートは自動的に再処理されていない。 2026年7月23日(水)午前8時～午後11時頃のアメリカ/東西の輸入が開始された場合は、そのプロファイルがインポートされるように再実行してください。 この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月21日 20:36 UTCinvestigating

   現在、SMSやWhatsAppキャンペーンを作成またはスケジューリングする際にSMSのサブスクリプション、SMS送信の遅延、エラーに影響を及ぼす問題を調査しています。 通常のサービスをできるだけ迅速に復元できるよう取り組んでおります。 情報が増えるとすぐに別のアップデートを共有します.

2. 2026年7月21日 20:47 UTCidentified

   問題の原因と修正が実装されていることを確認しました。 システムのパフォーマンス改善が始まります.

3. 2026年7月21日 20:57 UTCmonitoring

   SMSオプトインフォーム、送信、キャンペーン作成、スケジューリングなどのシステム性能が安定しています。 今後も、この事件を通じて、皆様のお越しをお待ちしております.

4. 2026年7月21日 21:09 UTCresolved

   SMS購読、SMS送信、およびSMSおよびWhatsAppキャンペーンの作成およびスケジューリングは期待どおりに動作します。 この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月9日 1:52 UTCinvestigating

   2026年7月8日、米国東部午後4時、当社は、Webhooksを用いた統合による製品のアップデートの同期を遅らせました。 これは、テンプレートや顧客ハブなどのカタログデータを引き起こし、リアルタイムで更新しません。 お客様からは、最大4時間以内の商品データを見ることができます。 送信は影響しませんが、テンプレートの商品データはリアルタイム情報を反映していない可能性があります。 可能な限り迅速に解決し、別のアップデートを短時間で共有します.

2. 2026年7月9日 3:14 UTCidentified

   2026年7月8日(水)の午後9時45分に米国東部にて、製品カタログの新webhook処理を行なっております。 テンプレートや顧客ハブなど、カタログデータは、履歴書を同期するまで、日付から残されます。 当社のエンジニアリングチームは、リアルタイムカタログの更新を復元するために積極的に取り組んでいます。 最新情報をお届けいたします.

3. 2026年7月9日 4:34 UTCmonitoring

   2026年7月8日、米国東部午後11時13分頃に、webhooksの処理を再開しました。 これは、Webhooksを使用して製品を更新する統合から新しいWebhooksがリアルタイムで同期されることを意味します。 当社のエンジニアリングチームは、衝撃の窓(9:45 PMと11:13 PM US/Eastern July 8, 2026)から、あらゆる製品アップデートのwebhooksを追い上げるために修理を実施しています。 修理が完了し、事故が完全に解決されたら確認します.

4. 2026年7月9日 16:13 UTCmonitoring

   Eコマースインテグレーションから製品のアップデートがリアルタイムで正常に同期し続けています。 以前の衝撃窓からレコードを完全に更新するための背景修復(9:45 PMから11:13 PM米国/東部2026)はまだ進行中です。 修理完了後確認いたします.

5. 2026年7月10日 21:01 UTCresolved

   衝撃の窓から製品更新のwebhooksを追い上げるための修理が完了し、影響を受けた製品データが最新です。 この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月7日 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. 2026年7月7日 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. 2026年7月7日 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. 2026年7月7日 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. 2026年7月7日 16:56 UTCresolved

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

1. 2026年7月2日 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日 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. 2026年6月12日 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. 2026年6月12日 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. 2026年6月12日 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. 2026年6月12日 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. 2026年6月10日 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. 2026年6月10日 19:02 UTCidentified

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

3. 2026年6月10日 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. 2026年6月10日 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. 2026年6月8日 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. 2026年6月8日 21:19 UTCidentified

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

3. 2026年6月8日 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. 2026年6月8日 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. 2026年6月9日 0: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日 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. 2026年6月6日 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. 2026年6月3日 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. 2026年6月3日 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. 2026年6月3日 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. 2026年6月3日 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. 2026年5月19日 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. 2026年5月19日 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. 2026年5月20日 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. 2026年5月19日 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. 2026年5月19日 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. 2026年5月19日 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. 2026年5月19日 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. 2026年5月8日 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. 2026年5月8日 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. 2026年5月8日 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. 2026年5月8日 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. 2026年5月8日 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. 2026年5月9日 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. 2026年5月8日 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日 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日 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日 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日 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. 2026年5月8日 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. 2026年5月5日 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. 2026年5月5日 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. 2026年5月5日 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. 2026年5月6日 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. 2026年5月6日 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. 2026年5月6日 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日 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日 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日 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. 2026年5月6日 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. 2026年5月7日 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. 2026年5月7日 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. 2026年4月26日 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日 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日 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.