Wednesday 6th December 2017

DNS

The cause of the issue with INETC1047.INETC.NET NS1.HOSTS.IM has been identified and a fix is currently being deployed.