Optimove Outage History

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

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

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

Started Dec 14, 2025, 06:31 PM UTC· resolved Dec 14, 2025, 10:12 PM UTC

1. investigating Dec 14, 2025, 06:31 PM UTC

   Real-time trigger campaigns that rely on server-side events are currently not triggering as expected. In addition, web events are experiencing delays in updating customer attribute values. Investigation is ongoing to identify the exact cause and restore normal processing. This may result in: - Trigger-based campaigns not firing in real time - Delayed audience qualification - Lag in behavioral or attribute-driven personalization

2. identified Dec 14, 2025, 06:58 PM UTC

   We have identified the root cause of the delay in server-side event processing and are actively working on a fix. Real-time trigger campaigns using server-side events are still not triggering as expected, and web event attribute updates may continue to be delayed while remediation is in progress. We will provide another update once the fix is deployed or if there is a material change in system behavior.

3. monitoring Dec 14, 2025, 07:28 PM UTC

   A fix has been successfully rolled out, and we are seeing server-side processing queues steadily reducing. Real-time trigger campaigns and web event attribute updates are beginning to recover, though some delays may still be observed while the remaining backlog is processed. We are closely monitoring the system and will provide a further update once processing has fully returned to normal.

4. monitoring Dec 14, 2025, 08:02 PM UTC

   The fix remains in place, and server-side processing queues continue to reduce. However, delays are still being observed in real-time trigger campaigns using server-side events and in web event attribute updates. The team is actively monitoring processing rates and making adjustments to ensure a full return to normal performance. We will share another update once delays are fully resolved or if there is a significant change.

5. monitoring Dec 14, 2025, 08:52 PM UTC

   Events processing queues continue to reduce. However, some delays are still present in real-time trigger campaigns using server-side events and in web event attribute updates. We are actively monitoring the system to ensure processing returns to normal and will provide another update once delays are fully resolved

6. monitoring Dec 14, 2025, 09:59 PM UTC

   Server-side processing queues are almost back to normal levels. Some minor delays may still be observed in real-time trigger campaigns using server-side events and in web event attribute updates as the final backlog clears. We continue to monitor closely and will provide a confirmation once processing has fully stabilized.

7. resolved Dec 14, 2025, 10:12 PM UTC

   Real-time trigger campaigns using server-side events are triggering as expected, and web events are now updating customer attribute values in real time without delay. We will continue to monitor the system to ensure ongoing stability. No data loss was identified during this incident.

Read the full incident report →

Started Nov 26, 2025, 05:21 PM UTC· resolved Nov 26, 2025, 08:17 PM UTC

1. investigating Nov 26, 2025, 05:21 PM UTC

   Some customers are experiencing slow performance and loading issues when working in the Optimove app, particularly in Target Groups and Web & App Activity filters. This does not affect non-UI functions such as campaign execution.

2. identified Nov 26, 2025, 05:40 PM UTC

   Our engineering team may have identified the root cause of the degraded performance affecting Target Groups and the Web & App Activity filters. They are currently applying corrective steps to address the issue and restore standard functionality. We will share another update as soon as the fix is confirmed. I appreciate your patience while we continue working on this.

3. monitoring Nov 26, 2025, 06:59 PM UTC

   Our engineering team has completed the changes related to the suspected root cause, and we are already seeing improved performance across the affected areas. Target Groups and Web & App Activity filters are loading faster, and overall responsiveness has improved. We are continuing to monitor the system closely to ensure full stability. Another update will follow once everything is fully confirmed.

4. resolved Nov 26, 2025, 08:17 PM UTC

   This issue has been fully resolved. System performance has returned to normal. Target Groups, Web & App Activity filters, and Streams are all functioning as expected and loading quickly. Our engineering team has confirmed the fix, and monitoring shows stable performance across all previously affected areas. Thank you for your patience while we worked through this.

Read the full incident report →

Started Nov 18, 2025, 07:44 AM UTC· resolved Nov 19, 2025, 12:17 AM UTC

1. investigating Nov 18, 2025, 07:44 AM UTC

   We are currently experiencing errors leading to delays and failures in 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. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control as soon as this incident is resolve. 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 Optimove Recovery Run: You can reach out to our support team as [email protected] and ask that we re-run failed campaigns for you. Please reach out with your instance name and request that we recover your failed campaigns. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

