Dualog incident

Mail routing issue between Dualog mail server and Office 365 recipients

Critical Resolved View vendor source →

Dualog experienced a critical incident on April 3, 2022 affecting Email and Automatic File Transfer and Support Services, lasting 3h 41m. The incident has been resolved; the full update timeline is below.

Started
Apr 03, 2022, 10:06 AM UTC
Resolved
Apr 03, 2022, 01:47 PM UTC
Duration
3h 41m
Detected by Pingoru
Apr 03, 2022, 10:06 AM UTC

Affected components

Email and Automatic File TransferSupport Services

Update timeline

  1. investigating Apr 03, 2022, 10:06 AM UTC

    We are experiencing intermittent performance issues on our Support email [email protected]. We are working on identifying the issue. In the meantime, please use [email protected] to reach out to our 24/7 Support Team. All ships will be notified about this temporary change.

  2. investigating Apr 03, 2022, 12:20 PM UTC

    *** DO NOT REPLY TO THIS MESSAGE *** Recipient: All ships and Dualog Status subscribers Dear Captains, We are experiencing issues with our Support email [email protected]. We are working on identifying the issue. In the meantime, if you need any Dualog-related assistance please use the following email address to reach out to our 24/7 Support Team: [email protected] We are also available at our usual phone numbers: +47 77621911 +65 62221911 We will notify you as soon as the problem is resolved and you can go back to using our standard email address. Team Dualog

  3. monitoring Apr 03, 2022, 01:21 PM UTC

    Our standard Dualog Support email address [email protected] is now available. The root cause has been identified. We have experienced a mail routing issue between our mail server and Office 365 recipients. This issue also involved some ship's outgoing mail to Office365-recipients (hence the inclusion of the Email services in this incident). We have already escalated this issue to Microsoft and the fix is in place. We are currently monitoring the traffic flow and it is looking promising at the moment.

  4. resolved Apr 03, 2022, 01:47 PM UTC

    This incident has been resolved.