2017-03-16 20:01 UTC: The networking services on Web346 are currently down and the machine is offline. We’re working to restore service at this time and will update this post when more information is available.
2017-03-16 22:06 UTC: Web346 is back online after our upstream network provider reconfigured a switch. We’ll continue to monitor for signs of trouble.
2017-03-16 22:26 UTC: Web346 has gone offline again. We’re working to restore service at this time and will update this post when more information is available.
2017-03-16 23:25 UTC: We’re still investigating the connectivity issue.
2017-03-17 00:24 UTC: We’re still investigating the connectivity issue.
2017-03-17 01:44 UTC: We’ve switched Web346 to a different OS kernel and it seem to be stable now. We’ll continue to monitor.
2017-03-17 15:43 UTC: Several hours ago, we determined that Web346 was being attacked. At that time, we took steps to mitigate the attack, and the server has been stable since then. We’ll continue to monitor.
2017-03-24 15:22 UTC: We’ve not seen any further issues over the past several days.
2017-03-10 22:35 UTC: Our control panel and API was under heavy load for the past 10 minutes and may have been slow or unresponsive for some customers. The problem has been resolved and the panel and API are responding normally at this time.
2017-03-02 22:15 UTC: A network connectivity issue in one of our data centers is affecting our incoming mail system. We’re working to restore service and will update this post as soon as more info is available.
2017-03-02 22:47 UTC: This issue is also affecting some of our dedicated servers: DWEB53, DWEB39, DWEB73
2017-03-02 22:52 UTC: Connectivity is now restored. We’ll continue to monitor.
2017-03-03 00:18 UTC: The cause of the issue was a faulty linecard in the data center. The problem has been resolved.