News for hackers. Stuff that matters.

A comment on Linode DDoS continues – Atlanta down for 16+ hours. Parent comment

Re:Linode DDoS continues – Atlanta down for 16+ hours by StanAngeloff on Saturday January 02, 2016 @04:44AM (#10825693)
I agree Linode have mishandled the situation, badly. The lack of information about the ongoing attacks is disconcerting. We have 40+ nodes in London and Frankfurt and are dreading the attacks resuming in those locations. Due to lack of information about the specifics of the attacks, the measures Linode are taking and an explanation why this has happened in the first place, we can't communicate any sound information back to our customers. The only way forward is to switch providers until this quiets down and more details surface.
[ Parent | on HN ]
Re:Linode DDoS continues – Atlanta down for 16+ hours by tsturzl on Monday January 04, 2016 @03:21PM (#10838253)
Out of the top 10 hosting companies, only the 3 largest ones could probably have sustained these attacks, and even those providers would like suffer at least minor outages. The problem wasn't lack of prevention, but scale of attack. There comes a point where the attack, even when mitigated can cause issues.

They were able to mitigate the attacks quickly, but their bandwidth was saturated.

[ Parent | on HN ]
Re:Linode DDoS continues – Atlanta down for 16+ hours by StanAngeloff on Tuesday January 05, 2016 @04:19AM (#10842236)
I don't disagree and hopefully it didn't come across as blaming Linode for not handling the DDoS more efficiently.

My comment was with regards to their inability to communicate with customers about on-going attacks and what was being done to mitigate them. There has been (after nearing 2 weeks of DDoS) just one statement on the status page by a network engineer. No company statement, no information on the measures taken, no e-mails, no support tickets. Nada. We have customers in the Middle East that are geo-blocked from accessing nodes in London. We had to find this ourselves. [1]

Furthermore their billing system didn't account for all the downtime. Looking at our latest statement, all instances have been at 100% uptime.

[1] http://www.theregister.co.uk/2016/01/04/linode_back_at_last_...

[ Parent | on HN ]