Update at 22:09:10(BST): Update at 20:14:46(BST): This email should now be with all affected reseller:
Server22 is now back online using replacement hardware. We have recreated domains and email accounts and have also been able to restore most user's database data. Due to the catastrophic disk failure most files and email remain unrecoverable. We do ask that users restore from their local backups at this time.
Around 5.30PM email services were re-activated, and you should now see new emails flowing into server22 hosted mailboxes. Email sent to mailboxes during the outage should have been queued at the sender's side. These emails should now start to be delivered to mailboxes.
If you do have a site that was previously migrated from an older reseller system, its possible we may have legacy backups for the site, relating to its period on the prior server. We are presently building a list of these sites internally for restoration. If you do have such a site, please contact us and we can check if a backup does exist and attempt a restore.
Update at 20:00:20(BST): All resellers have now been emailed with an update on this situation.
The server is back online with new hardware. Accounts have been recreated and mailboxes recreated. Email should now be coming in also.
Database data was restored from maintenance backups. Files and email on the disks were completely unrecoverable, so clients will need to refer to their local backups.
Please note that the reseller service does not come with backups as standard, backups are an optional on request add on only.
Update at 13:54:20(BST): We have emailed all affected resellers with an update and will be calling them shortly.
7th June 2013, at 8:41AM
24th June 2013, at 9:09PM
Update at 16:53:49(BST): The issue has now been resolved. The phone lines are now open.
15:01:22(BST): We are having some technical difficulties with our phone lines because of which they currently closed. We hope to have this resolved soon. If you require any assistance please file a ticket with us using the 34SP control panel.
1st June 2013, at 11:50AM
1st June 2013, at 3:53PM
Update at 10:40:03(BST): With no further issues on this server we are happy that the issue has been resolved.
9th May 2013, at 11:58AM
10th May 2013, at 9:40AM
Update at 20:33:00(BST): Update at 19:01:04(BST): Phones are back online now, but may need to go off one more time this evening briefly.
Due to some quick office maintenance phone support is going offline. This should last no more than 60-90mins.
2nd May 2013, at 6:36PM
2nd May 2013, at 7:33PM
Update at 16:04:28(BST): Following several disk checks, the server is now available again.
29th April 2013, at 11:30AM
29th April 2013, at 3:04PM
Update at 22:36:46(BST): The issue has now been resolved with this server.The upgrade went as expected and all servers are checking out fine after the completed work. The basic systems now have double RAM (20>40GB) which should vastly improve performance.
We will continue to monitor system uptime and performance but expect things to dramatically improve from here on out.
Update at 22:16:24(BST): Upgrade is now complete and the servers are rebooting and being cross checked.
Update at 21:56:20(BST): Our engineer is now on site and starting the upgrade. PH20-22 will now go offline for 15-30 minutes.
Update at 21:24:13(BST): Several tweaks have improved stability through the evening and we also expect our engineer to be on site within the next 30 minute to commence the final upgrade.
Update at 20:27:31(BST): Due to the increasing instability of the platform, we have escalated the emergency work.
We are presently arranging for an engineer to head to the datacenter and begin the upgrade this evening (Apr 16th). More updates as this unfolds, but we expect to restore full availability this evening.
We have identified a load issue on this trio of servers.
We will be monitoring and maintaining these systems best we can through this evening (Apr 16th).
During the morning of April 17th we intend to complete an emergency upgrade on this system which will vastly increase system resources.
This should correct the issue long term.
16th April 2013, at 6:36PM
16th April 2013, at 9:36PM
Update at 02:29:14(BST): Update at 01:50:57(BST): All servers should now be back online that have been affected by this event.
Update at 01:20:21(BST): We have identified the area of our network generating the issue and are presently isolating the cause. Most systems will now be fine, but some may still be slowed.
We are presently examining a slow down of several systems on our network.
16th April 2013, at 12:21AM
16th April 2013, at 1:29AM
Update at 18:31:55(BST): Prohost 17-19 are now back online and serving. Each server has had its RAM doubled form 20GB to 40GB. This, in addition to some granular tweaks to the overall system should provide a vastly better uptime level for all users.
Update at 18:22:20(BST): PH17-19 have now been upgraded and are booting back up.
Update at 18:02:37(BST): PH17-19 are now going offline.
We will be shortly beginning an emergency maintenance window on the prohost 17 through 19 servers.
We will be doubling the servers RAM, which should take 15-30 minutes in total. This should help ease the repeating load issues the servers have experienced lately.
Once the maintenance begins and ends, we will update this post.
11th April 2013, at 5:03PM
11th April 2013, at 5:31PM
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