131–140 of 182 posts
I wish they had a datacenter in Brazil.
Is it free [1], free* [2] or "free" [3]? [1]: free as in free beer, at no direct cost to users [2]: terms and conditions apply, free until you hit certain conditions (for example, constant barrage) [3]: free as in the customers pay for the (mandatory) DDoS protection via increased prices (similar to how I remember OVH handling their "free" DDoS protection)
Fascinating! I learned about fail2ban this week as well as how to search for bad SSH actors -- I was amazed at the traffic requests my Linode was getting decked with. Having this as a default seems good.
Assuming you aren't getting 1000s per minute, of course.
I guess this is basically the same as OVH's "VAC" system? I sometimes get these emails: >We have just detected an attack on IP address x.x.x.x. In order to protect your infrastructure, we vacuumed up your traffic onto our mitigation infrastructure. The entire attack will thus be filtered by our infrastructure, and only legitimate traffic will reach your servers. and then: >We are no longer able to detect any attack o…
> I never need to do anything, but I don't think these attacks are real anyway What would it take to convince you an attack is real when it has been 100% mitigated and you never saw it in your backend infrastructure? I ask as the engineering manager for DDoS protection at Cloudflare, and we stop a lot of attacks. But I feel this tension in the communication and product offering... if we do our job well enough that a…
Earlier quoted context omitted.
Linode gives me 1000GB of transfer for the $5 it costs me to rent a vm, while AWS would charge me $150 for just that bandwidth by itself.
Do you actually use it?
Earlier quoted context omitted.
It's much more advanced than you think : custom asics etc...
Source?
This isn't on the level of some other providers, they'll still null route you if you go over an unspecified amount of traffic. IIRC they use Juniper and Corero. This is the reply I got from their support, just a few days ago: >In short, our DDoS protection works by filtering out DoS-like traffic and is applied via the Linode network, so all Linodes are automatically protected. If your server were to be on the receivi…
Edit: To clarify, filter = protection. Preventing all traffic is not. Both were stated in the description above so they should be clear which one it is.
Earlier quoted context omitted.
Do you publish metrics on “attacks prevented” (or access to logging and monitoring) for customers?
Yes. For HTTP customers there are full SIEM logs under Firewall > Overview on our dashboard, and for paid tiers there are drill-down analytics in addition to the full SIEM logs. There is also log push to receive near real-time full HTTP logs into Google or AWS for your own analysis and these show if a firewall feature touched the request or if it was served from cache. In addition for HTTP customers we show graphs of…
Earlier quoted context omitted.
Do you actually use it?
I’ve been a Linode customer for at least 5 years, and yes, I’ve used a large percentage of that cap on a few occasions. It’s real, if that’s what you’re implying. I use them over other options because their value and simplicity are outstanding.
Unfortunately I've noticed that their "unmetered pipe" offering is quite a downgrade, as it's only 10 Mbit.
EDIT: Sorry, I'm wrong. All dedicated servers have 1 Gbit unlimited uplinks. I'm not sure why I keep getting confused on this point, their support has confirmed this fact many times to me.
Earlier quoted context omitted.
> You can thank them for making free DDoS protection mainstream AWS does charge for WAF and Shield, I believe. I also remember comparing AWS Lambda at Edge vs Cloudflare Workers (though Lambda allows for longer execution times and generally provides more flexibility like RAM, CPU, Runtimes since it runs on a Linux VM vs V8 Isolates for Workers), costs were something like 10x apart. Can't wait for WebSockets support f…
> I also remember comparing AWS Lambda at Edge vs Cloudflare Workers ... costs were something like 10x apart. According to the AWS pricing example[1] 10 million requests per month on Lambda@Edge costs $9.13. The same thing on Cloudflare Workers[2] costs $5.00. So I would expect it to be closer to 2x. Although as you say there's a bit more flexibility with Lambda@Edge so it'll depend on your particular case. I'm curio…
I guess, when I compared, I took Lambda@Edge's per second billing into consideration and not per 50ms (which brings down the RAM usage cost from $62.52 to $3.13 and total usage from $68.52 to $9.13).
What really sealed the deal for me was the very low cold-start times with Workers. I'm not aware of recent improvements with Lambda@Edge, but the last time I tried them, it wasn't uncommon to hit 100ms+ start times.