Optimove Outage History

Started Aug 07, 2026, 03:27 AM UTC· resolved Aug 07, 2026, 07:26 PM UTC

1. investigating Aug 07, 2026, 03:27 AM UTC

   On August 6, we experienced an internal issue affecting Email campaign execution. As a result, some campaigns scheduled during the affected timeframe were not executed as expected. Where possible, eligible affected campaigns were rerun. Campaigns with future recurring occurrences will continue according to their regular schedule. We apologize for the inconvenience caused.

2. investigating Aug 07, 2026, 03:28 AM UTC

   We are continuing to investigate this issue.

3. investigating Aug 07, 2026, 06:54 AM UTC

   Investigating - We have identified an issue affecting the execution of some Optimail campaigns on August 6 and August 7. Our teams are currently reviewing the affected campaigns and monitoring campaign execution while Engineering continues to investigate the issue. We will provide further updates as more information becomes available.

4. investigating Aug 07, 2026, 10:08 AM UTC

   We continue to investigate an issue affecting the execution of some Optimail campaigns on August 6 and August 7. Our teams are reviewing affected campaigns, rerunning eligible campaigns where possible, and closely monitoring campaign execution. We will provide further updates as more information becomes available.

5. identified Aug 07, 2026, 11:35 AM UTC

   Identified – We have identified the issue affecting some Optimail campaign executions in the EU region. Customers in the EU region are advised not to manually rerun affected campaigns at this time while our team deploys a fix. Our teams are actively working on remediation. Campaigns in the US region are not affected and can be retried as needed. We will provide an update once affected campaigns can be safely retried.

6. monitoring Aug 07, 2026, 11:49 AM UTC

   Monitoring – The fix has been completed, and Optimail campaigns in the EU region are now processing normally. Campaign execution retries in the EU are safe to resume. Our teams will continue monitoring campaign execution to ensure stability. Please feel free to rerun campaigns now.

7. resolved Aug 07, 2026, 07:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 19, 2026, 09:12 AM UTC· resolved Jul 19, 2026, 11:50 AM UTC

1. monitoring Jul 19, 2026, 09:12 AM UTC

   What's happening Meta (Facebook) is experiencing a service disruption. Because campaign delivery to this channels depends on Meta's APIs, some Optimove campaigns targeting Meta audiences are affected. How this may affect you - Campaigns sending to Meta may fail - Audience syncs to Meta Custom Audiences may stall or error out - Delivery reports and channel metrics for Meta may be delayed or incomplete Important: This is a Meta-side outage, not an Optimove platform issue. Campaigns on all other channels (email, SMS, push, web, and other integrations) are unaffected and running normally. What we're doing Monitoring Meta's status. We will confirm here when Meta service is restored and Meta-channel execution is back to normal.

2. resolved Jul 19, 2026, 11:50 AM UTC

   Meta services have recovered and campaign delivery to Facebook has resumed.

Read the full incident report →

Started Jul 08, 2026, 01:21 PM UTC· resolved Jul 08, 2026, 02:02 PM UTC

1. investigating Jul 08, 2026, 01:21 PM UTC

   We are currently experiencing errors leading to delays in Daily Batch. As a result, some campaigns may remain in a “Not Run” status. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option. https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period. https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run. To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

2. resolved Jul 08, 2026, 02:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 04, 2026, 12:15 PM UTC· resolved Jul 04, 2026, 06:43 PM UTC

1. investigating Jul 04, 2026, 12:15 PM UTC

   We are currently experiencing errors leading to delays in campaign execution. As a result, some campaigns may remain in a “Not Run” status. This typically occurs when the Batch Data Update is delayed and campaign execution starts later than scheduled, causing some campaigns to miss their designated run time. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option. https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period. https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run. To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

2. investigating Jul 04, 2026, 12:16 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 04, 2026, 01:58 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Jul 04, 2026, 06:36 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Jul 04, 2026, 06:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 06, 2026, 04:19 AM UTC· resolved Jun 06, 2026, 12:52 PM UTC

1. investigating Jun 06, 2026, 04:19 AM UTC

   We are currently experiencing errors leading to delays in the daily data update process for some instances. As a result, campaigns scheduled to run after the daily update may be delayed or may remain in a “Not Run” status. This issue affects only some instances using the impacted daily update workflow. Instances using other daily update workflows are not affected. This typically occurs when the daily data update process after the ETL phase is delayed or fails, preventing campaign execution from starting as scheduled and causing some campaigns to miss their designated run time. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option: https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period: https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1-2 hours, or sooner if new information becomes available.

2. monitoring Jun 06, 2026, 06:36 AM UTC

   A fix has been applied, and the affected daily data update process is now showing signs of recovery. We are currently re-initiating previously failed batch updates in a controlled manner to avoid creating additional load. Some customers may continue to experience delays while these updates are being processed. Next Steps: We are continuing to resume the affected batch update processes and monitor their successful completion. Next Update: We will provide another update within 1–2 hours, or sooner if normal operation is fully restored.

3. resolved Jun 06, 2026, 12:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 19, 2026, 01:06 PM UTC· resolved May 19, 2026, 02:37 PM UTC

