Update at 11:43:21(GMT): The issue has now been resolved with this server.The engineers have now resolved the issue that was causing the outage and all is not running back as it should.
We are currently experiencing issues with our vps18 server. Our engineers have been notified to the issue and are investigating. We hope to have resolved shortly.
Please accept our apologies for any inconvenience caused.
18th February 2012, at 10:17AM
18th February 2012, at 11:43AM
Update at 08:48:41(GMT): The issue has now been resolved with this server.Our phone support system is presently offline. It will be accessible again when this status message is resolved.
13th February 2012, at 6:12PM
14th February 2012, at 8:48AM
Update at 20:02:06(GMT): Update at 19:09:54(GMT): Update at 23:18:38(GMT): Due to a recently discovered Plesk vulnerability, several servers have had their siteadmin login details reset.
Affected servers include:
business: business4
reseller: reseller6,7,8,12
professional: prohost12
personal: k9,robbie,ted
If you have been affected, we will have emailed your registered email address with full details, and how to proceed.
12th February 2012, at 11:18PM
27th February 2012, at 8:02PM
Update at 18:11:34(GMT): Update at 22:52:13(GMT): Services should now be running much smoother. However users may see one off minor glitches as we work to patch systems affected by the weeks attacks.
We are presently seeing a spike in traffic across our network which is causing slowed access to several systems (notably reseller servers 2, 6, 7, 8).
Most servers and systems should be accessible albeit with reduced speed at this time.
12th February 2012, at 7:26PM
13th February 2012, at 6:11PM
Update at 19:09:49(GMT): Update at 19:15:15(GMT): Back online - investigations continuing as to why this is happening.
12th February 2012, at 5:21PM
20th February 2012, at 7:09PM
Update at 22:52:24(GMT): Update at 14:14:15(GMT): Due to unforseen circumstances, phone support for today, Sunday 12th February, will be via email only. Phone support will resume tomorrow, Monday 13th. Apologies for any inconvenience caused.
12th February 2012, at 9:35AM
12th February 2012, at 10:52PM
Update at 19:25:14(GMT): Update at 14:52:26(GMT): Whilst we continue to monitor the situation, we believe at this time that the problem has been resolved and that all services should be performing normally.
Update at 09:07:35(GMT): Engineers have identified a number of servers that are being maliciously flooded with requests. The increase in traffic has had a knock on effect to most servers in our network. Engineers are currently working on blocking IPs that initiated this attack, and searching out and replacing code on affected sites.
Update at 08:07:27(GMT): We have seen a few shorter and less serious repetitions of the same problem, and continue to solve them each time. We are looking to implement a more permanent fix as soon as possible.
Update at 22:48:21(GMT): Update at 22:39:42(GMT): Most services should now be back online and accessible at normal speeds.
Update at 22:19:35(GMT): We have started to isolate the cause of the network load and work has begun to mitigate the excess network traffic. Some users will now see services back to full operation while others may find access intermittent while work continues.
Update at 21:09:08(GMT): We now have an engineer onsite and are working on correcting the fault.
Update at 20:36:19(GMT): We presently have an engineer on site at one of our datacenters investigating this issue.
We are presently investigating slowed access to our network. All hosted services may experience access issues at this time.
7th February 2012, at 8:27PM
12th February 2012, at 7:25PM
Update at 20:37:28(GMT): Update at 10:13:20(GMT): We have completed this maintenance and are monitoring the situation on these servers to see that it has been improved.
7th February 2012, at 9:31AM
7th February 2012, at 8:37PM
Update at 00:44:57(GMT): At midnight, databases on the PH3 server will be unavailable for approximately 10 minutes time, while emergency work takes place.
6th February 2012, at 11:40PM
7th February 2012, at 12:44AM
Update at 09:44:40(GMT): The issue has now been resolved with this server.server1.xenserve.com is now available again and the fault has been corrected.
6th February 2012, at 8:32PM
7th February 2012, at 9:44AM