We are currently experiencing a DDoS attack on web508. 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-08 04:40 UTC:  The attack has subsided and Web508 is back online.

2016-04-08 06:24 UTC:  The attack has resumed, we’re continuing to work towards restoring services. Sorry for the troubles, thank you for your patience.

2016-04-08 08:10 UTC: The attack has subsided and Web508 is back online. We are monitoring the server to ensure the proper operation of all services.

2016-04-08 09:40 UTC: The attack has resumed, we are working to restore the services ASAP.

2016-04-08 11:00 UTC: The nature of the attack has changed; we are still working to mitigate it.

2016-04-08 11:40 UTC: At this point the attack was mitigated. We are monitoring the server closely.

2016-04-08 18:45 UTC: Web508 has been stable for the past several hours. We’ll continue to monitor.

2016-04-09 03:57 UTC: Web508 is inaccessible at the moment, we’re working to restore it once more. Please stand by.

2016-04-09 06:55 UTC: The DDoS has subsided, Web508 is now accessible and for the moment stable. We’re continuing to monitor it while looking at other avenues to help further mitigate any future attacks.

2016-04-09 09:30 UTC: The attack is back. We are working to mitigate it.

2016-04-09 10:10 UTC: We managed to mitigate the attack. The server is now operational, but the attack is still ongoing, so we’ll continue to monitor the server.

2016-04-09 14:30 UTC: Web508 has been stable for the past several hours. We’ll continue to monitor.

2016-04-11 02:22 UTC: The attack on Web508 seems to have stopped but we will continue to monitor the server for a little longer to be sure. Thank you for your patience.

2016-04-12 16:03 UTC: The attack on Web508 has resumed and the server is currently null-routed. We’re working to mitigate the attack and restore service at this time.

2016-04-12 16:35 UTC: Connectivity to Web508 has been restored. We’ll continue to monitor.

2016-04-13 23:29 UTC: Web508 has been stable for over 24 hours.

2016-04-15 18:06 UTC: The attack on Web508 has resumed and the server is currently null-routed. We’re working to mitigate the attack and restore service at this time.

2016-04-15 18:52 UTC: Connectivity to Web508 has been restored. We’ll continue to monitor.

2016-04-18 14:10 UTC: The attack on Web508 has resumed and the server has been placed in DDoS mitigation.  The server is now operational, but the attack is still ongoing, so we’ll continue to monitor the server. Some traffic may be blocked or a delayed as part of the mitigation.