1. monitoring May 19, 2026, 01:06 PM UTC

   We identified and resolved a service degradation in our EU environment that impacted some customers. During the affected window, Web SDK events delivery into the Triggered Campaigns path was disrupted, which delayed or prevented triggered campaigns from firing for the impacted accounts. Server-side events, as well as standard Web SDK events, were unaffected throughout the incident. IMPACT - Affected: Triggered Campaigns powered by Web SDK events in the EU region. - Not affected: Server-side event ingestion, scheduled campaigns, Standard Wed SDK Events - Customers may observe a temporary dip in Triggered Campaign volume corresponding to the affected window. ROOT CAUSE The disruption was caused by an infrastructure change deployed in our EU environment on May 18-19, which inadvertently affected the path used to deliver Web SDK events into the platform. NEXT STEPS - We are conducting an internal post-incident review to prevent recurrence. - We are reinforcing our pre-deployment validation for infrastructure changes that affect event ingestion paths. - Events that did not reach the platform during the incident window cannot be retroactively replayed; data captured via server-side integrations during this period is intact. NEED HELP? If you believe your account experienced impact beyond what is described above, please contact us at [email protected] We sincerely apologize for the disruption and appreciate your patience.

2. resolved May 19, 2026, 02:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2026, 06:56 PM UTC· resolved Apr 22, 2026, 07:34 PM UTC

1. investigating Apr 22, 2026, 06:56 PM UTC

   We are currently investigating reports of slow response times and intermittent errors when logging into the platform, and our engineering team is actively working to restore full service as quickly as possible.

2. identified Apr 22, 2026, 07:01 PM UTC

   Our authentication service is currently experiencing performance degradation that may result in slow response times or errors when accessing the site, and we are closely monitoring their progress toward a resolution.

3. monitoring Apr 22, 2026, 07:10 PM UTC

   The issues affecting our login service have been resolved, and we are now closely monitoring performance to ensure continued stability for all users.

4. resolved Apr 22, 2026, 07:34 PM UTC

   This incident has been resolved

Read the full incident report →

Started Apr 10, 2026, 08:41 AM UTC· resolved Apr 10, 2026, 10:24 AM UTC

1. investigating Apr 10, 2026, 08:41 AM UTC

   We are investigating an issue affecting the Campaign Builder, where some users may be unable to create campaigns. Our team is working to identify the root cause and restore normal functionality as quickly as possible.

2. identified Apr 10, 2026, 08:49 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Apr 10, 2026, 10:05 AM UTC

   A fix has been implemented for the issue affecting campaign creation in the Campaign Builder. We are monitoring the results to ensure stability.

4. monitoring Apr 10, 2026, 10:24 AM UTC

   Apr 10, 10:24 UTC Resolved - This incident has been resolved. Apr 10, 10:05 UTC Monitoring - A fix has been implemented for the issue affecting campaign creation in the Campaign Builder. We are monitoring the results to ensure stability. Apr 10, 08:49 UTC Identified - The issue has been identified and a fix is being implemented. Apr 10, 08:41 UTC Investigating - We are investigating an issue affecting the Campaign Builder, where some users may be unable to create campaigns. Our team is working to identify the root cause and restore normal functionality as quickly as possible.

5. resolved Apr 10, 2026, 10:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 07, 2026, 07:51 AM UTC· resolved Apr 07, 2026, 09:22 AM UTC

1. investigating Apr 07, 2026, 07:51 AM UTC

   We are currently investigating this issue.

2. identified Apr 07, 2026, 08:10 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Apr 07, 2026, 09:22 AM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Apr 07, 2026, 09:22 AM UTC

   Apr 7, 09:22 UTC Resolved - This incident has been resolved. Apr 7, 09:22 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 7, 08:10 UTC Identified - The issue has been identified and a fix is being implemented. Apr 7, 07:51 UTC Investigating - We are currently investigating this issue.

5. resolved Apr 07, 2026, 09:22 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 23, 2026, 03:05 PM UTC· resolved Mar 23, 2026, 04:46 PM UTC

1. identified Mar 23, 2026, 03:05 PM UTC

   We are currently experiencing an issue where the Target Group (TG) size cannot be calculated in the Target Group Configuration section. As a result, the "Show Size" functionality may return "N/A" or fail to load. This issue is limited to the UI display only. Target Group size is still calculated correctly during campaign execution, and campaigns are not impacted. Our team is actively investigating the issue and working toward a resolution.

2. monitoring Mar 23, 2026, 03:15 PM UTC

   We identified an issue affecting the Target Group Configuration section, where the "Show Size" functionality could return "N/A" or fail to load. We have rolled back a recent change, and service is improving. This issue is limited to the UI display only. Target Group size continues to be calculated correctly during campaign execution, and campaigns are not impacted. We are continuing to monitor the situation to ensure full resolution.

