2020-11-27 14:30 UTC: Web512 is back from an emergency reboot. We plan on taking the server down for an fsck to check the file system. Please watch this area for updates and progress on the incident. We appreciate your patience.
2020-11-27 16:40 UTC: We are taking down Web512 for the fsck and will update when we have more information.
2020-11-27 18:00 UTC: The fsck is ongoing and there is no ETA at this time when it will be complete or the server back online.
2020-11-27 18:18 UTC: The fsck is complete on Web512. The server has been returned to operational status and is serving traffic. Our system administrators will continue monitoring the server closely.
We are currently experiencing connectivity issues in USA affecting some servers.
Our network team is working on resolving the issue as quickly as possible.
Please watch this area for updates and progress on the incident.
2020-08-09 13:45 Our data center technicians are looking into the issue on the following servers.
Web512 IP Address: 18.104.22.168
Web513 IP Address: 22.214.171.124
Web514 IP Address: 126.96.36.199
Web515 IP Address: 188.8.131.52
Web555 IP Address: 184.108.40.206
Web556 IP Address: 220.127.116.11
Web560 IP Address: 18.104.22.168
Web563 IP Address: 22.214.171.124
2020-08-09 16:15 UTC: Our onsite technicians confirm all servers are online. The networking team is working on root cause as to why traffic is not routing to the servers.
2020-08-09 17:05 UTC: We have isolated the root cause to a bad router. Our team is in the process of replacing the router.
2020-08-09 18:19 UTC: Switch as been replaced and all servers are back online.
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-10-06 1903 UTC The server has been placed under DDoS mitigation. It is currently accessible, but some customers may experience degraded network connectivity. We continue to monitor the machine closely.
2016-10-06 22:29 UTC: The attack has subsided and the server is responding normally at this time. The mitigation system is still in place, and we’ll continue to monitor for signs of trouble.
2016-10-07 18:45 UTC: The server has been removed from the mitigation system.