Update at 23:04:57(BST): The issue has now been resolved with this server.Upgrades completed successfully at approximately 22.57. All services should now be working.
Update at 22:46:25(BST): The upgrade is now beginning, we expect it to take no longer than 20 minutes.
Atmail is going offline in the next few minutes. This is in order to implement some emergency upgrades to deploy additional capacity.
Email services hosted on Atmail will be inaccessible for 10-20 minutes at most.
16th August 2012, at 10:25PM
16th August 2012, at 10:04PM
Update at 22:24:34(BST): Update at 00:30:52(BST): At around 8.30PM (August 14th) we were forced to restart bind on our primary DNS server (ns.34sp.com). Bind is the system that converts domain name addresses to IP addresses. Previously undetected configuration errors on the system meant that bind did not restart automatically. Work began immediately on investigating and correcting several configuration records that were corrupted. During this time our secondary DNS server (ns2.34sp.com) was unaffected and continued to serve DNS.
The primary DNS system was restored at approximately 11.40PM. Any affected users would have seen services restored at this time. Please note that each end user would have been affected differently; depending on ISP caching and access of nameservers, many users would experience no loss of service. For affected users, email sent during the event, should be queued by the sending mail server and redelivered without fault.
The nature of this fault was quite rare, and the causes now rectified. We do not anticipate a repeat of this event.
14th August 2012, at 11:47PM
16th August 2012, at 9:24PM
Update at 16:31:26(BST): The issue has now been resolved with this server.We are currently rebooting the server as an emergency measure. Apologies for any inconvenience caused.
14th August 2012, at 12:44PM
14th August 2012, at 3:31PM
Update at 09:26:25(BST): The issue has now been resolved with this server.We discovered a number of compromised private servers within our network that were sending out huge volumes of traffic. We tracked each one down, cleared them up and informed the customers. This was actioned late Sunday evening and we've been monitoring the situation since. Everything is now clear and running as expected.
We are currently aware of some network issues and our engineers have been notified. The cause is currently being identified and we're hoping to have this resolved shortly.
We apologise for the inconvenience caused.
5th August 2012, at 7:37PM
6th August 2012, at 8:26AM
Update at 12:38:41(BST): From 30th July to 3rd August, phone support will be available from 8:00am to 5:00pm. This represents a slight reduction in our normal hours and is a result of staff shortages. Normal hours will resume as of Saturday 4th August.
30th July 2012, at 4:36PM
6th August 2012, at 11:38AM
Update at 16:34:48(BST): The issue has now been resolved with this server.
26th July 2012, at 12:20PM
30th July 2012, at 3:34PM
Update at 07:48:25(BST): The issue has now been resolved with this server.Update at 07:48:17(BST): All services are now back online on the server.
26th July 2012, at 7:41AM
26th July 2012, at 6:48AM
Update at 10:57:15(BST): Update at 12:08:40(BST): Update at 12:03:47(BST): IP has now been moved to the new server and all sites/services should now be available again.
If you are experiencing any issues with this migration please do open a ticket to support.
17th July 2012, at 8:51AM
19th July 2012, at 9:57AM
Update at 11:01:47(BST): Update at 00:09:03(BST): A hardware issue has now been resolved and the server is back online. All should remain okay now and we'll continue to closely monitor this.
Update at 21:27:52(BST): An engineer is now on their way to the datacentre to investigate the fault, as remote access has failed.
We are currently experiencing issues with a personal hosting plan server - adam. Our engineers are presently looking into the issue and hope to have the server up and running again shortly.
Please accept our apologies for any inconvenience caused and our assurances we are working as quickly as possible to get this resolved.
14th July 2012, at 4:30PM
19th July 2012, at 10:01AM
Update at 21:27:16(BST): Update at 19:26:49(BST): Email authentication should be working once more.
We have detected a corruption of an internal database that has caused our SMTP authentication system to briefly halt.
This is a minor error that should be corrected momentarily and services will be restored.
13th July 2012, at 6:49PM
14th July 2012, at 8:27PM