Web442 is currently inaccessible. We are investigating the issue; please stand by for updates.
2016-04-17 03:45 UTC: Our upstream provider have enabled DDOS protection for the server. Network traffic will be degraded during that time. We will remove the DDOS protection as soon as the attack subsides.
2016-04-18 03:25 UTC: The heavy traffic has subsided and mitigation has been removed. At this time the server is stable. We will monitor the server a little further.
2016-04-18 09:30 UTC: The attack has resumed and the server is currently null-routed. We are working to restore the services ASAP.
2016-04-18 13:35 UTC: We’ve managed to mitigate the attack. We are monitoring the server closely.
2016-04-18 14:05 UTC: Our mitigation system was not able to contain the severity of the attack. The server has been null-routed again.
2016-04-18 22:19 UTC: The null route has been lifted and service has been restored. We’ll continue to monitor.
2016-04-20 10:30 UTC: The attack has resumed and our upstream provider has enabled DDOS protection for the server. Degraded network traffic and intermittent connectivity issues are to be expected while DDOS mitigation is active. We are working to restore normal connectivity as soon as possible.
2016-04-22 10:00 UTC: The attack has subsided and normal connectivity has been restored. We’ll continue to monitor.
2016-04-25 04:21 UTC: The attack has resumed and we’re working to have the null route removed and DDoS mitigation services enabled.
2016-04-25 05:27 UTC: The null route was removed under an hour ago and the server should be accessible. Keep in mind there may be intermittent access for some due to the DDoS mitigation service in place.
2016-04-25 10:00 UTC: The connectivity to the server has been stable for several hours. The DDoS mitigation service is still in place and we continue to monitor the server.
2016-04-26 04:25 UTC: The attack has subsided and normal connectivity has been restored. We’ll continue to monitor.