Update at 22:22:29(BST): The issue has now been resolved with this server.The update has completed and email services are now back online.
Update at 22:17:13(BST): The upgrade is now beginning.
In order to upgrade capacity on our Atmail mail cluster, the system will be taken offline for approximately 10-15 minutes.
Email access will be momentarily disabled. This post will be updated when maintenance begins and ends.
22nd August 2013, at 10:15PM
22nd August 2013, at 9:22PM
Update at 15:00:44(BST): The issue has now been resolved with this server.Webmail is now working.
There may still be some issues with SMTP passwords. If your password does not work, login to https://www.34sp.com/login' target='_blank'>https://www.34sp.com/login (SMTP) section and reset it.
Apologies for any inconvenience caused.
Engineers are currently aware that users cannot send email using webmail and some are having issues authenticating using their email clients. This is being investigated at present.
Those having an issue with an email client, such as Outlook etc can reset their password via https://www.34sp.com/login' target='_blank'>https://www.34sp.com/login (SMTP) section.
If the above does not work, please raise a support case and we will investigate your domain for you.
Apologies for any inconvenience caused.
22nd August 2013, at 2:40PM
22nd August 2013, at 2:00PM
Update at 00:13:45(BST): The issue has now been resolved with this server.Having tracked the issue to a faulty component within the server, a replacement has been fitted and the server is now being restored to normal service.
Update at 23:31:09(BST): Attempts to recover the system using remote access have failed, meaning we expect some form of hardware failure. A second engineer is on route with replacement hardware parts in an effort to correct the fault.
Update at 21:19:51(BST): We are still working on identifying the cause of the failure on this system. At this time we are running extensive disk checks on the server.
Update at 17:53:45(BST): The server has failed to come back on-line after the reboot. Remote access tools have been enabled by our on site engineer, to enable remote diagnosis.
We now have an engineer en route and will update this page as soon as we have more information. Again, we thank you for your patience.
Engineers are performing an emergency reboot on this server. Apologies for any inconvenience caused. Thank you for your patience.
19th August 2013, at 5:45PM
19th August 2013, at 11:13PM
Update at 14:30:58(BST): The issue has now been resolved with this server.All service now back on-line. Apologies for any inconvenience caused.
Update at 14:22:02(BST): Engineers have rebooted the server. We hope to have services back on-line within 10 minutes. Thank you for your patience.
Engineers are currently trying to bring services back on-line. We may have to reboot this server, if this fails in the next 5 minutes. Apologies for any inconvenience caused.
16th August 2013, at 2:17PM
16th August 2013, at 1:30PM
Update at 21:20:04(BST): Update at 06:42:34(BST): It has come to our attention that some users may still be experiencing slight issues with the control panel, engineers will be working on this throughout the morning.
Update at 22:26:15(BST): A temporary fix is now in place, so that all users can use the control panel just fine. Final work will complete on this tomorrow.
Update at 21:08:39(BST): We have identified an odd routing issue internally that is causing issues with the control panel. We are actively working on this now, and do hope to correct the fault within the evening.
We are investigating several reports of generalised issues within the 34SP.com control panel.
We are presently advising clients to temporarily hold off using the CP while our developers look into this.
More updates will be available as our development team identifies the issue.
7th August 2013, at 7:21PM
19th August 2013, at 8:20PM
Update at 21:56:09(BST): The issue has now been resolved with this server.Upgrade now complete
Update at 21:46:26(BST): The upgrade is now beginning.
In order to deploy additional mail capacity, Atmail email services will go offline this evening for around 10-15 mins.
This will start at approx 21.50-22.00. Updates will be posted here as this begins.
6th August 2013, at 9:38PM
6th August 2013, at 8:56PM
Update at 19:00:05(BST): The issue has now been resolved with this server.Update at 18:59:33(BST): Phones are back online folks!
We are presently investigating a fault affected our phone lines.
Please note support staff are working, and indeed, are so 24/7 for the next few days.
6th August 2013, at 6:19PM
6th August 2013, at 6:00PM
Update at 10:14:34(BST): The issue has now been resolved with this server.Engineers have located and fixed the network issue.
There's currently an issue with the network to server22. Our engineers are urgently tracing this and hope to have it resolved and online shortly.
We apologise for the inconvenience caused.
1st August 2013, at 9:59AM
1st August 2013, at 9:14AM
Update at 01:52:28(BST): The issue has now been resolved with this server.We are investigating a general issue causing slow down on our network right now.
23rd July 2013, at 1:42AM
23rd July 2013, at 12:52AM
Update at 13:33:44(BST): The server has come back up following the disk check and is now serving sites as normal.
Update at 12:52:45(BST), 22nd July: The server has been issued a reboot from our engineers. They are currently checking the logs and kernel version on the server to increase it's stability. The server is currently undergoing a disk check from the reboot and we expect it to come back online shortly.
We apologise for the inconvenience caused.
Update at 13:11:13(BST): The issue has now been resolved with this server.A new kernel has been installed. The disk check completed okay and no errors were found. All services have been up and running great for the last hour. Apologies for any inconvenience caused.
Our engineers are currently investigating an issue with Server19, the server is undergoing a reboot and disk check. Once it's back online the engineers will be looking for the cause of the issue.
We apologise for the inconvenience caused.
19th July 2013, at 11:38AM
22nd July 2013, at 12:33PM