attacks are even worse now, I'm headed to the datacenter to unplug the node with win29 and work on getting it going because null routes are working to block it properly.
I'm very sorry this is taking so long, I've made multiple phone calls and they are not understanding the words 'URGENT' and taking forever to put blocks in place.
ok, now again all is up but Win29, we are still awaiting confirmation that this is due to a null route in place, and then we will post further updates. I don't want any more false hope.
We're continuing to monitor the situation, at this time Win29 based sites will not be live, we are going to attempt to bring up the dedicated IP sites ASAP but taking in small steps here so that it does not return with more attacks.
The null route was put back in place and in fact extended all the way to further upstream peers because it is very huge in amount of data being pumped in, even after being down for over 72 hours. We will be moving accounts to other servers and dedicated IP addresses to work around this. As this was not an HTTP based attack, we're really not sure its target domain, so we are on guard for any return of attacks.
We've been actively making solutions for clients on Win29 shared IP to move their sites over to either dedicated IPs, or a single dediated IP that we manually move their DNS over to for their domains so that this doesn't keep their site down any longer.