Update at 18:41:16(BST): Update at 18:41:02(BST): This issue has been resolved. We have identified a compromised system that has now been isolated.
We have identified an issue affecting the general speed of our network.
We are attending to this matter now.
7th April 2013, at 6:22PM
7th April 2013, at 5:41PM
Update at 10:53:47(BST): The issue has now been resolved with this server.
This server is now back online. Apologies for any inconvenience caused.
Engineers have had to perform an emergency reboot on this server.
Apologies for any inconvenience caused.
5th April 2013, at 10:48AM
5th April 2013, at 9:53AM
Update at 13:50:55(GMT): The issue has now been resolved. Our phone lines are now open. Apologies for any inconvenience caused.
Update at 09:58:41(GMT): Our phone lines are currently closed as a member of our weekend staff is unable to come to work, due to the adverse weather. Apologies for any inconvenience caused.
23rd March 2013, at 9:58AM
23rd March 2013, at 1:50PM
Update at 15:31:45(GMT): The issue has now been resolved with this server.
The server is now back online. Apologies for any inconvenience caused.
Update at 14:55:21(GMT): We are having to perform an emergency reboot.
Apologies for any inconvenience caused.
15th March 2013, at 2:54PM
15th March 2013, at 3:31PM
Update at 10:17:55(GMT): This issue is now marked as resolved.
Update at 14:24:09(GMT): The issue has now been corrected. We identified a rogue server creating excess traffic that has now been corrected.
We do maintain automated systems to prevent these floods and in this instance the system seems to have failed to prevent the attack. We are presently reviewing the piece of hardware used to protect against these floods, in order to prevent a repeat.
Update at 14:13:59(GMT): We have identified the cause of the network load and are working to quickly correct this. All affected services will be accessible again momentarily.
Engineers are currently investigating initial reports of network traffic that is failing to resolve to a server. We'll post further information as soon as it becomes clear where the issue actually lies.
11th March 2013, at 1:46PM
12th March 2013, at 10:17AM
Update at 07:47:27(GMT): The issue has now been resolved with this server.Our engineers managed to isolate the issue causing this and resolve it around 0700 GMT. All mail services have been performing as normal since.
It has come to our attention there is currently issues connecting to our mail server database.
Our engineers have been notified and investigations will commence shortly.
This will be affecting all receiving of emails this includes webmail services as well as POP3 and IMAP connections for those on Professional and Business hosting plans.
34SP apologies for any inconvenience caused.
8th March 2013, at 6:23AM
8th March 2013, at 7:47AM
Update at 08:02:38(GMT): Though this was resolved some hours ago, we have now received confirmation that the maintenance window is clear and no further outage should be expected.
Update at 03:34:06(GMT): The outage has been caused due to unscheduled maintenance to one of our main provider's fibre networks.
We are still fine tuning the failover system and our engineers are working to bring it to full capacity to counter for the loss of service. Please bear with us whilst we continue to stabilise the framework to bring your service back to optimal performance and once again, please accept our sincerest apologies for any inconvenience that this may have caused.
Update at 02:44:48(GMT): Though this is mot now affecting all users, the initial rerouting of traffic seems not to have been sufficient. Engineers are actively working to resolve this as soon as possible. Updates will be provided as soon as we have any further news. Apologies for the continuing down time.
Update at 02:26:28(GMT): At approximately 1:30am, our network suffered from some instability. This caused service wide connection problems and our engineers were alerted to the issue.
The engineers pin pointed this issue as originating outside of our network and rerouted traffic accordingly as this did not failover automatically as intended. As of 2am the issue is considered largely resolved. Please accept our sincerest apologies for any inconvenience this may have caused.
5th March 2013, at 2:18AM
5th March 2013, at 8:02AM
Update at 08:43:04(GMT): The issue has now been resolved with this server.
The server is now back online. Thank you for your patience.
---
Engineers have had to perform an emergency reboot on this server. Apologies for any inconvenience caused.
4th March 2013, at 8:34AM
4th March 2013, at 8:43AM
Update at 23:44:13(GMT): The issue has now been resolved with this server.
These servers are now back online. Apologies for any inconvenience caused.
Customers are advised to check their VPS for any unauthorised activities and to remember to keep them updated at weekly.
---
There appears to be a large amount of traffic coming from these servers.
It may be a site that has been compromised and is being used to outbound attack.
Our engineers are working to find the cause.
Apologies for any inconvenience caused.
2nd March 2013, at 8:57PM
2nd March 2013, at 11:44PM
Update at 11:01:02(GMT): Update at 11:00:53(GMT): All users have now been migrated off this server.
Update at 13:49:33(GMT): Our engineers are looking to replace the hardware to ensure we can move our clients to another service. An engineer is currently on site at the data centre.
The stability of this server has been increasingly poor throughout the evening of Wed (20/02/13).
At this time the machine is repeatedly locking up requiring manual power cycles.
We will keep rebooting the machine throughout the night as required until Thursday (21/02/13) morning when our engineering team will be reviewing the fault as a priority.
21st February 2013, at 12:53AM
5th March 2013, at 11:01AM