2. investigating Nov 18, 2025, 08:39 AM UTC

   We are still seeing intermittent delays and failures in campaign execution. To avoid repeated failures, please refrain from re-running affected campaigns until the incident is fully resolved. Status: Engineering is actively testing fixes and working to restore stable execution. Recovery Options: Optimove Recovery Run: If needed, contact [email protected] with your instance name and request recovery of failed campaigns. Manual Run: Once stability is confirmed, high-priority campaigns can be re-run using the Run Now option in Mission Control. Next Update We will share another update within 1–2 hours, or sooner if we have significant progress.

3. identified Nov 18, 2025, 09:42 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. Current Guidance Please continue avoiding re-running failed campaigns until the fix is fully deployed and execution stability is confirmed. 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 hour or sooner if the fix is fully validated.

4. monitoring Nov 18, 2025, 10:28 AM UTC

   A fix for the campaign execution failures is now rolling out across all environments. Customer Guidance: You can safely re-run failed campaigns once your environment is updated to version 9.175.1. You can verify this in the About Details section of the application. If your version has not yet updated, please wait before re-running any failed campaigns. Next Steps: We will continue monitoring the rollout and execution stability as the update reaches all environments. Next Update: Another update will be shared within 1 hour or sooner once the rollout is complete.

5. resolved Nov 19, 2025, 08:29 AM 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.

Read the full incident report →

Started Nov 06, 2025, 01:37 PM UTC· resolved Nov 06, 2025, 02:50 PM UTC

1. investigating Nov 06, 2025, 01:37 PM UTC

   We’re investigating an issue causing Opti-X recommendations to intermittently not return results for some customers. We’ll share an update as soon as we know more.

2. identified Nov 06, 2025, 01:59 PM UTC

   We’ve identified the cause of an issue affecting Opti-X services following a recent deployment. As a result, recommendations, Smart Content, Smart Search, and Smart Campaigns may not be serving as expected for some customers. Our teams are working to restore full functionality - another update is due in in the next 15 minutes.

3. resolved Nov 06, 2025, 02:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2025, 10:10 AM UTC· resolved Nov 04, 2025, 02:26 PM UTC

1. investigating Nov 04, 2025, 10:10 AM UTC

   We’re currently investigating an issue causing delays in Web & App Activity data processing for some tenants. As a result, audiences that use web and app attributes may be temporarily affected. Other systems continue to operate normally.

2. identified Nov 04, 2025, 10:59 AM UTC

   We are working on a fix for an underlying infrastructure issue that is also causing delays in batch processing and campaign execution. Our team is actively addressing the problem and will provide another update as soon as more information becomes available.

3. identified Nov 04, 2025, 01:05 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Nov 04, 2025, 01:32 PM UTC

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

5. resolved Nov 04, 2025, 02:26 PM UTC

   The issue has been resolved and all services are operating normally. We will continue to monitor to ensure stability.

Read the full incident report →

Started Oct 27, 2025, 12:22 PM UTC· resolved Oct 27, 2025, 06:13 PM UTC

1. investigating Oct 27, 2025, 12:22 PM UTC

   We are currently investigating an issue that may cause delays in batch processing, as well as slower-than-usual performance in web and app activity. Our engineering team is actively working to resolve the issue as quickly as possible.

2. identified Oct 27, 2025, 01:17 PM UTC

   Description: We are aware of an issue causing delays in batch processing and slower-than-usual performance in web and app activity. The root cause has been identified as a disruption with a third-party vendor. Our team is working to resolve the issue, and we are monitoring the situation to ensure normal performance is restored as soon as possible. Impact: Some clients may experience delayed batch executions and intermittent updates for Web and App activity. Next Update: We will provide an update within the next hour or as soon as additional information becomes available. Thank you for your continued patience and understanding.

3. monitoring Oct 27, 2025, 01:39 PM UTC

   Description: Our team has implemented a fix, and we are monitoring the recovery of affected batch processes.

4. monitoring Oct 27, 2025, 03:35 PM UTC

   We are continuing to closely monitor the recovery of the affected batch processes. Our review has identified that certain campaigns configured with the “Run Anyway” option have entered a “Not Run” status. Should you wish for these campaigns to still execute today, they will need to be manually triggered from Mission Control. We appreciate your understanding as we work to ensure full restoration of normal processing.

5. resolved Oct 27, 2025, 06:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 09:29 AM UTC· resolved Oct 21, 2025, 07:26 AM UTC

1. investigating Oct 20, 2025, 09:29 AM UTC

   We're experiencing an elevated level of errors and are currently looking into the issue. Mobile Push, Web Push, WhatsApp, SMS, In-App messaging campaigns are impacted.