3. monitoring Mar 23, 2026, 04:46 PM UTC

   Mar 23, 16:46 UTC Resolved - We have confirmed that the issue affecting the Target Group Configuration section has been resolved, and the "Show Size" functionality is now operating normally. We will continue to monitor to ensure ongoing stability. Mar 23, 15:15 UTC Monitoring - We identified an issue affecting the Target Group Configuration section, where the "Show Size" functionality could return "N/A" or fail to load. We have rolled back a recent change, and service is improving. This issue is limited to the UI display only. Target Group size continues to be calculated correctly during campaign execution, and campaigns are not impacted. We are continuing to monitor the situation to ensure full resolution. Mar 23, 15:05 UTC Identified - We are currently experiencing an issue where the Target Group (TG) size cannot be calculated in the Target Group Configuration section. As a result, the "Show Size" functionality may return "N/A" or fail to load. This issue is limited to the UI display only. Target Group size is still calculated correctly during campaign execution, and campaigns are not impacted. Our team is actively investigating the issue and working toward a resolution.

4. resolved Mar 23, 2026, 04:46 PM UTC

   We have confirmed that the issue affecting the Target Group Configuration section has been resolved, and the "Show Size" functionality is now operating normally. We will continue to monitor to ensure ongoing stability.

Read the full incident report →

Started Mar 17, 2026, 12:49 PM UTC· resolved Mar 17, 2026, 02:55 PM UTC

1. identified Mar 17, 2026, 12:49 PM UTC

   We are currently experiencing an issue causing unexpected errors and delays in campaign execution. What we’re doing- Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Next update- We will provide an update within 1–2 hours, or sooner if there are any significant developments.

2. identified Mar 17, 2026, 01:37 PM UTC

   We have identified the source of the issue leading to delays in campaign execution - Mitigation is in progress. Our team is working to restore normal service and will provide another update soon.

3. monitoring Mar 17, 2026, 02:01 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Mar 17, 2026, 02:13 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Mar 17, 2026, 02:55 PM UTC

   This incident has been resolved.

6. monitoring Mar 17, 2026, 02:55 PM UTC

   Mar 17, 14:55 UTC Resolved - This incident has been resolved. Mar 17, 14:13 UTC Update - A fix has been implemented and we are monitoring the results. Mar 17, 14:01 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 17, 13:37 UTC Update - We have identified the source of the issue leading to delays in campaign execution - Mitigation is in progress. Our team is working to restore normal service and will provide another update soon. Mar 17, 12:49 UTC Identified - We are currently experiencing an issue causing unexpected errors and delays in campaign execution. What we’re doing- Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Next update- We will provide an update within 1–2 hours, or sooner if there are any significant developments.

Read the full incident report →

Started Mar 14, 2026, 09:02 AM UTC· resolved Mar 14, 2026, 10:10 AM UTC

1. investigating Mar 14, 2026, 09:02 AM UTC

   We are currently experiencing unexpected errors leading to delays in campaign execution. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

2. monitoring Mar 14, 2026, 10:10 AM UTC

   Mar 14, 10:10 UTC Resolved - This incident has been resolved. Mar 14, 09:02 UTC Investigating - We are currently experiencing unexpected errors leading to delays in campaign execution. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

3. resolved Mar 14, 2026, 10:10 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 03, 2026, 10:20 AM UTC· resolved Mar 03, 2026, 12:20 PM UTC

1. investigating Mar 03, 2026, 10:20 AM UTC

   We’re currently investigating an issue where emails sent to our Support inbox are not being processed as expected, which may delay ticket creation and responses. Workaround: Please submit your request via the Optimove Academy “Submit a request” form or use the in-app/help widget to reach our Support teams while we work to restore normal email processing.

2. investigating Mar 03, 2026, 10:21 AM UTC

   Note: Emails are being queued and will be processed once service is restored. Some response delays and potential SLA impact may occur.

3. identified Mar 03, 2026, 11:48 AM UTC

   We have identified the root cause of the issue affecting all Support email inboxes and are working with our service provider on remediation. We expect the issue to be resolved within the next 45 minutes. Emails remain queued and will be processed once service is fully restored. Some response delays and potential SLA impact may occur. For urgent matters, please continue using the Optimove Academy “Submit a request” form or the in-app /help widget. We will provide confirmation once the issue is fully resolved.

4. monitoring Mar 03, 2026, 12:20 PM UTC

   Mar 3, 12:20 UTC Resolved - The issue affecting all Support email inboxes has been resolved. Email processing has resumed, and queued messages are being processed. You may experience short-term delays as we work through the backlog. We do not expect further impact. Thank you for your patience. Mar 3, 11:48 UTC Identified - We have identified the root cause of the issue affecting all Support email inboxes and are working with our service provider on remediation. We expect the issue to be resolved within the next 45 minutes. Emails remain queued and will be processed once service is fully restored. Some response delays and potential SLA impact may occur. For urgent matters, please continue using the Optimove Academy “Submit a request” form or the in-app /help widget. We will provide confirmation once the issue is fully resolved. Mar 3, 10:21 UTC Update - Note: Emails are being queued and will be processed once service is restored. Some response delays and potential SLA impact may occur. Mar 3, 10:20 UTC Investigating - We’re currently investigating an issue where emails sent to our Support inbox are not being processed as expected, which may delay ticket creation and responses. Workaround: Please submit your request via the Optimove Academy “Submit a request” form or use the in-app/help widget to reach our Support teams while we work to restore normal email processing.

