Klaviyo Outage History

Started Apr 26, 2026, 07:24 AM UTC· resolved Apr 26, 2026, 08:11 AM UTC

1. 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.

2. 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.

3. 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 →

Started Mar 27, 2026, 05:15 AM UTC· resolved Mar 27, 2026, 05:15 AM UTC

1. 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 →

Started Jan 12, 2026, 12:23 PM UTC· resolved Jan 12, 2026, 12:23 PM UTC

1. 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 →

Started Dec 23, 2025, 12:07 AM UTC· resolved Dec 23, 2025, 12:07 AM UTC

1. monitoring Dec 23, 2025, 12:07 AM UTC

   Dec 22, 19:07 EST Resolved - This incident has been resolved. Dec 22, 18:58 EST Monitoring - We have confirmed the app is now widely available and are moving the incident to monitoring. 10% of accounts experienced messaging delays during this window. We are working to replay any impacted messages, including unsubscribes, inbound SMS, and flows. Any campaigns that failed during this time will need to be manually resent. We will continue to monitor system performance. Dec 22, 18:37 EST Update - We identified broader service disruption across the Klaviyo app between 5:55 pm and approximately 6:10 pm ET. While initial reports were limited to account switching, we have since confirmed additional impact to app availability and functionality. The underlying issue has been addressed, and the app is now available. Some customers may continue to experience intermittent issues as systems fully recover. We are actively monitoring. Dec 22, 17:37 EST Investigating - We are investigating reports of users unable to switch accounts once logged into Klaviyo

Read the full incident report →

Started Dec 18, 2025, 06:36 AM UTC· resolved Dec 18, 2025, 06:36 AM UTC

1. 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 →

Started Dec 17, 2025, 01:49 AM UTC· resolved Dec 17, 2025, 01:49 AM UTC

1. 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 →

Started Dec 05, 2025, 09:00 AM UTC· resolved Dec 05, 2025, 09:00 AM UTC

1. 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 →

Started Dec 03, 2025, 08:36 PM UTC· resolved Dec 03, 2025, 08:36 PM UTC

1. monitoring Dec 03, 2025, 08:36 PM UTC

   Dec 3, 15:36 EST Resolved - Monitoring is complete, and this incident has been resolved. We appreciate your patience throughout this incident. Dec 3, 15:21 EST Monitoring - We successfully reverted the change and have confirmed that Customer Agent Web Chat follow-up prompts are sending as expected. We will continue to monitor to ensure there is no further impact. Dec 3, 15:08 EST Identified - As of 3:00 PM US/Eastern, we confirmed this issue is only impacted Web Chat. Customer Agent via SMS chat is not impacted. We have identified a recent change as the root cause and will be reverting this shortly. We continue to monitor closely and appreciate your patience throughout this incident. Dec 3, 14:57 EST Investigating - We are currently investigating an issue impacting Customer Agent follow-up prompts beginning around 11:20 AM US/Eastern. Follow-up prompts are not appearing after replies from the AI Agent. This prevents end users from continuing the conversation or escalating to a human agent. We'll provide updates as more information is available.

Read the full incident report →

Started Nov 28, 2025, 10:05 PM UTC· resolved Nov 28, 2025, 10:05 PM UTC

1. 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 →

Started Nov 18, 2025, 07:06 PM UTC· resolved Nov 18, 2025, 07:06 PM UTC

1. 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 →

Started Nov 14, 2025, 10:00 PM UTC· resolved Nov 14, 2025, 10:00 PM UTC

1. 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 →

Started Nov 02, 2025, 05:41 PM UTC· resolved Nov 02, 2025, 05:41 PM UTC

1. 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 →

Started Oct 29, 2025, 07:43 PM UTC· resolved Oct 29, 2025, 07:43 PM UTC

1. monitoring Oct 29, 2025, 07:43 PM UTC

   Oct 29, 15:43 EDT Resolved - This incident has been resolved. Oct 29, 15:27 EDT Monitoring - We have mitigated the delays and we expect SMS event processing to be fully caught up within the next 20 minutes. There was no data loss as a result of this incident. Oct 29, 15:12 EDT Update - We are still working to restore normal processing of SMS events. A subset of customers may see delays of up to 90 minutes at this time. SMS Sending remains unaffected. Oct 29, 14:27 EDT Update - We want to acknowledge that downstream services (Segments and Flows) relying on the SMS events will also be impacted, until the event processing has caught up, which we expect to happen shortly. We'll continue to provide updates as they are available. Oct 29, 14:16 EDT Identified - Starting at 1:00 PM US/Eastern, we began experiencing delays of up to 40 minutes for SMS events processing. SMS Sending is not impacted. We have identified the issue and are in the process of reverting a change to restore normal processing. We'll provide updates as soon as more information is available.

Read the full incident report →

Started Oct 24, 2025, 12:23 AM UTC· resolved Oct 24, 2025, 12:23 AM UTC

1. monitoring Oct 24, 2025, 12:23 AM UTC

   Oct 23, 20:23 EDT Resolved - 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 →

