Resolved 17.20 BST
All issues have now been identified and resolved. Our team will continue to monitor the systems until we are satisfied the service it fully stable.
Thanks you for your patience and apologies for any inconvenience caused.
---
Update 15.40 BST:
Our technical director continues to work on this issue to try and find the quickest resolve and restoration of your service. We cannot apologies enough and hope we can get the issue cleared as soon as is possible.
Again thank you for your continued patience in this matter.
----
Update 14.40 BST:
Our technical director is now in direct contact with Cisco regarding the router issues and hope to have a resolve as soon as is possible.
Thank you for your continued patience in this matter.
----
Update 1300BST:
Cisco are currently investigating the issues with our router and are working to restore full service as soon as possible.
----
We are currently experiencing significant network issues. This will be affecting all services, and showing as packet loss and failed connections.
Engineers have been working on this problem for several hours, and are currently in contact with Cisco for additional support.
We will post updates here when they are available
5th September 2009, at 11:56AM
5th September 2009, at 3:21PM
01:30: The server is now back online and all services restored. No data has been affected as a result of this fault.
00:25: Despite repeated attempts to restore the system, the physical prohost1.34sp.com server cannot be correctly accessed. We suspect a hardware related issue at this time. As a result a standy box is now being brought online to restore services. All data is stored on a highly redundant central NAS system, so data is unaffected by the loss of the orginal prohost1.34sp.com machine.
22:30: Engineers have now determined the cause of this fault and are working to restore the system ASAP. Services should be restored shortly.
21.36: We are presently looking at an issue affecting this server.
4th September 2009, at 9:46PM
4th September 2009, at 11:39PM
Update at 16:15:18 (BST) : The issue has now been resolved with this server.
4th September 2009, at 3:10PM
4th September 2009, at 3:15PM
Resolved and Updated
4th September 2009, at 1:39PM
4th September 2009, at 11:41AM
This has now been resolved.
---------------------
The server is currently being worked on by our engineers. Apologies for any inconvenience caused. This issue has now been resolved at 09:57
--------------
3rd September 2009, at 7:09PM
4th September 2009, at 7:59AM
[UPDATE 17:22 BST] The server is now back online and our engineers are now investigating the cause and solution.
[UPDATE 17:19 BST] This server has experienced some issues again and our engineers are looking at this now.
Apologies for any inconvenience caused.
[UPDATE 16:54: BST] The issue has now been resolved with this server.
--------------
The server is currently being worked on by our engineers. Apologies for any inconvenience caused.
3rd September 2009, at 4:44PM
3rd September 2009, at 3:23PM
3rd September 2009
14.28 This issue has now been corrected.
Apologies for any inconvenience caused.
14:00 Prohost2.34sp.com is presently offline. We are looking into the issue affecting this system.
----------------------------------------
2nd September 2009
22:00 This issue has now been corrected
21:20 Prohost2.34sp.com is presently offline. We are looking into the issue affecting this system.
2nd September 2009, at 9:51PM
3rd September 2009, at 12:28PM
Maintenance is now complete.
Apologies for any inconvenience caused.
--------------------------------------------
We are currently repairing the database and the site and logins to it will be available as soon as possible.
Again thank you for your patience.
----------------------------------------------
Our website is currently offline and our engineers are working on this at present.
Apologies for any inconvenience caused.
1st September 2009, at 6:45PM
1st September 2009, at 5:10PM
Update at 07:47:24 (BST) : The issue has now been resolved with this server.
1st September 2009, at 7:37AM
1st September 2009, at 6:47AM
Update at 21:21:43 (BST) : The issue has now been resolved with this server.
30th August 2009, at 8:59PM
30th August 2009, at 8:21PM