5. resolved Mar 03, 2026, 12:20 PM UTC

   The issue affecting all Support email inboxes has been resolved. Email processing has resumed, and queued messages are being processed. You may experience short-term delays as we work through the backlog. We do not expect further impact. Thank you for your patience.

Read the full incident report →

Started Feb 17, 2026, 10:18 AM UTC· resolved Feb 17, 2026, 10:28 PM UTC

1. investigating Feb 17, 2026, 10:18 AM UTC

   We are currently experiencing errors causing delays in campaign execution in the EU environment. Workaround: For time-sensitive campaigns, users may leverage the “Run Now” option in Mission Control. Accounts with Force Run enabled will process campaigns if the issue is resolved within the defined grace period. Our engineering team is actively investigating and working to restore normal processing.

2. identified Feb 17, 2026, 10:37 AM UTC

   We have identified the root cause of the campaign execution delays in the EU environment. Ou team is actively working to restore normal processing as quickly as possible. We will continue to provide updates as progress is made.

3. monitoring Feb 17, 2026, 12:26 PM UTC

   Campaign processing queues in the EU environment are decreasing and performance is gradually improving. We are continuing to investigate the root cause, including potential third-party dependencies, while closely monitoring the system. We will provide further updates as more information becomes available.

4. monitoring Feb 17, 2026, 02:42 PM UTC

   The issue affecting campaign execution in the EU environment has been resolved. Note: Some scheduled campaigns may remain in a “Not Run” status. This occurs when the batch data update is delayed and campaign execution starts later than scheduled, causing certain campaigns to miss their designated run time. Recovery Options: - For campaigns that remained in a “Not Run” status, users may leverage the “Run Now” option in Mission Control. - Accounts with Force Run enabled may have campaigns processed within the defined grace period. - Alternatively, you may reach out to our Support team if you require assistance running affected campaigns in bulk. We appreciate your patience and understanding.

5. monitoring Feb 17, 2026, 10:28 PM UTC

   Feb 17, 22:28 UTC Resolved - This incident has been resolved. Feb 17, 14:42 UTC Update - The issue affecting campaign execution in the EU environment has been resolved. Note: Some scheduled campaigns may remain in a “Not Run” status. This occurs when the batch data update is delayed and campaign execution starts later than scheduled, causing certain campaigns to miss their designated run time. Recovery Options: - For campaigns that remained in a “Not Run” status, users may leverage the “Run Now” option in Mission Control. - Accounts with Force Run enabled may have campaigns processed within the defined grace period. - Alternatively, you may reach out to our Support team if you require assistance running affected campaigns in bulk. We appreciate your patience and understanding. Feb 17, 12:26 UTC Monitoring - Campaign processing queues in the EU environment are decreasing and performance is gradually improving. We are continuing to investigate the root cause, including potential third-party dependencies, while closely monitoring the system. We will provide further updates as more information becomes available. Feb 17, 10:37 UTC Identified - We have identified the root cause of the campaign execution delays in the EU environment. Ou team is actively working to restore normal processing as quickly as possible. We will continue to provide updates as progress is made. Feb 17, 10:18 UTC Investigating - We are currently experiencing errors causing delays in campaign execution in the EU environment. Workaround: For time-sensitive campaigns, users may leverage the “Run Now” option in Mission Control. Accounts with Force Run enabled will process campaigns if the issue is resolved within the defined grace period. Our engineering team is actively investigating and working to restore normal processing.

6. resolved Feb 17, 2026, 10:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 24, 2026, 12:58 PM UTC· resolved Jan 24, 2026, 02:46 PM UTC

1. investigating Jan 24, 2026, 12:58 PM UTC

   We have identified an issue causing a small percentage of campaigns to fail during execution. Please note that the majority of campaigns are proceeding successfully. ​Our team is currently executing a manual rerun for the affected campaigns. However, this recovery process will take some time to complete and risks campaigns going into "Not Run" status. ​Recommendation: If you have a high-priority campaign that has failed, we recommend manually re-running it immediately via the user interface (using the "Play" button in the campaign status window) rather than waiting for the backend recovery.

2. identified Jan 24, 2026, 02:03 PM UTC

   We are addressing execution errors affecting a limited number of campaigns. Due to potential delays and a risk of "Not Run" statuses, we advise manually triggering any high-priority campaigns via the UI for immediate delivery.

3. monitoring Jan 24, 2026, 02:24 PM UTC

   Backend recovery is underway and systems are stable. However, to avoid further delays while the queue clears, we continue to advise manually re-running any critical campaigns via the UI.

4. monitoring Jan 24, 2026, 02:46 PM UTC

   Jan 24, 14:46 UTC Resolved - The issue is resolved and systems are fully operational. Please verify your campaign statuses and manually run any campaigns that remain in "Not Run" or "Failed" status directly from the site. Jan 24, 14:24 UTC Monitoring - Backend recovery is underway and systems are stable. However, to avoid further delays while the queue clears, we continue to advise manually re-running any critical campaigns via the UI. Jan 24, 14:03 UTC Identified - We are addressing execution errors affecting a limited number of campaigns. Due to potential delays and a risk of "Not Run" statuses, we advise manually triggering any high-priority campaigns via the UI for immediate delivery. Jan 24, 12:58 UTC Investigating - We have identified an issue causing a small percentage of campaigns to fail during execution. Please note that the majority of campaigns are proceeding successfully. ​Our team is currently executing a manual rerun for the affected campaigns. However, this recovery process will take some time to complete and risks campaigns going into "Not Run" status. ​Recommendation: If you have a high-priority campaign that has failed, we recommend manually re-running it immediately via the user interface (using the "Play" button in the campaign status window) rather than waiting for the backend recovery.

