We are investigating the issue and will update the post as soon as we have further details.
2017-01-23 23:46 UTC: We’re running a filesystem check on Web340 at this time.
2017-01-24 00:40 UTC: The disk on Web340 is completely unrecoverable. We’re going to use the most recent backup to restore the machine to new hardware. We’ll email affected customers with the new server details.
2017-01-24 02:18 UTC: We’re transferring data from the backup server to the new hardware at this time.
2017-01-24 02:28 UTC: The new server details were just emailed to all affected customers.
2017-01-24 02:45 UTC: About 30% of the affected customers have been restored so far.
2017-01-24 05:37 UTC: About 62% of the affected customers have been restored so far.
2017-01-24 09:20 UTC: Most sites should now be back online. Large files are still being restored
2017-01-24 12:00 UTC: Large files are still being restored.
2017-01-24 19:06 UTC: Large files are still being restored.
2017-01-24 23:15 UTC: Some very large files for a very small number of accounts are still being restored.
2017-01-25 01:58 UTC: All accounts on Web340 have been restored to the new server. If you’re having any problems with your site on the new hardware, then please open a support ticket and our team will assist you.
Currently, websites on Web501, Web507, Web513 are be unreachable. We’re actively investigating this, please stand by for further updates.
2016-12-16 03:41 UTC: Websites and applications should be resolving for all three servers. We’ll monitor them for a little while. Please open a support ticket if you believe there are any persisting issues. Thank you for your patience.
2016-12-15 18:26 UTC: The server is currently not responding. We are investigating the issue and will update this post as soon as we have further details.
2016-12-15 18:34 UTC: The front end nginx server is up and operational at this time. Normal service has been restored. Our System Administrators will be monitoring to make sure that it starts normally.
2016-12-15 10:05 UTC: Connectivity to Web473 is intermittent from various locations. We’re investigating the issue at this time and will update this post when we have more information.
2016-12-15 10:45 UTC: Our data center technicians reported that this issue is due to a failed network router which caused interface connections and routing protocols on the device to stop forwarding traffic. The network engineers are currently working on getting the router back online.
2016-12-15 11:40 UTC: The network router is now fixed and the connectivity to Web473 has been restored.