2. identified Oct 20, 2025, 09:41 AM UTC

   Errors are related to an AWS outage and it seems like AWS were able to recover some services - more update to follow. From AWS: Oct 20 2:27 AM PDT We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information.

3. monitoring Oct 20, 2025, 11:33 AM UTC

   Following an update from AWS we are monitoring the services covering. From AWS: Oct 20 3:35 AM PDT The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution. Additionally, some services are continuing to work through a backlog of events such as Cloudtrail and Lambda. While most operations are recovered, requests to launch new EC2 instances (or services that launch EC2 instances such as ECS) in the US-EAST-1 Region are still experiencing increased error rates. We continue to work toward full resolution. If you are still experiencing an issue resolving the DynamoDB service endpoints in US-EAST-1, we recommend flushing your DNS caches. We will provide an update by 4:15 AM, or sooner if we have additional information to share.

4. resolved Oct 21, 2025, 07:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 16, 2025, 04:49 PM UTC· resolved Oct 16, 2025, 05:17 PM UTC

1. investigating Oct 16, 2025, 04:49 PM UTC

   Some customers sending Optimail marketing campaigns may have experienced delays. Campaigns are sending now, and we’re continuing to monitor progress.

2. monitoring Oct 16, 2025, 04:59 PM UTC

   Our engineering team identified the root cause of the issue affecting Optimail campaign sending and implemented a fix. Affected campaigns are now being delivered, and we should no longer be experiencing delays. We will continue to monitor system performance.

3. resolved Oct 16, 2025, 05:17 PM UTC

   Our engineering team has confirmed that the issue affecting Optimail campaign sending has been fully resolved. All services are now operating normally, and campaign deliveries have returned to expected performance levels.

Read the full incident report →

Started Oct 07, 2025, 09:34 AM UTC· resolved Oct 07, 2025, 05:29 PM UTC

1. investigating Oct 07, 2025, 09:34 AM UTC

   We are currently investigating an issue affecting the Optimove site. Multiple pages that are related to Target Groups have a long loading time for some tenants. Affected pages: Manage Target Groups / Target Group Discovery / Customer Explorer This incident is limited to UI and site functionality. Campaign execution, daily processes, and API access remain fully functional and unaffected. We will provide updates as we learn more.

2. identified Oct 07, 2025, 12:23 PM UTC

   We identified the root cause for the extended opening time for Target Group-related pages in Optimove UI. We are currently working on mitigating the cause of the issue with top priority. More updates will be provided as we learn more.

3. monitoring Oct 07, 2025, 01:28 PM UTC

   We have implemented a fix for the issue and are observing much faster loading times of Target Group-related pages in Optimove UI. Campaign execution, batch update processes, and API access remain fully functional and unaffected. We will continue to monitor the situation closely and provide a final update once the incident is fully resolved.

4. resolved Oct 07, 2025, 05:29 PM UTC

   The issue affecting loading time for Target Group-related pages has been resolved. Functionality is now working as expected. Campaign execution, daily processes, and API access remained fully functional and unaffected throughout the incident. Thank you for your patience while our teams investigated and monitored this incident.

Read the full incident report →

Started Sep 11, 2025, 09:36 AM UTC· resolved Sep 11, 2025, 10:52 AM UTC

1. investigating Sep 11, 2025, 09:36 AM UTC

   We are investigating an issue affecting the Optimove site where Mission control and Campaign Builder pages not loading. This incident is limited to UI and site functionality Daily process, Campaign execution and API access is fully functional and unaffected

2. investigating Sep 11, 2025, 09:40 AM UTC

   We are continuing to investigate this issue.

3. identified Sep 11, 2025, 10:21 AM UTC

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

4. monitoring Sep 11, 2025, 10:31 AM UTC

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

5. resolved Sep 11, 2025, 10:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2025, 09:49 AM UTC· resolved Sep 01, 2025, 10:56 AM UTC

1. investigating Sep 01, 2025, 09:49 AM UTC

   We are currently investigating an issue affecting the Optimove site. Target Group details and lists are not loading for some tenants. This incident is limited to UI and site functionality. Campaign execution, daily processes, and API access remain fully functional and unaffected. We will provide updates as we learn more.

2. identified Sep 01, 2025, 10:04 AM UTC

   We have identified the root cause of the issue affecting Target Group details and lists for some tenants. Our teams are taking corrective action to restore full functionality. Campaign execution, daily processes, and API access remain fully functional and unaffected. We will continue to share updates as remediation progresses.