5. resolved Jan 24, 2026, 02:46 PM UTC

   The issue is resolved and systems are fully operational. Please verify your campaign statuses and manually run any campaigns that remain in "Not Run" or "Failed" status directly from the site.

Read the full incident report →

Started Jan 23, 2026, 02:43 AM UTC· resolved Jan 23, 2026, 02:04 PM UTC

1. investigating Jan 23, 2026, 02:43 AM UTC

   We are currently experiencing errors leading to delays in campaign execution. As a result, some campaigns may remain in a “Not Run” status. This typically occurs when the Batch Data Update is delayed and campaign execution starts later than scheduled, causing some campaigns to miss their designated run time. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option. https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period. https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run. To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

2. investigating Jan 23, 2026, 05:47 AM UTC

   We continue to experience delays in campaign execution impacting some customers, which may result in certain campaigns remaining in a “Not Run” status. Not all customers are affected. Our engineering team is actively continuing the investigation and working to stabilize execution. At this time, the behavior remains consistent with delayed batch processing causing some campaigns to miss their scheduled run window. What We’re Doing: Engineering remains engaged and focused on restoring normal execution as quickly as possible. We are closely monitoring the system and affected tenants. Recovery Options (unchanged): Manual Run: High-priority campaigns can be triggered manually using Run Now in Mission Control. Force Run: If enabled, campaigns will still deliver once the issue is resolved within the grace period. Next Update: We will provide another update within 1–2 hours, or sooner if there are any meaningful changes.

3. investigating Jan 23, 2026, 08:47 AM UTC

   We are continuing to experience delays in campaign execution, affecting a subset of customers. Some campaigns may remain in a “Not Run” status. Not all customers are impacted. Relevant engineering teams are actively investigating and working to stabilize execution. At this time, the behavior is consistent with delayed batch processing, which may cause certain campaigns to miss their scheduled run window. What We’re Doing: Engineering teams remain fully engaged and focused on restoring normal execution as quickly as possible. We are closely monitoring the system and the affected tenants. Recovery Options are unchanged from previous updates. Next Update: We will share another update within 1-2 hours, or sooner if there are any significant changes.

4. identified Jan 23, 2026, 09:16 AM UTC

   We have identified the root cause of the campaign execution failures. A fix has been developed and is now being prepared for rollout. We are beginning to run the campaign execution for the first batch of customers. Next Steps Our engineering team is rolling out the fix and monitoring its impact closely. We will provide confirmation once the rollout is complete and normal operation is restored. Next Update You can expect another update within 1-2 hours or sooner if the fix is fully validated. Recovery Options are unchanged from previous updates.

5. identified Jan 23, 2026, 11:24 AM UTC

   The fix has been developed and rolled out to the production environment. We are continuing to gradually proceed with the campaign execution processes for customers. Next Steps We will monitor the execution process for customers and continue gradually with batch updates. We will provide additional updates once normal operation is restored. Next Update You can expect another update within 1-2 hours or sooner if the fix is fully validated.

6. monitoring Jan 23, 2026, 01:04 PM UTC

   A fix for the campaign execution failures is rolled out across all environments. We are gradually resuming campaign execution processes for customers. Next Steps: We are continuing to resume execution processes and monitor their successful completion. We will provide additional updates once normal operation is restored. Next Update: Another update will be shared within 1-2 hours.

