- Detected by Pingoru
- Jun 12, 2026, 02:49 PM UTC
- Resolved
- Jun 12, 2026, 05:30 PM UTC
- Duration
- 2h 40m
Affected: Customer AgentHelpdeskIntegrations - OtherWhatsApp
Timeline · 4 updates
-
investigating Jun 12, 2026, 02:49 PM UTC
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.
-
identified Jun 12, 2026, 03:48 PM UTC
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.
-
monitoring Jun 12, 2026, 05:19 PM UTC
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.
-
resolved Jun 12, 2026, 05:30 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 06:47 PM UTC
- Resolved
- Jun 10, 2026, 07:46 PM UTC
- Duration
- 58m
Affected: Email Content
Timeline · 4 updates
-
investigating Jun 10, 2026, 06:47 PM UTC
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.
-
identified Jun 10, 2026, 07:02 PM UTC
We have identified the root cause and are working on a fix. We will share another update shortly.
-
monitoring Jun 10, 2026, 07:23 PM UTC
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.
-
resolved Jun 10, 2026, 07:46 PM UTC
Customers should no longer see any errors when selecting a template while creating or editing a campaign. This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 09:10 PM UTC
- Resolved
- Jun 09, 2026, 12:49 AM UTC
- Duration
- 3h 39m
Affected: Campaign Email SendingSMS Sending - Toll Free Number SMSSMS Sending - Toll Free Number MMSSMS Sending - Short Code SMSSMS Sending - Short Code MMS
Timeline · 5 updates
-
investigating Jun 08, 2026, 09:10 PM UTC
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.
-
identified Jun 08, 2026, 09:19 PM UTC
We have identified the root cause and are working on a fix. We will share another update shortly.
-
identified Jun 08, 2026, 11:20 PM UTC
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.
-
monitoring Jun 08, 2026, 11:54 PM UTC
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.
-
resolved Jun 09, 2026, 12:49 AM UTC
Campaign sending has been restored and the backlog of delayed campaigns has completed sending. This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 06, 2026, 05:18 PM UTC
- Resolved
- Jun 06, 2026, 11:05 PM UTC
- Duration
- 5h 47m
Affected: WhatsApp
Timeline · 2 updates
-
investigating Jun 06, 2026, 05:18 PM UTC
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.
-
resolved Jun 06, 2026, 11:05 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 02:23 PM UTC
- Resolved
- Jun 03, 2026, 05:16 PM UTC
- Duration
- 2h 52m
Affected: Integrations - Shopify
Timeline · 4 updates
-
investigating Jun 03, 2026, 02:23 PM UTC
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.
-
identified Jun 03, 2026, 02:46 PM UTC
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.
-
monitoring Jun 03, 2026, 03:06 PM UTC
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.
-
resolved Jun 03, 2026, 05:16 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 08:36 PM UTC
- Resolved
- May 20, 2026, 12:30 AM UTC
- Duration
- 3h 54m
Affected: SMS Sending - Toll Free Number SMSSMS Sending - Toll Free Number MMSSMS Sending - Short Code SMSSMS Sending - Short Code MMSSMS Sending - OtherAnalyticsSegmentationFlow Triggering
Timeline · 3 updates
-
investigating May 19, 2026, 08:36 PM UTC
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.
-
identified May 19, 2026, 10:21 PM UTC
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.
-
resolved May 20, 2026, 12:30 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 04:11 PM UTC
- Resolved
- May 19, 2026, 05:38 PM UTC
- Duration
- 1h 27m
Affected: Klaviyo AppCampaign Email SendingSMS Sending - Toll Free Number SMSFlow Email SendingSMS Sending - Toll Free Number MMSSMS Sending - Short Code SMSSMS Sending - Short Code MMSSMS Sending - OtherMobile Push Sending
Timeline · 4 updates
-
investigating May 19, 2026, 04:11 PM UTC
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.
-
identified May 19, 2026, 04:46 PM UTC
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.
-
monitoring May 19, 2026, 05:17 PM UTC
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.
-
resolved May 19, 2026, 05:38 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 03:02 PM UTC
- Resolved
- May 09, 2026, 12:31 AM UTC
- Duration
- 9h 29m
Affected: Klaviyo AppAnalytics
Timeline · 6 updates
-
investigating May 08, 2026, 03:02 PM UTC
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.
-
identified May 08, 2026, 05:10 PM UTC
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.
-
identified May 08, 2026, 06:37 PM UTC
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.
-
identified May 08, 2026, 08:19 PM UTC
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.
-
monitoring May 08, 2026, 11:13 PM UTC
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.
-
resolved May 09, 2026, 12:31 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 01:32 AM UTC
- Resolved
- May 08, 2026, 07:05 PM UTC
- Duration
- 17h 32m
Affected: Klaviyo APIAnalyticsSegmentationFlow Triggering
Timeline · 6 updates
-
investigating May 08, 2026, 01:32 AM UTC
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.
-
identified May 08, 2026, 02:22 AM UTC
Our engineering team is continuing to monitor areas affected by the upstream service provider. At this stage, event processing has recovered and is working as expected. There remains processing delays for segmentation and analytics. There may be sending delays with Campaigns & Flows that rely include impacted segments and loading issues with reporting pages. We will provide updates as soon as more information is available.
-
identified May 08, 2026, 03:46 AM UTC
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.
-
identified May 08, 2026, 07:08 AM UTC
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.
-
monitoring May 08, 2026, 04:59 PM UTC
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.
-
resolved May 08, 2026, 07:05 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 09:24 PM UTC
- Resolved
- May 07, 2026, 11:02 PM UTC
- Duration
- 2d 1h
Affected: Klaviyo AppCampaign Email SendingCustomer AgentFlow Email SendingCustomer HubEmail DeliverabilityHelpdeskEmail ContentMobile Push SendingAnalyticsSegmentationReviewsList SubscriptionSignup FormsUnsubscribe & Preference PagesProfiles
Timeline · 12 updates
Read the full incident report →
- Detected by Pingoru
- Apr 26, 2026, 07:24 AM UTC
- Resolved
- Apr 26, 2026, 08:11 AM UTC
- Duration
- 46m
Affected: Klaviyo API
Timeline · 3 updates
-
identified Apr 26, 2026, 07:24 AM UTC
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.
-
monitoring Apr 26, 2026, 07:43 AM UTC
We successfully implemented a fix as of 3:20 AM US/Eastern that restored all API activity. We are continuing to monitor the results.
-
resolved Apr 26, 2026, 08:11 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 05:15 AM UTC
- Resolved
- Mar 27, 2026, 05:15 AM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Mar 27, 2026, 05:15 AM UTC
Mar 27, 01:15 EDT Resolved - Real-time segmentation is processing in real-time, and this incident has been resolved. Mar 27, 00:46 EDT Monitoring - Starting around 8:15 PM US Eastern 26th March, we began seeing delays in real-time segment processing for a subset of customers. Segments may be out of date by up to 2.5 hours. Engineering have identified a solution and are working to implement the fix shortly. We will continue to provide updates as real-time segmentation functionality is restored.
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 12:23 PM UTC
- Resolved
- Jan 12, 2026, 12:23 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Jan 12, 2026, 12:23 PM UTC
Jan 12, 07:23 EST Resolved - This incident has been resolved. Jan 12, 07:05 EST Monitoring - A fix has been implemented and we are monitoring results. Campaign sending and scheduling is back to normal, and all delayed campaigns have been replayed. Jan 12, 06:51 EST Identified - As of 6:45am US Eastern, the issue has been identified and a fix implemented. Any new scheduled or sent campaigns should process, with slight delays. We are actively replaying any campaigns that were delayed. Jan 12, 06:12 EST Investigating - Beginning around 5am US Eastern time, we began observing delays in campaign scheduling and sending. New campaigns, and scheduled RAST (calculate Recipient at Send Times) campaigns, are unable to send. However non-RAST campaigns that were scheduled prior to 5am US Eastern Time are processing as usual. We do not expect data loss. We are actively working to resolve the incident and will provide updates as soon as possible.
Read the full incident report →
- Detected by Pingoru
- Dec 23, 2025, 12:07 AM UTC
- Resolved
- Dec 23, 2025, 12:07 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2025, 06:36 AM UTC
- Resolved
- Dec 18, 2025, 06:36 AM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Dec 18, 2025, 06:36 AM UTC
Dec 18, 01:36 EST Resolved - This incident has been resolved. Dec 18, 01:06 EST Monitoring - A fix has been implemented and we are monitoring the results. Dec 18, 00:12 EST Identified - The issue has been identified and a fix is being implemented. Dec 17, 23:10 EST Investigating - Starting around 9:52pm US Eastern, a database upgrade failure caused data processing delays in-app. As a result, we are experiencing delays in event processing, flows, unsubscribes, segmentation, sending for certain campaigns, and v3 APIs. No data loss is expected. We are actively working to resolve the incident and will provide updates when possible.
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2025, 01:49 AM UTC
- Resolved
- Dec 17, 2025, 01:49 AM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Dec 17, 2025, 01:49 AM UTC
Dec 16, 20:49 EST Resolved - As of 8:23 PM US/Eastern on 12/16/2025, this incident has been resolved and template cloning functionality has been fully restored. Dec 16, 20:11 EST Monitoring - Beginning around 6:42 PM US/Eastern on 12/16/2025, customers may have noticed an issue with cloning templates from the Template Library. Our engineering team has identified the cause of this issue and is implementing a fix to restore functionality. We'll provide updates as soon as more information is available.
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 10:42 AM UTC
- Resolved
- Dec 05, 2025, 09:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 05, 2025, 10:42 AM UTC
Between 3:48am (US Eastern) and 4:10am (US Eastern) Cloudflare experienced an outage which affected Klaviyo. During this time, users were unable to access Klaviyo.com and all Klaviyo APIs. During this window, a number of services were affected. Subscription events and click tracking events were lost. Outbound campaign message sending was not affected. Klaviyo is now fully operational and this incident has been resolved. https://www.cloudflarestatus.com/incidents/k9ppxftx8bs5
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 08:36 PM UTC
- Resolved
- Dec 03, 2025, 08:36 PM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Nov 28, 2025, 10:05 PM UTC
- Resolved
- Nov 28, 2025, 10:05 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Nov 28, 2025, 10:05 PM UTC
Nov 28, 17:05 EST Resolved - This incident has been resolved. Nov 28, 16:11 EST Monitoring - Access to these services (Customer Hub, Helpdesk, and Customer Agent) remains stable. We are continuing to closely monitor these systems. Nov 28, 15:46 EST Identified - Starting at 3:40pm (US Eastern), we have restored access to these services (Customer Hub, Helpdesk, and Customer Agent). We continue to closely monitor these systems. Nov 28, 15:27 EST Investigating - Starting at 3:00pm (US Eastern), Klaviyo Helpdesk, Customer Hub, and the onsite web chat functionality of Customer Agent are unavailable. Our team is investigating the issue and will update with progress as soon as possible.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 07:06 PM UTC
- Resolved
- Nov 18, 2025, 07:06 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Nov 18, 2025, 07:06 PM UTC
Nov 18, 14:06 EST Resolved - This incident has been resolved, as of 2 pm US eastern. All affected components are operational. Nov 18, 09:34 EST Monitoring - Fixes have been implemented for some services and we are monitoring the issues. Nov 18, 08:58 EST Identified - Cloudflare declared an incident around 6:30 am US Eastern causing all onsite activities, such as unsubscribe and subscribe preference pages and onsite form submissions to error out. Forms appear, but no requests or related events or subscriptions are processing. API calls are also experiencing 403s. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We're currently investigating mitigation steps for the affected features.
Read the full incident report →
- Detected by Pingoru
- Nov 14, 2025, 10:00 PM UTC
- Resolved
- Nov 14, 2025, 10:00 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Nov 14, 2025, 10:00 PM UTC
Nov 14, 17:00 EST Completed - The scheduled maintenance has been completed. Nov 14, 11:00 EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov 14, 09:58 EST Scheduled - Between 11:00 AM and 5:00 PM US/Eastern on Friday, November 14, 2025, Klaviyo Engineering will perform maintenance on our events infrastructure. During this maintenance window, event analytics may be delayed up to 45 minutes. No data loss will occur and no other Klaviyo functionality will be impacted.
Read the full incident report →
- Detected by Pingoru
- Nov 02, 2025, 05:41 PM UTC
- Resolved
- Nov 02, 2025, 05:41 PM UTC
- Duration
- —
Timeline · 1 update
-
monitoring Nov 02, 2025, 05:41 PM UTC
Nov 2, 12:41 EST Resolved - The incident is now resolved. All delayed data for Facebook Integrations, which occurred between 1:00 AM and 2:00 AM, has been fully restored. Nov 2, 08:13 EST Monitoring - A fix has been identified and we are monitoring the results. Nov 2, 02:03 EST Identified - As of 1:00 AM ET (approximately one hour ago), our Facebook integration sync encountered a failure, resulting in a temporary delay in data sync. We have confirmed that no data has been lost, and the system failure is strictly impacting sync times. The root cause has been successfully identified, and our engineering team is actively working on deploying the necessary fix.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2025, 07:43 PM UTC
- Resolved
- Oct 29, 2025, 07:43 PM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Oct 24, 2025, 12:23 AM UTC
- Resolved
- Oct 24, 2025, 12:23 AM UTC
- Duration
- —
Affected: Email ContentUnsubscribe & Preference Pages
Timeline · 1 update
-
resolved Oct 24, 2025, 12:23 AM UTC
Between 3:46pm EST and 7:29pm EST on 23rd Oct 2025, customers may have noticed an issue causing web view & unsubscribe tags to redirect to incorrect Template previews or broken pages. This may have affected some customers' ability to view or test templates as expected. The Engineering team has identified the cause and implemented the fix. We are seeing links redirect as expected.
Read the full incident report →
- Detected by Pingoru
- Oct 21, 2025, 05:06 PM UTC
- Resolved
- Oct 21, 2025, 05:06 PM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →