Web527 did not come back after a reboot. We are looking into this and will resolve as quickly as possible.
2017-08-15 13:48 UTC: The server is back online. The issue was with the installed kernel. It was changed and the server rebooted.
The server is currently inaccessible. We are investigating the issue and will update as soon as we have more details.
2017-07-12 00:33 UTC: Web550 is back online at this time. The problem appears to have been an DDoS attack targeting Web550. The attack has subsided. We’ll continue to monitor.
2017-07-12 15:32 UTC: Web550 was rebooted 90 minutes ago to attempt to resolve an issue with IPv6 connectivity. The server is back online, but IPv6 connectivity is down.
The server is currently not responding. We are looking into the issue and will provide an update as soon as possible.
2017-07-07 21:20 UTC: Investigations so far have found a hardware issue with the raid controller. We are continuing to investigate.
2017-07-07 21:40 UTC: The server is back online. No hardware issues were found.
We are currently investigating the issue and will update as soon as we have further details.
2017-06-22 19:06 UTC: The servers are accessible again. There was a network issue that caused the temporary interruption.
Our upstream provider will be performing emergency maintenance one of their routers on May 30th starting at 08:00 UTC.
A three hour maintenance window has been scheduled. The total expected downtime should not exceed three minutes.
The affected servers are:
Mailbox12, Mailbox13, Mailbox14, Mailbox15, Mailbox16
The server is currently not accessible. We are looking into this and will update as soon as we have further details.
2017-05-15 14:59 UTC: We are still investigating the issue.
2017-05-15 17:20 UTC: Our datacenter technicians are working directly to power on the server.
2017-05-15 20:17 UTC: The server is accessible again.
The server is currently not accessible. We are looking into this and will update as soon as we have further details.
2017-04-26 00:04 UTC: The servers is back online.
The server is currently not accessible. We are looking into this and will update as soon as we have more details.
2017-04-21 17:37 UTC: The servers is back online.
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.
2016-12-30 13:33 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-30 13:41 UTC: We were able to reboot the server to resolve the issue. The server is back online.