Started Oct 21, 2025, 05:06 PM UTC· resolved Oct 21, 2025, 05:06 PM UTC

1. monitoring Oct 21, 2025, 05:06 PM UTC

   Oct 21, 13:06 EDT Resolved - All services have been restored and are operating normally. Monitoring is complete, and this incident has been resolved. We appreciate your patience throughout this incident. Oct 20, 20:31 EDT Update - As of 7:32pm EST, we have successfully processed the delayed unsubscribe events and conversion attribution analytics has been restored. We continue to monitor service functionality as repairs have been completed. Oct 20, 16:45 EDT Update - Flow sending is fully caught up and restored to real-time. We continue to process delayed conversion attribution analytics and delayed profile unsubscribes. Oct 20, 16:21 EDT Monitoring - Segmentation processing has been restored to real-time. Segments relying on custom object properties remain delayed and we're continuing to restore normal processing for these. We expect flow sending to be fully caught up within the next hour. We continue to process delayed conversion attribution analytics and delayed profile unsubscribes. Oct 20, 14:55 EDT Identified - A mitigation has been deployed for the issue impacting flow sending. Any delayed messages are now being replayed and flow performance is improving. We will confirm once this has been fully restored. The team continues to work through the segmentation processing delays. We continue to monitor closely and appreciate your patience throughout this incident. Oct 20, 13:37 EDT Update - We are currently experiencing delays in segmentation processing for a subset of users by up to 2.5 hours. We’re working to mitigate these processing delays as quickly as possible. Oct 20, 12:46 EDT Investigating - We are currently investigating an issue impacting flow sending beginning around 12:00 PM US/Eastern. We’ll provide updates as soon as more information is available. Oct 20, 11:26 EDT Update - Segmentation processing has been restored. We continue to work through processing for the delayed analytics and unsubscribes. Oct 20, 11:09 EDT Update - We continue to process delayed conversion attribution analytics and delayed profile unsubscribes. We are currently experiencing delays in segmentation processing for a subset of users by up to 60 minutes. We’re working to mitigate these processing delays as quickly as possible. Oct 20, 08:39 EDT Update - As of 8:30am EST, we have successfully sent the delayed campaign and flow messages. Over the next several hours, we will process delayed conversion attribution analytics and delayed profile unsubscribes. We continue to closely monitor our systems. Oct 20, 06:41 EDT Update - As of 6:15am EST, we are continuing to stabilize our systems and process any actions that were affected by the provider outage, which lasted from approximately 2:50 to 5:30am EST. We are attempting to send any campaigns and flows messages that couldn't be sent during that time. We are also processing events and profile information received during that time. Data from API requests that received an error during the incident were lost. We will continue to share updates as we make progress. Oct 20, 05:58 EDT Monitoring - As of 5:30am EST, the ability to log in and access the Klaviyo app has been restored. Restoration of all functionality and services is in progress. We are actively investigating the state of sending (campaigns, flows). We will continue to monitor services as functionality is repaired and will share updates as we make progress. Oct 20, 04:58 EDT Investigating - Starting around 2:50am EST, due to outages with an upstream provider, several services in Klaviyo including log-in and sending are inaccessible. We'll provide updates as soon as more information is available.

Read the full incident report →

Started Oct 02, 2025, 05:43 PM UTC· resolved Oct 02, 2025, 05:59 PM UTC

1. monitoring Oct 02, 2025, 05:43 PM UTC

   From 1:17 PM to 1:32 PM US/Eastern on 10/2/25, we experienced an issue that resulted in errors accessing the Klaviyo app, disruption in event ingestion, and issues submitting signup forms. A fix has been deployed and system performance is improving. We continue to monitor closely and appreciate your patience throughout this incident.

2. resolved Oct 02, 2025, 05:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 01, 2025, 02:16 AM UTC· resolved Oct 01, 2025, 02:31 AM UTC

1. monitoring Oct 01, 2025, 02:16 AM UTC

   We are currently monitoring an issue that was impacting subscribe and unsubscribe pages for all profiles. This may have prevented profiles from opting in or out of marketing communications. We'll provide updates as soon as more information is available.

2. resolved Oct 01, 2025, 02:31 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 19, 2025, 02:38 PM UTC· resolved Sep 19, 2025, 08:24 PM UTC

1. identified Sep 19, 2025, 02:38 PM UTC

   At around 7 AM Eastern time, we began experiencing delays in real-time event processing. Events may be out of date by up to 3 hours. Flows, Segments, Profiles, Reporting, as well as segment-targeted forms, may be impacted. We are actively working to restore real-time processing and will continue to provide updates here.

2. identified Sep 19, 2025, 05:07 PM UTC

   A fix has been implemented and we are monitoring the results. We expect real time event processing to be fully restored within 1 hour.

3. monitoring Sep 19, 2025, 06:42 PM UTC

   Event processing has been restored to real-time. There was no data loss as a result of this incident. We’re continuing to monitor and will post another update once we have fully cleared any backlog of processing data.

4. resolved Sep 19, 2025, 08:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 19, 2025, 01:38 PM UTC· resolved Sep 29, 2025, 01:27 PM UTC

