1200 PDT / 2000 BST – Our engineers have confirmed that the unplanned maintenance on the mail.i-3.com mail service, due to a hardware failure, has been successful and all services have been restored. All queued messages are clearing or have cleared the inbound message queues in MaxMail and are being received by the hosted mail server. We apologise for any inconvenience which this may have caused.
0810 PDT / 1610 BST – Our engineers have confirmed that the restoration of the disk subsystems will take longer than initially anticipated, to resynchronise all of the user data. The latest estimates for full restoration of services to I-3 hosted email systems is 1300 PDT / 2100 BST. This issue does not impact the MaxMail filtering systems. We will post further updates as they become available. Users of the hosted mail (i-3) system can use the message continuity feature within the MaxMail filtering systems, to access and send emails during this maintenance window.
0510 PDT / 1310 BST – Our engineers are currently troubleshooting a recurrence of the issue with the disk subsystem on the I-3 mail server, which is used for their email hosting by a small number of MAX Mail customers.
The http://mail.i-3.com service and control panel access will be unavailable from 0800 EDT/1300 BST on 23/05/2016 until 1200 EDT / 1700 BST on 23/05/2016 for essential maintenance.
During this time, I-3 mail customers will not be able to send or receive mail through the I-3 mail server directly, but no messages will be lost, and those customers can use the continuity feature within the MAX Mail control panel (http://mail.maxfocus.com) to both review any incoming messages in queue and to send new messages as necessary. We will update the status here with any updates as they become available.
10:30am Pacific / 6:30pm GMT – The networking issue within the Amsterdam datacenter has been largely resolved, and our engineers have updated the routing within that datacenter to circumvent any remaining issues. Our monitoring shows that message processing has returned to normal within that facility; we will continue to monitor and will take any further action necessary. Other datacenters were unaffected by the issue.
10:00am Pacific / 6:00pm GMT – Our monitoring has detected a networking issue within the Amsterdam datacenter that may be impacting message processing within that facility. That datacenter is used primarily for backup (lower MX priority) traffic, but some primary traffic is also routed through that datacenter. We are in contact with the networking team at that datacenter, which is working to resolve the issue. We will post further updates here. Other datacenters are unaffected.