7. monitoring Jan 23, 2026, 02:04 PM UTC

   Jan 23, 14:04 UTC Resolved - The issue causing both campaign execution failures and delays has been fully resolved. During the incident, some campaigns may have remained in a Not Run status. This can occur when the Batch Data Update is delayed, and campaign execution begins later than scheduled, resulting in certain campaigns missing their designated run window. Force Run Behavior If your instance has Force Run enabled, affected campaigns may still be executed automatically as part of the batch process, provided the incident was resolved within the configured grace period. More details on Force Run can be found here: https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run To enable Force Run for your instance, please reach out to your Customer Success Manager. Current Status Campaign execution has stabilized, failure rates have returned to normal, and all systems are fully operational. 'Not Run' campaigns can be manually run by clicking on the 'Play' button in the relevant campaign status window. Jan 23, 13:04 UTC Monitoring - A fix for the campaign execution failures is rolled out across all environments. We are gradually resuming campaign execution processes for customers. Next Steps: We are continuing to resume execution processes and monitor their successful completion. We will provide additional updates once normal operation is restored. Next Update: Another update will be shared within 1-2 hours. Jan 23, 11:24 UTC Update - The fix has been developed and rolled out to the production environment. We are continuing to gradually proceed with the campaign execution processes for customers. Next Steps We will monitor the execution process for customers and continue gradually with batch updates. We will provide additional updates once normal operation is restored. Next Update You can expect another update within 1-2 hours or sooner if the fix is fully validated. Jan 23, 09:16 UTC Identified - We have identified the root cause of the campaign execution failures. A fix has been developed and is now being prepared for rollout. We are beginning to run the campaign execution for the first batch of customers. Next Steps Our engineering team is rolling out the fix and monitoring its impact closely. We will provide confirmation once the rollout is complete and normal operation is restored. Next Update You can expect another update within 1-2 hours or sooner if the fix is fully validated. Recovery Options are unchanged from previous updates. Jan 23, 08:47 UTC Update - We are continuing to experience delays in campaign execution, affecting a subset of customers. Some campaigns may remain in a “Not Run” status. Not all customers are impacted. Relevant engineering teams are actively investigating and working to stabilize execution. At this time, the behavior is consistent with delayed batch processing, which may cause certain campaigns to miss their scheduled run window. What We’re Doing: Engineering teams remain fully engaged and focused on restoring normal execution as quickly as possible. We are closely monitoring the system and the affected tenants. Recovery Options are unchanged from previous updates. Next Update: We will share another update within 1-2 hours, or sooner if there are any significant changes. Jan 23, 05:47 UTC Update - We continue to experience delays in campaign execution impacting some customers, which may result in certain campaigns remaining in a “Not Run” status. Not all customers are affected. Our engineering team is actively continuing the investigation and working to stabilize execution. At this time, the behavior remains consistent with delayed batch processing causing some campaigns to miss their scheduled run window. What We’re Doing: Engineering remains engaged and focused on restoring normal execution as quickly as possible. We are closely monitoring the system and affected tenants. Recovery Options (unchanged): Manual Run: High-priority campaigns can be triggered manually using Run Now in Mission Control. Force Run: If enabled, campaigns will still deliver once the issue is resolved within the grace period. Next Update: We will provide another update within 1–2 hours, or sooner if there are any meaningful changes. Jan 23, 02:43 UTC Investigating - We are currently experiencing errors leading to delays in campaign execution. As a result, some campaigns may remain in a “Not Run” status. This typically occurs when the Batch Data Update is delayed and campaign execution starts later than scheduled, causing some campaigns to miss their designated run time. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option. https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period. https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run. To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

8. resolved Jan 23, 2026, 02:04 PM UTC

   The issue causing both campaign execution failures and delays has been fully resolved. During the incident, some campaigns may have remained in a Not Run status. This can occur when the Batch Data Update is delayed, and campaign execution begins later than scheduled, resulting in certain campaigns missing their designated run window. Force Run Behavior If your instance has Force Run enabled, affected campaigns may still be executed automatically as part of the batch process, provided the incident was resolved within the configured grace period. More details on Force Run can be found here: https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run To enable Force Run for your instance, please reach out to your Customer Success Manager. Current Status Campaign execution has stabilized, failure rates have returned to normal, and all systems are fully operational. 'Not Run' campaigns can be manually run by clicking on the 'Play' button in the relevant campaign status window.

Read the full incident report →

Started Jan 21, 2026, 07:04 PM UTC· resolved Jan 22, 2026, 09:12 AM UTC

1. investigating Jan 21, 2026, 07:04 PM UTC

   We are seeing degraded performance affecting the Real Time Track and Trigger component in the USA region. This can result in delays or slower processing of real-time events and may impact US Track and Trigger campaigns.

2. investigating Jan 21, 2026, 07:58 PM UTC

   We are continuing to work on stabilizing the system. At this time, the service remains in a degraded state, and while mitigation efforts are ongoing, the root cause has not yet been identified. Our teams are actively investigating and will provide further updates as soon as more information becomes available.

3. monitoring Jan 21, 2026, 08:48 PM UTC

   Our teams are investigating the issue and have identified conditions that affected system stability. We are actively working to restore normal operation and have placed the service under close monitoring to ensure continued stability. Additional updates will follow.

4. monitoring Jan 22, 2026, 09:12 AM UTC

   Jan 22, 09:12 UTC Resolved - This incident has been resolved. Jan 21, 20:48 UTC Monitoring - Our teams are investigating the issue and have identified conditions that affected system stability. We are actively working to restore normal operation and have placed the service under close monitoring to ensure continued stability. Additional updates will follow. Jan 21, 19:58 UTC Update - We are continuing to work on stabilizing the system. At this time, the service remains in a degraded state, and while mitigation efforts are ongoing, the root cause has not yet been identified. Our teams are actively investigating and will provide further updates as soon as more information becomes available. Jan 21, 19:04 UTC Investigating - We are seeing degraded performance affecting the Real Time Track and Trigger component in the USA region. This can result in delays or slower processing of real-time events and may impact US Track and Trigger campaigns.

5. resolved Jan 22, 2026, 09:12 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 20, 2026, 08:06 AM UTC· resolved Jan 20, 2026, 01:22 PM UTC

1. investigating Jan 20, 2026, 08:06 AM UTC

   We’re investigating an issue impacting OptiText SMS message sending/delivery. Our team is working to identify the cause and restore normal service.

2. identified Jan 20, 2026, 09:35 AM UTC

   We’ve identified an issue impacting OptiText SMS message sending/delivery related to a change made by an external SMS provider. We’re working closely with the provider to restore normal service.

