After a period of monitoring, both Prohost1 and Prohost4 are running satisfactorily. Please contact support if you have any further questions.
8th February 2010, at 4:02PM
8th February 2010, at 6:40PM
Update at 18:20:09( GMT ) : The issue has now been resolved with this server.
8th February 2010, at 3:53PM
8th February 2010, at 6:20PM
Update at 18:22:49( GMT ) : The issue has now been resolved with this server.
8th February 2010, at 3:51PM
8th February 2010, at 6:22PM
We're happy to report that server6.xenserve.com is now back to full working order.
Thank you for your patience throughout the duration of this issue.
8th February 2010, at 1:16PM
8th February 2010, at 5:13PM
We're happy to report that server7.xenserve.com is now back to full working order.
Thank you for your patience throughout the duration of this issue.
8th February 2010, at 12:42PM
8th February 2010, at 5:12PM
We have been looking at fault on the prohost4.34sp.com server through the last 48 hours.
Recurring load on the server is exceptionally high. When this happens, www and/or mysql services can temporarily fail. Email is unaffected.
Right now we are monitoring the server with an additional level of care. While outages do occur, they are fairly sporadic and limited to 2-3 minutes maximum.
It will take a little longer to diagnose and correct these faults. In the meantime if these faults are severely affecting your websites performance we would be happy to assist in a migration of your account to a completely different prohosting system.
This should alleviate issues within 24 hours for you (DNS migration can take upto 24 hours).
2nd February 2010, at 5:17PM
3rd February 2010, at 6:54PM
The congestion appears to have been a one-off (legitimate) peak and all services appear to be running normally. Please contact support if you continue to have connectivity issues.
2nd February 2010, at 1:49PM
8th February 2010, at 1:28PM
Update at 16:37:05( GMT ) : The issue has now been resolved with this server.
1st February 2010, at 4:04PM
1st February 2010, at 4:37PM
Update at 08:37:06 (GMT) : The issue has now been resolved with this server.
1st February 2010, at 8:19AM
1st February 2010, at 8:37AM
Update at 19:28:17( GMT ) : The issue has now been resolved with this server.
30th January 2010, at 7:13PM
30th January 2010, at 7:28PM