3. monitoring Sep 01, 2025, 10:41 AM UTC

   We are observing consistent recovery in the availability of Target Group details and lists for tenants that were previously affected. Error rates have dropped significantly, and functionality appears to be stable. Campaign execution, daily processes, and API access remain fully functional and unaffected. We will continue monitoring closely and provide a final update once the incident is fully resolved.

4. resolved Sep 01, 2025, 10:56 AM UTC

   The issue affecting Target Group details and lists for some tenants has been resolved. Functionality is now working as expected. Campaign execution, daily processes, and API access remained fully functional and unaffected throughout the incident. Thank you for your patience while our teams investigated and monitored this incident.

Read the full incident report →

Started Aug 25, 2025, 06:23 AM UTC· resolved Aug 25, 2025, 07:39 AM UTC

1. investigating Aug 25, 2025, 06:23 AM UTC

   We are currently investigating errors and unavailability affecting our SFTP service. The issue impacts file uploads and is holding back the batch process. Impact: Some tenants may experience delays in scheduled campaign execution dependent on the batch process. Workaround: For time-sensitive campaigns, you can use the Run Now option to execute campaigns with the latest available data in Optimove.

2. identified Aug 25, 2025, 06:50 AM UTC

   We have identified an issue impacting some incoming connections to our SFTP service, which is preventing certain clients from successfully uploading files. Impact: Some tenants may experience delays in file transfers and scheduled campaign execution dependent on the batch process. Workaround: For time-sensitive campaigns, you can use the Run Now option to execute campaigns with the latest available data in Optimove. Our team is working to restore full connectivity.

3. monitoring Aug 25, 2025, 07:05 AM UTC

   We have implemented a fix for the issue affecting incoming connections to our SFTP service, and clients are now able to upload files successfully. Next steps: Please re-upload any files that may have failed earlier today to ensure they are processed. We are closely monitoring the service to confirm full stability.

4. resolved Aug 25, 2025, 07:39 AM UTC

   The issue affecting incoming connections to our SFTP service has been fully resolved. Clients can now upload files successfully, and the batch process is running as expected. Action required: Impacted tenants should re-upload any files that may have failed earlier today to ensure they are processed.

Read the full incident report →

Started Jul 30, 2025, 11:52 AM UTC· resolved Aug 01, 2025, 11:47 AM UTC

1. identified Jul 30, 2025, 11:52 AM UTC

   We are working to resolve an issue affecting access to Opti-x for some Optimove core provisioned users.

2. monitoring Jul 31, 2025, 09:49 AM UTC

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

3. resolved Aug 03, 2025, 11:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 13, 2025, 07:24 AM UTC· resolved Jun 13, 2025, 08:21 AM UTC

1. investigating Jun 13, 2025, 07:24 AM UTC

   We received reports of increased issues with some Optimal templates with the visual editor, and will continue investigating the issue. This does not impact existing campaign execution and only limits template edits and creation via the visual editor.

2. monitoring Jun 13, 2025, 08:00 AM UTC

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

3. resolved Jun 13, 2025, 08:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:30 PM UTC· resolved Jun 13, 2025, 01:02 AM UTC

1. investigating Jun 12, 2025, 06:30 PM UTC

   We are currently investigating an issue where some users are unable to log in. Our team is actively working to identify the cause and implement a fix. We will share more updates as they become available. Thank you for your patience.

2. investigating Jun 12, 2025, 06:37 PM UTC

   We are currently investigating an issue where some users are unable to log in. In parallel, we are also observing disruptions affecting external infrastructure providers, which may be contributing to broader service instability. Our team is actively working to assess the impact and will provide updates as soon as more information becomes available. Thank you for your continued patience.

3. investigating Jun 12, 2025, 06:45 PM UTC

   We have identified that the ongoing service disruptions are linked to a major outage affecting a global cloud infrastructure provider. This issue is impacting multiple services across the internet and is contributing to login failures and degraded performance in our application. We are closely monitoring the situation and are in contact with the affected provider. At this time, there is no workaround, but we will continue to provide timely updates as new information becomes available. We appreciate your patience and understanding as this industry-wide incident is being addressed.

4. monitoring Jun 12, 2025, 07:01 PM UTC

   We are beginning to observe signs of recovery following the earlier outage affecting Google Cloud Platform (GCP), which caused widespread disruption across many online services. Impacted services, including user login and application performance, are gradually returning to normal across multiple regions. Our team continues to actively monitor system health and remains in close contact with GCP to ensure full restoration and stability. We will keep this page updated with the latest status.

