Hacker News Reader

Comment by USNetizen | Hacker News Reader

I find this ironic because about 2 years ago I had a couple VMs with them that suffered CHRONIC DDoS attacks, all the time. I had to move my clients to a whole other platform. Linode, on the other hand, simply blamed us for supposedly causing the repeat DDoS attacks - one after another for months on end. They even got rather flippant with me exclaiming how "dumb" I was to not understand that is was MY problem apparently, not theirs, even though the target of the DDoS was several addresses in their IP block and not tied to a single client domain, server or anything else. They continued to blame us personally, and even tried to get us to foot the $3,000+ traffic bill.

Well, the tables have turned. Looks like it IS a Linode problem after all. And not a one-time issue, either. This has been happening to them for YEARS.

View on HN

+1 for IP block DDOS'ing - last time I ran a Linode VM it was DDOS'd to smitheereens within half an hour of putting it up (and of course, without any notice that I was liable for overages...)

>(and of course, without any notice that I was liable for overages...)

Inbound traffic does not count against your bandwidth quota, so if you were the target of a DoS attack, this would not result in overages.

https://www.linode.com/pricing

(Unless you were responding to all that traffic, that is.)

They were DDoSing HTTP amongst other services, so, yeah, there was a response via the websites being hosted. That's where the overages came from.

Every point you make I can counter, I've been with them for years, have multiple VMs with them, find their support team fast, competent and courteous. DDOS is a problem for every ISP and every ISP customer.

Not so fast. We migrated all of our former Linode clients to AWS and Azure and have not suffered a single DDoS in the roughly 2 years since the move to other providers. At Linode, on the other hand, we suffered more than a dozen in less than a year - even with different VMs, different IPs, different OSes and different configurations. We were also plagued with overwhelming attempts to brute-force SSH and other services from IPs in China while we hosted with Linode. Nowhere else did we see so much malicious activity targeted against our clients' VMs as we did at Linode.

During that time, Linode support tried ruthlessly to pass the buck and blame us and our clients, denying they had any major problems. Well, here we are and Linode DDoS attacks are STILL occurring on a regular basis, still making news, and they seem to do little about it in terms of a long-term solution. Whereas I have yet to have a single client suffer a Linode-scale DDoS on AWS or Azure at all after almost a half decade of using them.

To be fair, i've had a single linode VPS for years (i'd have to check to figure out how many) and this ddos is the first time i've ever had any issues whatsoever with my linode.

Luck of the draw. Certain IP blocks in the Linode range are attacked all the time, as evidenced here. We had a couple VMs that were never attacked, but far too many of them were on a regular basis for us to even consider staying with Linode.

I've probably had some 50 nodes with Linode over the last 7ish years. Until about 2 years ago I would enthusiastically recommend them to anyone who would listen, but I've found the service has slipped massivel over the last couple of years and now we're trying to migrate people away. We have about 10 nodes left now and blips of lost connectivity and hardware failures are common unfortunately, and the feeling I get from their support team is that this is just to be expected now.

Reply on news.ycombinator.com