1. investigating Sep 19, 2025, 01:38 PM UTC

   We are currently investigating an issue where a subset of scheduled and draft campaigns may not be appearing in the campaign list view as expected. We are actively investigating. We’ll provide updates as soon as more information is available.

2. identified Sep 19, 2025, 09:50 PM UTC

   We're continuing to work through repairs for this subset of campaigns. We'll provide updates as soon as more information is available. We appreciate your patience throughout this incident.

3. monitoring Sep 22, 2025, 07:43 PM UTC

   We have concluded our repairs and these campaigns should now show in the campaign list view as expected. We continue to monitor closely and appreciate your patience throughout this incident.

4. resolved Sep 29, 2025, 01:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2025, 09:05 PM UTC· resolved Sep 16, 2025, 09:21 PM UTC

1. identified Sep 16, 2025, 09:05 PM UTC

   Starting 3:50pm US/Eastern on 9/16/25, we began observing delays in event-triggered flows. Users may see delays of up to 60 minutes. We're currently working on a fix. We’ll provide updates as soon as more information is available.

2. monitoring Sep 16, 2025, 09:17 PM UTC

   A fix has been deployed and system performance is improving. We continue to monitor closely and appreciate your patience throughout this incident.

3. resolved Sep 16, 2025, 09:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 03, 2025, 09:32 PM UTC· resolved Sep 03, 2025, 10:56 PM UTC

1. investigating Sep 03, 2025, 09:32 PM UTC

   We are currently investigating an issue where omnichannel campaigns were resent unexpectedly. We'll provide updates as soon as more information is available.

2. monitoring Sep 03, 2025, 10:41 PM UTC

   We have identified the root cause and have mitigated any further incorrect resends of omnichannel campaigns. We continue to monitor closely and appreciate your patience throughout this incident.

3. resolved Sep 03, 2025, 10:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 12, 2025, 04:39 PM UTC· resolved Aug 12, 2025, 05:14 PM UTC

1. investigating Aug 12, 2025, 04:39 PM UTC

   We are currently investigating delays in the triggering of event-based flows, which began around 08/12/2025 at 11:45 US/Eastern. Our team is actively working to resolve the issue. Further updates will be provided as soon as new information is available.

2. monitoring Aug 12, 2025, 05:05 PM UTC

   Triggering of event-based flows is now back to real-time. We're continuing to monitor and will provide an additional confirmation of full recovery.

3. resolved Aug 12, 2025, 05:14 PM UTC

   This is now resolved, triggering is back to real-time.

Read the full incident report →

Started Jul 08, 2025, 07:20 PM UTC· resolved Jul 08, 2025, 07:50 PM UTC

1. investigating Jul 08, 2025, 07:20 PM UTC

   We are currently experiencing delays in event processing. Customers may see delays in event data syncing, event-triggered flows sending, and real-time segmentation. We are in the process of restoring normal operations and will continue to provide updates here.

2. monitoring Jul 08, 2025, 07:44 PM UTC

   We have mitigated the delays and event-processing has been restored to real-time. There was no data loss as a result of this incident. We’re continuing to monitor and will post another update once we have fully cleared any backlog of processing data.

3. resolved Jul 08, 2025, 07:50 PM UTC

   Event processing has been fully restored. This incident is now resolved.

Read the full incident report →

Started Jul 02, 2025, 07:41 PM UTC· resolved Jul 03, 2025, 06:29 PM UTC

1. identified Jul 02, 2025, 07:41 PM UTC

   From 1:39-2:47PM US/Eastern on 7/2/25, Klaviyo users may have had duplicate flow messages sent to their profiles. Customers received the original message as expected, but may have received duplicate versions in the minutes to follow. Duplicate sending is no longer occurring. Our Engineering Team is investigating any downstream effects and will provide an update once we have more information.

2. identified Jul 02, 2025, 10:58 PM UTC

   We're continuing to work through repairs to billing as a result of the duplicate sends and will provide credits to the impacted accounts. We'll provide another update once we have more information to share.

3. resolved Jul 03, 2025, 06:29 PM UTC

   The team continues to work through the appropriate adjustments to billing as a result of these duplicate sends. We expect to follow up with impacted customers early next week with more information once this work has been completed.

Read the full incident report →

Started Jun 28, 2025, 01:50 PM UTC· resolved Jun 28, 2025, 03:58 PM UTC

1. investigating Jun 28, 2025, 01:50 PM UTC

   We are currently investigating a delay in event processing for email & mobile push related events such as delivered, open, and click events. The delay began at 2:00AM (US Eastern). Any email or push message reporting and segments based on email or push events will be outdated. Message sending is not impacted. We are working to resolve this delay in event processing.

2. identified Jun 28, 2025, 02:46 PM UTC

   We have addressed the underlying issue and have begun processing email message events. We expect to process all of the delayed events with no data loss. The team determined that push message events were not impacted.

3. resolved Jun 28, 2025, 03:58 PM UTC

   Email message events are now processing in real-time, and the team is replaying any dropped events.

Read the full incident report →