Update at 09:00:02(GMT): The issue has now been resolved with this server.The engineers have now resolved the issues that were causing the service failures. All services are back up and running again and under monitoring.
The server k9 appears be having trouble with the main Apache and MySQL services which will stop websites and email from working.
Our engineers have been notified and are investigating now. Please accept our apologies for any inconvenience caused during this time.
16th March 2012, at 8:12AM
16th March 2012, at 9:00AM
Update at 14:46:48(GMT): The issue has now been resolved with this server.Reboot and update complete.
The server is undergoing a reboot and emergency maintenance . This was for security reasons. We apologise for any inconvenience caused.
14th March 2012, at 1:38PM
14th March 2012, at 2:46PM
Update at 12:45:20(GMT): We are no longer experiencing any delays on the sending of SMTP mail.
7th March 2012, at 2:53PM
8th March 2012, at 12:45PM
Update at 10:19:43(GMT): The mail queue on adam has now been resolved and mail for users on this server will be processed normally.
6th March 2012, at 10:10AM
8th March 2012, at 10:19AM
Update at 19:45:35(GMT): The issue has now been resolved with this server.Update at 19:29:21(GMT): All services should now be restored.
Update at 19:28:27(GMT): Our engineer has now restored most services. Any remaining issues will be addressed momentarily.
Update at 18:47:31(GMT): Our engineer is now on site to fix the last few remaining servers affected by this fault.
Update at 17:46:30(GMT): The following servers are still unavailable due to this network issue:
vps20
vps21
prohost10
prohost11
prohost12
prohost13
businesshost1
xenserve19
xenserve20
We have an engineer en route to the datacentre to fix this remaining set of servers now and will update this post again once this had been done.
5th March 2012, at 10:49AM
5th March 2012, at 7:45PM
Update at 09:50:41(GMT): The issue with this server is now resolved
3rd March 2012, at 2:44PM
5th March 2012, at 9:50AM
Update at 14:04:44(GMT): The mail queue on max has now been cleared and we are seeing email delivered to mailboxes.
2nd March 2012, at 10:05PM
12th March 2012, at 2:04PM
Update at 13:34:51(GMT): Queues on the SMTP array have returned to nominal levels and there shouldn't be any delays remaining connected with the use of this service.
29th February 2012, at 9:12AM
1st March 2012, at 1:34PM
Update at 16:42:18(GMT): The issue has now been resolved with this server.Update at 10:16:57(GMT): The VPS18 issue will be resolved today and the final moves are taking place.
Update at 15:05:18(GMT): We only have a small amount of containers remaining on VPS18. We are contacting these clients as and when we migrate.
Update at 10:15:37(GMT): The restoration of containers is taking longer than initially expected due to manual work involved. We're informing clients as and when their container is being moved.
Update at 17:36:52(GMT): Almost half of the clients have been contacted and VPS servers moved.
Update at 15:55:28(GMT): We have moved some containers and we're going through them one by one. Unfortunately this can be a slow process. We will be ringing customers before moving them.
Update at 12:44:05(GMT): As a precaution engineers are moving all containers from VPS18 to a separate server. This will prevent any further issues. Customers will be contacted in due course.
Update at 10:23:55(GMT): We are currently going through each VPS container and contacting the owner. We will be updating them while we work on restoring their services.
Update at 09:32:27(GMT): The server has had firmware updates, however some data loss may have occurred during the reboot. Our engineers are looking into this. We will be updating this page as soon as we have any further information.
A fault was identified with the server this evening. It was rebooted a little after 11PM and is presently undergoing disk scans before coming back up.
We do realise this is a repeating fault. Please be advised replacement hardware is on order and set for installation and migration imminently.
28th February 2012, at 11:44PM
5th March 2012, at 4:42PM
Update at 13:34:06(GMT): After 48 hours of close monitoring, we are resolving this status.
28th February 2012, at 12:35PM
1st March 2012, at 1:34PM