Update at 08:34:29(BST): The works on the payment system have been completed successfully.
We are currently performing an upgrade on our payment systems so payments may be unavailable for the next 30 minutes.
13th June 2011, at 8:01AM
13th June 2011, at 7:34AM
Update at 12:31:20(BST): The issue has now been resolved with this server.
This server has become unresponsive. We have an engineer en route to the datacentre to investigate.
11th June 2011, at 10:48AM
11th June 2011, at 11:31AM
Update at 22:22:37(BST): The issue has now been resolved with this server.We are presently investigating a fault affecting this server and its services.
9th June 2011, at 8:02PM
9th June 2011, at 9:22PM
Update at 20:33:53(BST): The issue has now been resolved with this server.This issue was resolved a shortwhile ago, if you are still experiencing any issues please do let us know.
8th June 2011, at 7:01PM
8th June 2011, at 7:33PM
Update at 09:24:09(BST): We have been operating with IPv6 access available to our website & account pages thus far with zero reported problems. As a result, I believe that it is suitable to mark this (potential) outage as resolved.
Any customers having trouble accessing our website (or any site hosted by 34SP.com) should drop us an e-mail to discuss this.
7th June 2011, at 9:30PM
13th June 2011, at 8:24AM
Update at 21:26:03(BST): Gambit has been running well since this outage first occurred, therefore we are marking this update as resolved.
5th June 2011, at 8:04PM
7th June 2011, at 8:26PM
Update at 21:03:45(BST):
All appears to be well now. This outage is now marked as resolved.
5th June 2011, at 5:54PM
5th June 2011, at 8:03PM
Update at 09:53:40(BST): The issue has now been resolved with this server.The issue with this server has now been resolved.
3rd June 2011, at 8:05AM
3rd June 2011, at 8:53AM
Update at 21:04:17(BST):
All appears to be well since the change to the network. This means that this update will now be marked as resolved/closed.
2nd June 2011, at 10:29PM
5th June 2011, at 8:04PM
Update at 09:59:17(BST): This issue was resolved as of the earlier update.
31st May 2011, at 3:40AM
3rd June 2011, at 8:59AM