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
Update at 00:24:08(GMT): The issue has now been resolved with this server.Server13 is about to be rebooted in order to apply several critical firmware updates.
Expected downtime is approximately 10 minutes.
27th February 2012, at 11:45PM
28th February 2012, at 12:24AM
Update at 16:42:09(GMT): The issue has now been resolved with this server.Update at 15:28:38(GMT): The delivery issue has now been resolved and mail has been verified as delivering successfully. This means that any new mail sent to users on server5.xenserve.com, or mail sent from the server should be delivered as usual.
The large queue of spam mails generated between Saturday and Tuesday afternoon is still in the process of being cleaned before delivery to mailboxes on server5.xenserve.com. It currently stands at approximately 1,000,000 e-mails and we would expect this to reduce a lot before delivery to customers is made.
27th February 2012, at 2:07PM
5th March 2012, at 4:42PM
Update at 10:50:24(GMT): We have identified this issue and resolved it. We will report the problem to our firewall providers so that they can implement a permanent fix
25th February 2012, at 9:45AM
25th February 2012, at 10:50AM
Update at 22:15:42(GMT): The mail backlog has now been cleared and full service restored.
24th February 2012, at 1:31PM
24th February 2012, at 10:15PM
Update at 14:20:29(GMT): We have cleaned out a large queue of e-mail that had built up and have seen the server behave reliably this morning, so we are marking this issue as resolved.
Our automated monitoring systems will continue to monitor adam.34sp.com and alert us to any issues.
22nd February 2012, at 11:12PM
23rd February 2012, at 2:20PM
Update at 16:04:59(GMT): All containers have now restarted.
22nd February 2012, at 3:35PM
22nd February 2012, at 4:04PM
Update at 19:39:27(GMT): The issue has now been resolved with this server.The server and all containers are now back online.
This server is about to be rebooted for some brief emergency maintenance.
Downtime is anticipated to be approximately 10 minutes or so.
20th February 2012, at 7:09PM
20th February 2012, at 7:39PM