Monitoring - A fix has been implemented and we are monitoring the results.
Oct 29, 2024 - 21:16 UTC
Update - A fix is ready and going through the testing cycle to make sure the UI incident is resolved
Oct 29, 2024 - 16:57 UTC
Update - We are continuing to work on a fix for this issue.
Oct 29, 2024 - 11:54 UTC
Identified - We identified the source of an issue affecting the Optimove site - exporting customer lists from the customer explorer leads to logging out of users. This incident is limited to UI and site functionality.
The Batch process, Campaign execution, and API access are fully functional and unaffected.
Oct 29, 2024 - 10:48 UTC
Investigating - We are investigating an issue affecting the Optimove site in exporting customer lists from the customer explorer. This incident is limited to UI and site functionality
The Batch process, Campaign execution, and API access are fully functional and unaffected
Oct 29, 2024 - 10:19 UTC
Effective November 18th, 2024, Optimove will discontinue support and sunset the service for API integrations utilizing the username and password login method as we shift to only support API Key authentication.
We recommend creating and implementing API Keys for all integrations by 1st October to ensure seamless functionality and support.
We are committed to maintaining the security and performance of our services. As part of this commitment, we are delivering updates to the security settings of our API to protect your data and ensure compliance with the latest industry standards.
What is happening? We will retire older, less secure encryption methods (called "ciphers") from our API. Starting January 6, 2025, these weak encryption methods will no longer be supported, and older versions of some client-side software may no longer be able to connect to our API.
What does this mean for you? To ensure you can continue using our services without interruption, please take the following steps before January 6, 2025: Update your software: Make sure you are using the latest version of your software or application that connects to our API. Most recent versions will already support the necessary security settings (encryption methods like AES-256 or TLS 1.2/1.3)
If your client-side application successfully establishes an SSL connection to the test URL, no further action is needed. If the test fails (SSL Handshake failure), please reach out to your software provider for assistance with updating or reconfiguring your client software.
Need help? If you have any questions or need assistance, please feel free to contact our support team at Support@Optimove.com. We’re here to help!
Thank you for your attention to this important update, and for your continued trust in our services. Posted on
Oct 07, 2024 - 08:49 UTC
Resolved -
This incident has been resolved.
Oct 27, 15:15 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Oct 27, 14:33 UTC
Update -
A fix is ready and being implemented with an ETA of 30 minutes for the next update
Oct 27, 14:23 UTC
Update -
Update: the root cause was identified as a networking issue in a managed service used by Optimove batch process. We are working with our hosting provider to implement a solution. More updates will follow.
Oct 27, 12:13 UTC
Update -
We are still working on a fix - no immediate ETA for resolution
Oct 27, 09:35 UTC
Identified -
The issue has been identified - we are working on a fix
Oct 27, 08:57 UTC
Investigating -
We are investigating elevated errors identified in our processing of the Batch Update Process leading to delays in campaign execution for some tenants.
Oct 27, 07:03 UTC
Resolved -
This incident has been resolved.
Oct 23, 09:06 UTC
Monitoring -
A fix has been implemented, and batch updates are back on track. Some tenants might experience a delay of ~45 minutes in the completion of the Campaign Execution phase of the Batch update
Oct 23, 08:21 UTC
Identified -
We identified and are working to fix elevated errors identified in our processing of the Batch Update Process leading to delays in campaign execution for some tenants.
Oct 23, 08:08 UTC
Resolved -
This incident has been resolved.
Oct 20, 14:12 UTC
Investigating -
We are investigating elevated errors in our processing of the campaign events notification (example: event type 1), which are leading to delays in campaign execution. This means delays in third-party API channels and conditional campaigns may have executed to no customers for conditional campaigns and third-party event subscription channels.
Oct 20, 12:59 UTC