3. monitoring Jan 20, 2026, 12:19 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Jan 20, 2026, 01:22 PM UTC

   Jan 20, 13:22 UTC Resolved - This incident has been resolved. Jan 20, 12:19 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan 20, 09:35 UTC Identified - We’ve identified an issue impacting OptiText SMS message sending/delivery related to a change made by an external SMS provider. We’re working closely with the provider to restore normal service. Jan 20, 08:06 UTC Investigating - We’re investigating an issue impacting OptiText SMS message sending/delivery. Our team is working to identify the cause and restore normal service.

5. resolved Jan 20, 2026, 01:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 07, 2026, 11:04 AM UTC· resolved Jan 07, 2026, 01:36 PM UTC

1. investigating Jan 07, 2026, 11:04 AM UTC

   We are investigating delays in the Batch Update process affecting some EU tenants. As a result, scheduled campaigns may execute later than their configured time. Campaign execution will resume automatically once batch processing completes.

2. identified Jan 07, 2026, 12:02 PM UTC

   The issue causing delays in batch processing in the EU region has been identified. Scheduled campaign executions, batch processing, and report generation may continue to be delayed for EU customers while remediation is in progress. Our teams are actively working to resolve the issue and will provide further updates as progress continues.

3. monitoring Jan 07, 2026, 12:55 PM UTC

   Mitigation has been applied and batch processing in the EU region is beginning to recover. Scheduled campaign executions, batch processing, and report generation may still experience delays as the system stabilizes. We are continuing to monitor the situation closely and will provide a final update once resolved.

4. monitoring Jan 07, 2026, 01:36 PM UTC

   Jan 7, 13:36 UTC Resolved - Batch processing in the EU region has returned to normal operation. Scheduled campaign executions, batch processing, and report generation are no longer experiencing delays. Campaigns that were marked as “Not Run” during the delay window will not execute automatically. Customers can identify affected campaigns via Mission Control in the Optimove platform and take action as needed, such as re-running or re-scheduling the campaign. We will continue to monitor the system to ensure stability. Jan 7, 12:55 UTC Monitoring - Mitigation has been applied and batch processing in the EU region is beginning to recover. Scheduled campaign executions, batch processing, and report generation may still experience delays as the system stabilizes. We are continuing to monitor the situation closely and will provide a final update once resolved. Jan 7, 12:02 UTC Identified - The issue causing delays in batch processing in the EU region has been identified. Scheduled campaign executions, batch processing, and report generation may continue to be delayed for EU customers while remediation is in progress. Our teams are actively working to resolve the issue and will provide further updates as progress continues. Jan 7, 11:04 UTC Investigating - We are investigating delays in the Batch Update process affecting some EU tenants. As a result, scheduled campaigns may execute later than their configured time. Campaign execution will resume automatically once batch processing completes.

5. resolved Jan 07, 2026, 01:36 PM UTC

   Batch processing in the EU region has returned to normal operation. Scheduled campaign executions, batch processing, and report generation are no longer experiencing delays. Campaigns that were marked as “Not Run” during the delay window will not execute automatically. Customers can identify affected campaigns via Mission Control in the Optimove platform and take action as needed, such as re-running or re-scheduling the campaign. We will continue to monitor the system to ensure stability.

Read the full incident report →

Started Jan 05, 2026, 12:57 PM UTC· resolved Jan 05, 2026, 05:25 PM UTC

1. investigating Jan 05, 2026, 12:57 PM UTC

   We are investigating delays in the Batch Update process affecting some EU tenants. As a result, scheduled campaigns may execute later than their configured time. Campaign execution will resume automatically once batch processing completes.

2. monitoring Jan 05, 2026, 01:39 PM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Jan 05, 2026, 05:25 PM UTC

   Jan 5, 17:25 UTC Resolved - This incident has been resolved. Jan 5, 13:39 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan 5, 12:57 UTC Investigating - We are investigating delays in the Batch Update process affecting some EU tenants. As a result, scheduled campaigns may execute later than their configured time. Campaign execution will resume automatically once batch processing completes.

4. resolved Jan 05, 2026, 05:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 30, 2025, 10:06 AM UTC· resolved Dec 30, 2025, 02:30 PM UTC

1. investigating Dec 30, 2025, 10:06 AM UTC

   We are investigating an issue impacting scheduled campaign execution in both EU and US regions. Campaigns using Conditional Execution, Re-evaluate Target Group, or “Run Now” may be delayed and may remain in “Processing” or appear as “Failed” / “Not Run”. This may impact deliveries via Optimove native channels (e.g., Optimail, Optimobile, OptiText). We are working to restore normal processing.

2. monitoring Dec 30, 2025, 10:41 AM UTC

   A fix has been applied and scheduled campaign batches are progressing, though some delays have already occurred. We are still seeing issues impacting campaigns using Conditional Execution, Re-evaluate Target Group, and “Run Now”, which may continue to appear as delayed or show “Failed” / “Not Run” status. We are monitoring closely and continuing to work toward full resolution.

3. monitoring Dec 30, 2025, 11:20 AM UTC

   We continue to monitor recovery. Some delays may still be observed for campaigns using Conditional Execution, Re-evaluate Target Group, and “Run Now”. For campaigns showing a “Not Run” status, re-running the campaign from the Optimove platform is available.

