Update at 10:00:59(BST): The issue has now been resolved with this server.This issue was resolved around an hour ago, an issue with the firewall setup within each domain had caused it to block all external connections, we have increased limits on the firewall connection tracking systems to avoid this issue re-occurring.
At the same time a kernel update was also applied to the server as well.
30th August 2011, at 8:19AM
30th August 2011, at 9:00AM
Update at 10:26:29(BST): The outage was caused by a "rare failure" in the UPS systems. Despite this hardware being designed with N+1 redundancy, the loss of two units resulted in a 20ms dip in power to our racks within that room.
We are confident that our providers have rectified this fault and will be working to mitigate any recurrence of this particular scenario in the future.
24th August 2011, at 2:36PM
1st September 2011, at 9:26AM
Update at 20:23:36(BST): Xenserve19 has been running well since the incident today, however please see the recent post regarding the emergency upgrade as this will require some further (planned) downtime this evening, but will hopefully put to bed these issues with load.
19th August 2011, at 8:17AM
13th September 2011, at 7:23PM
Update at 09:36:50(BST): Phone lines are now open again.
9th August 2011, at 11:36PM
11th August 2011, at 8:36AM
Update at 23:33:44(BST): Prohost12 now appears to be running acceptably once again, outage marked as resolved.
9th August 2011, at 9:19AM
9th August 2011, at 10:33PM
Update at 23:34:39(BST): No lasting issues have been experienced in the week since the maintenance, therefore this outage is now marked as resolved.
2nd August 2011, at 9:40PM
9th August 2011, at 10:34PM
Update at 16:22:01(BST): The issue has now been resolved with this server.This matter was resolved around 2.30PM
2nd August 2011, at 2:22PM
2nd August 2011, at 3:22PM
Update at 16:33:11(BST): This migration is now being marked as finished, if however anyone is having any issues since the migration please do contact us and we will aid in looking into the problems for you.
2nd August 2011, at 8:07AM
3rd August 2011, at 3:33PM
Update at 14:21:50(BST): We haven't seen a resurgence of this issue lately and no specific issue was identified since the last episode.
30th July 2011, at 12:16PM
2nd August 2011, at 1:21PM
Update at 19:16:42(BST): The issue has now been resolved with this server.Update at 19:11:13(BST): We identified an exploited user account that allowed a rogue process to cause excessive load. This has been eliminated and the server has been rebooted (19.07).
Update at 18:42:11(BST): We are presently investigating an issue of severe load on the bill.34sp.com server. Services are offline at this time.
20th July 2011, at 6:39PM
20th July 2011, at 6:16PM