5. monitoring Jun 12, 2025, 07:09 PM UTC

   We are continuing to monitor for any further issues.

6. monitoring Jun 12, 2025, 07:17 PM UTC

   We continue to observe steady recovery across our services following the earlier disruption caused by a Google Cloud Platform (GCP) issue. This incident impacted multiple GCP products globally, leading to service interruptions for numerous online platforms. Google has confirmed that the issue is recovering in some locations and continues to work towards full mitigation. Our engineering teams closely monitor system performance to ensure full restoration and stability. We will provide further updates as more information becomes available.

7. monitoring Jun 12, 2025, 07:42 PM UTC

   We continue to monitor the recovery from the earlier Google Cloud Platform (GCP) service disruption. As per GCP's latest update, most locations have fully recovered. There is no estimated time of full recovery at this time. We are closely monitoring the situation and will provide further updates as more information becomes available.

8. monitoring Jun 12, 2025, 08:20 PM UTC

   Our engineering teams are fully engaged in restoring services impacted by the current Google Cloud Platform (GCP) disruption. We are observing continued recovery across services, We will provide the next update within 20 minutes.

9. monitoring Jun 12, 2025, 08:37 PM UTC

   We are seeing continued recovery across all regions. Most services are stabilizing, and remaining issues are progressively resolving. Our team remains focused on ensuring full restoration and will share further updates as needed.

10. monitoring Jun 12, 2025, 09:14 PM UTC

    Our monitoring indicates that services continue to recover steadily. At this time, no new issues have been identified, and system performance is stabilizing across all regions. According to the latest update from Google Cloud Platform (GCP), mitigation has been implemented for the issue in all regions, and GCP is observing signs of recovery. GCP expects full recovery to be completed within the next hour. We will continue to monitor the situation closely and provide another update as soon as more information becomes available.

11. monitoring Jun 12, 2025, 09:40 PM UTC

    All core services are currently operational, and we are no longer observing active issues. Recovery efforts following the earlier Google Cloud Platform (GCP) outage are progressing, including in the previously impacted us-central1 and multi-region/us regions. While system performance has stabilized, we remain in a heightened monitoring state to ensure full and sustained recovery across all components. We will continue to share updates as needed.

12. resolved Jun 13, 2025, 01:02 AM UTC

    The earlier disruption related to the Google Cloud Platform (GCP) outage has been mitigated, and all Optimove services are currently operational. However, full recovery is still in progress, particularly in processing pipelines and dependent third-party services. As a result, customers may experience delays in campaign execution and web and app activity processing while backlogs are being cleared. We are closely monitoring system performance and will continue working to ensure full stability across all components.

Read the full incident report →

Started Jun 08, 2025, 04:41 AM UTC· resolved Jun 08, 2025, 09:39 PM UTC

1. investigating Jun 08, 2025, 04:41 AM UTC

   We are investigating an increased error rate while accessing the Core Application and executing the Batch process.

2. investigating Jun 08, 2025, 05:57 AM UTC

   We are continuing to investigate this issue.

3. identified Jun 08, 2025, 06:21 AM UTC

   We are working with our infrastructure teams to recover services ASAP

4. identified Jun 08, 2025, 07:12 AM UTC

   Our teams are still on this incident - working to resolve connectivity issues

5. identified Jun 08, 2025, 09:56 AM UTC

   We are continuing to work on a fix for this issue.

6. identified Jun 08, 2025, 10:59 AM UTC

   Optimove is currently experiencing an issue with its optimove.net domain, which impacts our DNS records resolution. We are currently working to address the issue and will provide additional updates in the next hour. More updates in: https://optimovestatus.statuspage.io/

7. identified Jun 08, 2025, 12:15 PM UTC

   Optimove is currently experiencing a significant issue with the domain service for "optimove.net". As a result, clients may not be able log into the product or execute campaigns at this time. We are currently working to address the issue, and we anticipate that a resolution may take several hours. We will provide updates on the situation via our status page: https://optimovestatus.statuspage.io/.

8. identified Jun 08, 2025, 12:43 PM UTC

   We have identified a potential root cause related to DNS resolution failures and are currently validating it. If confirmed, we expect to implement a fix and begin the recovery process for batch and campaign execution services. We will share the next update within the hour. More updates to follow in: https://optimovestatus.statuspage.io/