4. monitoring Dec 30, 2025, 12:34 PM UTC

   We continue to monitor recovery. While batch processing remains active, we are still observing additional issues that may impact campaigns using Conditional Execution, Re-evaluate Target Group, and “Run Now”. Some delays or “Failed” / “Not Run” statuses may still occur. Further updates will be shared as progress continues.

5. monitoring Dec 30, 2025, 12:43 PM UTC

   We observed degradation impacting scheduled campaign execution and have rolled out an additional fix. Campaign processing is ongoing, and some delays or “Failed” / “Not Run” statuses may still be observed for campaigns using Conditional Execution, Re-evaluate Target Group, and “Run Now”. We are closely monitoring recovery.

6. monitoring Dec 30, 2025, 01:30 PM UTC

   Campaign batch processing is operating normally. We are still monitoring issues impacting campaigns using Conditional Execution, Re-evaluate Target Group, and “Run Now”, which may continue to experience delays or show “Failed” / “Not Run” status. Further updates will be provided as we continue to work toward full resolution.

7. resolved Dec 30, 2025, 02:30 PM UTC

   The issue impacting scheduled campaign execution has been resolved and systems are operating normally. Campaign batch processing and execution for Conditional Execution, Re-evaluate Target Group, and “Run Now” campaigns are now working as expected. Some campaigns that missed their execution window during the incident may still show a "Not Run" or "Failed" status. In these cases, customers can re-run the campaign from the Optimove platform to execute it.

Read the full incident report →

Started Dec 29, 2025, 10:20 AM UTC· resolved Dec 29, 2025, 11:44 AM UTC

1. investigating Dec 29, 2025, 10:20 AM UTC

   We are investigating an issue causing BI reports in the Optimove application to not reflect the latest data. Customers may see stale or missing updates across reporting views. Our team is working to restore normal report refresh behavior and will share updates as we learn more.

2. identified Dec 29, 2025, 11:09 AM UTC

   We’ve identified the issue causing BI reports in the Optimove application to not reflect the latest data. A fix is rolling out now, and we’ll provide another update as rollout progresses.

3. resolved Dec 29, 2025, 11:44 AM UTC

   The root cause has been fixed and BI reports are recovering. It may take up to 24 hours for all reports to fully update. If you need an expedited review, please contact [email protected].

Read the full incident report →

Started Dec 28, 2025, 08:59 AM UTC· resolved Dec 28, 2025, 12:05 PM UTC

1. investigating Dec 28, 2025, 08:59 AM UTC

   We are investigating an issue causing OptiMail metrics to be missing or not updating for some customers in both EU and US regions, starting Dec 26, 2025 14:02 UTC. This may impact Mission Control / OptiMail reporting visibility (e.g., recent campaign performance metrics). We are working to restore normal metrics processing and will provide updates as we learn more

2. monitoring Dec 28, 2025, 10:17 AM UTC

   A mitigation has been applied and OptiMail metrics processing has been restored for EU & US tenants. Some customers may still see missing or delayed metrics for the period while we assess recovery/backfill options and continue monitoring system stability

3. resolved Dec 28, 2025, 12:05 PM UTC

   OptiMail metrics processing has been restored for EU and US tenants. Metrics for the last ~24 hours are recovering and updating as expected. We are continuing work to reconcile the remaining missing/delayed metrics from the incident window.

Read the full incident report →

Started Dec 27, 2025, 09:01 AM UTC· resolved Dec 27, 2025, 10:11 AM UTC

1. investigating Dec 27, 2025, 09:01 AM UTC

   We are investigating delays in the Batch Update process affecting some EU tenants. As a result, scheduled campaigns may execute later than their configured time. Campaign execution will resume automatically once batch processing completes.

2. monitoring Dec 27, 2025, 09:14 AM UTC

   Mitigation has been applied and Batch Update processing is recovering. We are monitoring until processing times return to normal. Some residual campaign execution delays may still be observed during recovery.

3. resolved Dec 27, 2025, 10:11 AM UTC

   The issue causing campaign execution delays has been fully resolved. During the incident, some campaigns may have remained in a Not Run status. This can occur when the Batch Data Update is delayed and campaign execution begins later than scheduled, resulting in certain campaigns missing their designated run window. Force Run Behavior If your instance has Force Run enabled, affected campaigns may still be executed automatically as part of the batch process, provided the incident was resolved within the configured grace period. More details on Force Run can be found here: https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run To enable Force Run for your instance, please reach out to your Customer Success Manager. Current Status Campaign execution has stabilized, failure rates have returned to normal, and all systems are fully operational.

Read the full incident report →

Started Dec 21, 2025, 02:40 PM UTC· resolved Dec 21, 2025, 05:07 PM UTC

1. investigating Dec 21, 2025, 02:40 PM UTC

   We are currently experiencing errors leading to delays and failures in Facebook campaign execution. As a result, some campaigns may remain in a “Failed” status. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible.

2. monitoring Dec 21, 2025, 04:04 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Dec 21, 2025, 05:07 PM UTC

   This incident has been resolved.

Read the full incident report →