Update at 11:20:34(BST): The issue has now been resolved with this server.Engineers have now resolved this issue and all sites known to have been affected are now resolving correctly. If your own site appears to still have issues, please contact support@34sp.com and we can look into this directly for you.
Update at 09:58:47(BST): It seems that a minority of sites on personal hosting are now not responding following this migration. This will affect some sites on the following servers:
holly.34sp.com
robbie.34sp.com
erasmus.34sp.com
k9.34sp.com
ted.34sp.com
ash.34sp.com
We are working to resolve this as soon as possible.
2nd September 2012, at 12:00AM
2nd September 2012, at 10:20AM
Update at 11:47:08(BST):
All spam mail has now been deleted and all services are running normally. Again, thank you for your patience and apologies for any inconvenience caused.
Update at 09:22:10(BST):
We are continuing to delete the spam emails. As there was over 100,000 this is casing some slow down to website load times and email retrieval / delivery. We thank you for your patience. We would like to take this opportunity to remind customers that scripts on your sites are your responsibility and we urge you to keep all scripts up to date. Failure to do so, leaves your sites open to these types of spam attack and other vulnerabilities.
Update at 08:47:31(BST): The engineers are presently working on this and it appears the mail is not genuine so is in the process of being removed. Normal mail delivery will resume and no mail should be lost.
There is currently a large mail queue on the server which has formed overnight which will result in slow mail delivery to and from accounts on reseller server12.
Engineers are currently investigating into whether this is due to a genuine mail shot or a result of an exploited website being used to send spam email.
We will provide an update as soon as we receive confirmation.
34SP apologises for any inconvenience caused and gives assurances it will be resolved as soon as possible.
30th August 2012, at 8:04AM
30th August 2012, at 10:47AM
Update at 16:41:08(BST): This has now been resolved and connectivity restored for these servers.
24th August 2012, at 4:11PM
24th August 2012, at 3:41PM
Update at 19:16:15(BST): The issue has now been resolved with this server.This issue is now resolved
We are aware that the server prohost7.34sp.com is currently unavailable and are investigating this as a matter of urgency.
23rd August 2012, at 7:06PM
23rd August 2012, at 6:16PM
Update at 23:04:57(BST): The issue has now been resolved with this server.Upgrades completed successfully at approximately 22.57. All services should now be working.
Update at 22:46:25(BST): The upgrade is now beginning, we expect it to take no longer than 20 minutes.
Atmail is going offline in the next few minutes. This is in order to implement some emergency upgrades to deploy additional capacity.
Email services hosted on Atmail will be inaccessible for 10-20 minutes at most.
16th August 2012, at 10:25PM
16th August 2012, at 10:04PM
Update at 22:24:34(BST): Update at 00:30:52(BST): At around 8.30PM (August 14th) we were forced to restart bind on our primary DNS server (ns.34sp.com). Bind is the system that converts domain name addresses to IP addresses. Previously undetected configuration errors on the system meant that bind did not restart automatically. Work began immediately on investigating and correcting several configuration records that were corrupted. During this time our secondary DNS server (ns2.34sp.com) was unaffected and continued to serve DNS.
The primary DNS system was restored at approximately 11.40PM. Any affected users would have seen services restored at this time. Please note that each end user would have been affected differently; depending on ISP caching and access of nameservers, many users would experience no loss of service. For affected users, email sent during the event, should be queued by the sending mail server and redelivered without fault.
The nature of this fault was quite rare, and the causes now rectified. We do not anticipate a repeat of this event.
14th August 2012, at 11:47PM
16th August 2012, at 9:24PM
Update at 16:31:26(BST): The issue has now been resolved with this server.We are currently rebooting the server as an emergency measure. Apologies for any inconvenience caused.
14th August 2012, at 12:44PM
14th August 2012, at 3:31PM
Update at 09:26:25(BST): The issue has now been resolved with this server.We discovered a number of compromised private servers within our network that were sending out huge volumes of traffic. We tracked each one down, cleared them up and informed the customers. This was actioned late Sunday evening and we've been monitoring the situation since. Everything is now clear and running as expected.
We are currently aware of some network issues and our engineers have been notified. The cause is currently being identified and we're hoping to have this resolved shortly.
We apologise for the inconvenience caused.
5th August 2012, at 7:37PM
6th August 2012, at 8:26AM
Update at 12:38:41(BST): From 30th July to 3rd August, phone support will be available from 8:00am to 5:00pm. This represents a slight reduction in our normal hours and is a result of staff shortages. Normal hours will resume as of Saturday 4th August.
30th July 2012, at 4:36PM
6th August 2012, at 11:38AM
Update at 16:34:48(BST): The issue has now been resolved with this server.
26th July 2012, at 12:20PM
30th July 2012, at 3:34PM