9. identified Jun 08, 2025, 01:53 PM UTC

   We have made significant progress in addressing the DNS resolution issue. A fix is now being rolled out to restore service functionality. We expect to provide another update in the next 30 minutes.

10. monitoring Jun 08, 2025, 02:21 PM UTC

    A fix is rolling out, and site access functionality and API are being restored. Due to the outage Optimove experienced today, our SFTP service was unavailable, which may have impacted the upload of some files. Since daily batches depend on these files, we strongly recommend verifying that all files were uploaded correctly. This will help us ensure proper recovery and allow us to re-run the daily batch if necessary. We are actively monitoring the situation and are here to assist with any issues you may encounter. Thank you for your cooperation and understanding.

11. monitoring Jun 08, 2025, 02:53 PM UTC

    We are continuing to monitor for any further issues.

12. monitoring Jun 08, 2025, 03:28 PM UTC

    Services are recovering. Please note that the nature of DNS resolution and caching can sometimes cause delays as changes propagate across systems. This may take additional time before everything is fully restored. Thank you for your continued patience and understanding as we work to complete the recovery.

13. monitoring Jun 08, 2025, 04:30 PM UTC

    We are continuing to monitor for any further issues.

14. monitoring Jun 08, 2025, 06:50 PM UTC

    We are continuing to monitor for any further issues.

15. monitoring Jun 08, 2025, 08:02 PM UTC

    Further functionalities have been restored and are now back online. Our team continues to address the remaining issues to ensure full service restoration.

16. monitoring Jun 08, 2025, 08:40 PM UTC

    More services have been recovered and are now fully operational. We will continue to monitor and provide additional updates once resolved.

17. resolved Jun 08, 2025, 09:39 PM UTC

    The issue has been resolved, and all services are now operational. Recovery efforts are still ongoing, and we continue to monitor the service. We will provide any further updates as necessary. Additionally, a Root Cause Analysis (RCA) will be shared once the investigation is complete. Thank you for your patience and cooperation.

Read the full incident report →

Started May 14, 2025, 02:37 PM UTC· resolved May 14, 2025, 04:50 PM UTC

1. monitoring May 14, 2025, 02:37 PM UTC

   We are monitoring a fix released to address elevated errors in our Scheduled Campaign Execution. Some tenants will experience delays in scheduled campaign execution as part of the batch process.

2. resolved May 14, 2025, 04:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 14, 2025, 09:11 AM UTC· resolved May 14, 2025, 12:19 PM UTC

1. investigating May 14, 2025, 09:11 AM UTC

   We are investigating elevated errors in our batch update process. Specifically, we are facing an issue with the Data importing service on the optimove side. This is causing delays in batch data processing. Possible impact: Some tenants will experience up to 2 hours delays in scheduled campaign execution as part of the batch process.

2. identified May 14, 2025, 09:44 AM UTC

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

3. identified May 14, 2025, 10:34 AM UTC

   We are still working on a fix. Additional updates within 20 minutes.

4. identified May 14, 2025, 10:55 AM UTC

   The Fix is ready and is in testing stages - We expect a delivery ETA of 15 minutes that will allow our teams to restart the Batch process for impacted tenants.

5. monitoring May 14, 2025, 11:13 AM UTC

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

6. resolved May 14, 2025, 12:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 11, 2025, 12:30 PM UTC· resolved Apr 11, 2025, 03:10 PM UTC

1. resolved Apr 22, 2025, 10:15 AM UTC

   Opti-X Smart campaigns service encountered unexpected errors between April 11th 12:30PM UTC - April 21th 15:10 PM UTC. Note: Scheduled campaigns and normal triggered campaigns were not impacted - remained fully functional

Read the full incident report →

Started Apr 02, 2025, 08:36 PM UTC· resolved Apr 02, 2025, 09:43 PM UTC

1. investigating Apr 02, 2025, 08:36 PM UTC

   We are currently examining the elevated errors in campaign execution across multiple accounts and are investigating the issues being experienced.

2. identified Apr 02, 2025, 08:49 PM UTC

   We have identified the issue impacting a specific subset of accounts and are presently engaged in recovery efforts.

3. monitoring Apr 02, 2025, 09:01 PM UTC

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

4. monitoring Apr 02, 2025, 09:34 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Apr 02, 2025, 09:43 PM UTC

   The issue has been successfully resolved. However, we were unable to execute the campaign today for certain tenants who do not have the Force Run option enabled, and the scheduled time for the campaign has now passed. Should you wish to proceed with the campaign, please do not hesitate to initiate it at your convenience.

Read the full incident report →