Dualog incident

Dualog Email Delivery

Major Resolved View vendor source →

Dualog experienced a major incident on August 22, 2025 affecting Email and Automatic File Transfer, lasting 4h 11m. The incident has been resolved; the full update timeline is below.

Started
Aug 22, 2025, 09:18 AM UTC
Resolved
Aug 22, 2025, 01:30 PM UTC
Duration
4h 11m
Detected by Pingoru
Aug 22, 2025, 09:18 AM UTC

Affected components

Email and Automatic File Transfer

Update timeline

  1. investigating Aug 22, 2025, 09:18 AM UTC

    We are currently investigating an issue pertaining to email delivery. We are still determining the scope of this issue and will be providing more information shortly.

  2. investigating Aug 22, 2025, 10:20 AM UTC

    We are continuing to investigate this email delivery issue. The issue is isolated to inbound emails (from shore to ship). Outbound emails from the ship are not affected.

  3. identified Aug 22, 2025, 10:37 AM UTC

    We have identified an issue with email delivery issue causing substantial delays to incoming emails. This issue only affects incoming emails - shore to ship. Outgoing emails from the vessels are unaffected. Rest assured, we are treating this issue with the highest priority.

  4. monitoring Aug 22, 2025, 11:27 AM UTC

    We have implemented a fix and are monitoring the results. Email delays can still be expected while our systems handle the backlog. Stay tuned for further updates. The issue is isolated to inbound emails (from shore to ship). Outbound emails from the ship are not affected.

  5. monitoring Aug 22, 2025, 11:34 AM UTC

    We have implemented a fix and are monitoring the results. Email delays can still be expected while our systems handle the backlog. Stay tuned for further updates. The issue is isolated to inbound emails (from shore to ship). Outbound emails from the ship are not affected.

  6. monitoring Aug 22, 2025, 12:00 PM UTC

    The issue has been resolved by the implemented fix. The email backlog has been fully processed, and additional email delays are no longer expected. We are continuing to monitor the situation closely,

  7. resolved Aug 22, 2025, 01:30 PM UTC

    The issue has been resolved by the implemented fix. We apologise for any inconvenience caused.