I really feel bad for these folks. Does know if they have a DDOS mitigation strategy other than RTBH with their transit providers? I would have thought that after the 2015 attack they would have looked into traffic scrubbing with something like Arbor Network or Prolexic. I understand that these are not cheap and Linodes as well as many other hosting provider's margins are probably thin but I would think that it would pay for itself in one or two attacks by minimizing customer churn an event like that causes.
“We have been experiencing a catastrophic DDoS attack”
101–110 of 151 posts
Re: “We have been experiencing a catastrophic DDoS attack”
#102Godaddy has been getting attacked a lot recently as well. Who is likely behind attacking servers, whether other server companies or governments?
Organized crime syndicates? Vigilante hacktivists?
Re: “We have been experiencing a catastrophic DDoS attack”
#103I wonder if this is a diversion to keep Linode's security team busy so they won't notice someone compromising the Xen nodes with XSA-185/6/7/8?
Apparently they came to the same conclusion—just a bit late. https://status.linode.com/incidents/frq9sz7dyb1x
What in that article makes you think that? I don't see it. They do say "we'll have to upgrade Xen nodes", but they don't mention the DDoS or link them.
Re: “We have been experiencing a catastrophic DDoS attack”
#104Earlier quoted context omitted.
which tool are you using for master-master on postgres?
BDR isn't yet available in core Postgres. Postgres-BDR by a company called 2nd Quadrant seems to be the most widely used / best documented. It can be installed as a plugin [1] and there are patched 9.4 packages available [2]. I set up a POC with databases in UK and US (east coast) last year. It was fairly straight forward and seemed to work well. 1: https://2ndquadrant.com/en/resources/bdr/ 2: http://bdr-project.org/…
Don't! Not until the next release. We use the 9.4 and it's very experimental.
Re: “We have been experiencing a catastrophic DDoS attack”
#105I've done some googling before asking here: Can anybody explain why Linode is so often targeted like this? We moved Cronitor off Linode in spring 2015. During the christmas holiday when they suffered a 2 week DDOS I thought of the family time I'd be missing that year as we did a crash migration to AWS had we not migrated when we did. I have to imagine this has been horrible for their business. I would use Linode if I…
As others have said, maybe it's to affect a customer. However, hosting industry had a lot of roots in the adult content industry, and those guys didn't have many ethical guidelines. It was not uncommon for hosting companies to DDoS each other to drive a competitor out of business. Not saying that is the case here, but perhaps?
Re: “We have been experiencing a catastrophic DDoS attack”
#106I disagree with people saying these types of attacks can't be prevented if you switched hosts. I'm sure Google+cloudflare[0] would keep your website online. AWS also if you had the cash. The amount of distributed traffic happening right now against linode would probably only represent a 5% increase in traffic to a popular Google product. At least you know they have the expertise. Nothing against the very smart and ta…
Google and AWS probably have sophisticated DDOS mitigation (can anyone comment on this?) and you can scale up pretty quickly.
But if your service is the direct target of the attack (as opposed to the whole provider) and your servers are getting hammered...
Even if you architecture allows quick horizontal scaling, you still face a tough decision.
The attack could go on for days, and the hosting costs can go really high really fast. Which can be catastrophic for a small company.
Re: “We have been experiencing a catastrophic DDoS attack”
#107Earlier quoted context omitted.
> it is not their fault I don't understand this line of reasoning. It's not like DDoS attacks are some kind of 0-day failure mode that nobody has seen before. Would you also say "it is not their fault" if their uplink provider had a fiber cut and they didn't have redundant uplinks? I'm guessing not: it's well understood that has a service provider you need to plan for this kind of unavailability and pay more money fo…
There are a handful of environments that can sustain a large, coordinated DDOS attack. Can you sink 10-20Gb/s of traffic forever? Not cost effectively.
It wouldn't be 10-20g. That should be easy to handle for most hosting providers. Attacks these days are commonly over 100g. That becomes challenging
Re: “We have been experiencing a catastrophic DDoS attack”
#108Earlier quoted context omitted.
Usually it is and according to linode it is so in this case too. Edit: Not sure what alternate reality the downvoter lives in, but vast majority of the attacks these days are just "dumb" packet floods or even easier to filter reflection attacks. (Linode clarified this to be a mix of dns and ntp traffic on IRC) But hey, go on and find me a layer 7 attack that'll take down entire datacenters :)
One difference between Linode and providers like AWS is that the typical deployment architecture on Linode still exposes customer VPSes to direct L3 internet traffic whereas on a best-practices AWS deployment that is almost never the case. I'd imagine it's easier to filter out bogus L3 traffic when the vast majority of your target IP space comes with explicit configuration as to what sort of L7 application traffic is…
You can't really compare aws to linode. Aws have hundreds of Gb of transit bandwidth so they can easily absorbe big attacks. They also have a backbone network which allows them to increase the surface area of attacks which increases the available bandwidth.
It's actually not that easy to Filter "bogus" traffic. In the hosting world, especially cloud, you have thousands of customers doing whatever they want. Who knows what is bogus or not. And even if you can filter it at your edge routers your transit links are still going to be getting slammed. The filtering needs to be done upstream in the ISP network. This is usually a manual process as no one supports BGP FlowSpec at the moment.
RTBH is the best way to defend if you don't have the bandwidth to absorbe.
Re: “We have been experiencing a catastrophic DDoS attack”
#109Earlier quoted context omitted.
Usually it is and according to linode it is so in this case too. Edit: Not sure what alternate reality the downvoter lives in, but vast majority of the attacks these days are just "dumb" packet floods or even easier to filter reflection attacks. (Linode clarified this to be a mix of dns and ntp traffic on IRC) But hey, go on and find me a layer 7 attack that'll take down entire datacenters :)
One difference between Linode and providers like AWS is that the typical deployment architecture on Linode still exposes customer VPSes to direct L3 internet traffic whereas on a best-practices AWS deployment that is almost never the case. I'd imagine it's easier to filter out bogus L3 traffic when the vast majority of your target IP space comes with explicit configuration as to what sort of L7 application traffic is…
You can't really compare aws to linode. Aws have hundreds of Gb of transit bandwidth so they can easily absorbe big attacks. They also have a backbone network which allows the to increase the surface area of attacks which increases the available bandwidth
It's actually not that easy to Filter "bogus" traffic. In the hosting world, especially cloud, you have thousands of customers doing whatever they want. Who knows that is bogus or not. And even if you can filter it at your edge routers your transit links are still going to be getting slammed. The filtering needs to be done upstream in the ISP network. This is usually a manual process as no one supports BGP FlowSpec at the moment.
RTBH is the best way to defend if you don't have the bandwidth to absorbe.
Re: “We have been experiencing a catastrophic DDoS attack”
#110I don't get the hate towards linode here, on hacker news. I've been their client for a couple of years now and I find it an excellent vps provider. Excellent uptime and performance at a pretty good price. AWS has a few outages every year. Google just had one last week. Azure sucks balls. So, why the hate? Is it because it competes with some ycombinator startups?