The server is currently inaccessible. We are investigating the issue.
2016-05-02 17:32 UTC: Web510 was under a DDOS attack. It is accessible again. We are monitoring for any further issues.
2016-05-05 17:22 UTC: Our upstream provider has enabled mitigation for the next 24 hours. We are continuing to monitor, and the server is accessible now.
2016-05-06 10:05 UTC: The DDOS attack is ongoing, and the server is still behind our upstream provider’s DDOS protection system. The server is generally accessible, but some customers may experience degraded network connectivity and intermittent timeouts.
2016-05-06 16:20 UTC: The attack has subsided and normal connectivity has been restored. We’ll continue to monitor.
We are currently experiencing a DDoS attack on web404. Our upstream provider has enabled mitigation for this attack.
There are still some intermittent access issues until the attack subsides further.
We will update this post as soon as we have further information.
2016-04-02 04:53 UTC: Cisco Guard is still enabled to help reduce the impact. We are continuing to monitor.
2016-04-02 12:20 UTC: The attack was overwhelming our upstream provider’s DDoS mitigation system, so they were forced to null-route the server’s IP address. We’re working with them to restore service as soon as possible.
2016-04-02 13:00 UTC: The DDoS attack has subsided and the null route has been removed. We are continuing to monitor.
2016-04-02 23:35 UTC: The DDoS attack has resumed and the server IP has been null-routed again. Apologies for the troubles while we work to restore the server.
2016-04-03 02:03 UTC: The null-route on the server IP has been removed. The server is accessible with mitigation services enabled to help prevent further downtime. This however can cause intermittent access for some while the DDoS is in effect. We’ll continue to monitor the server. Thank you for your patience.
2016-04-04 17:07 UTC: Web404 has been stable for over 24 hours.
2016-04-04 18:10 UTC: The attack has resumed and Web404 has been null-routed again. We’re working to restore service at this time.
2016-04-04 18:47 UTC: The attack as subsided and the null-route has been lifted.