Optimove incident

DNS Resolution Issue Affecting Multiple Services

Major Resolved View vendor source →

Optimove experienced a major incident on June 8, 2025 affecting Core App and Core App and 1 more component, lasting 16h 58m. The incident has been resolved; the full update timeline is below.

Started
Jun 08, 2025, 04:41 AM UTC
Resolved
Jun 08, 2025, 09:39 PM UTC
Duration
16h 58m
Detected by Pingoru
Jun 08, 2025, 04:41 AM UTC

Affected components

Core AppCore AppAPIAPIBatch Data ProcessBatch Data ProcessTrack & TriggerTrack & TriggerOptimobile

Update timeline

  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.