Skip to content

DDoS protection on budget hosts is placebo

General Discussion by blogfranck 25 replies 3.6K views
#1

The protection they sell you for $2/month extra, voilà, it is nothing. The upstream provider does the null-route in 30 seconds regardless. Your "protected" IP goes offline while the attack continues against their infrastructure.

I have tested this. KnownHost "DDoS protection included" — 2Gbps UDP flood, server offline 4 minutes. CloudCone https://cloudcone.com "premium mitigation" — 800Mbps, null-routed 12 minutes. Both promised "up to 10Gbps protection."

The reality: budget hosting rents IP from upstream. Upstream has actual protection but costs per mitigation event. Budget provider cannot pay. So the null-route is the only tool. Voilà.

I am tired of the marketing.

#2

2Gbps and they FOLDED

My home connection handles more

ALL CAPS LIES for sale

But the null-route is not protection, is surrender

grabs popcorn, checks /r/drama
#3

It actually works, mostly.

Then someone on my network pissed off a Minecraft kid. 300Mbps reflection attack. GreenCloudVPS's "protection":

14:32:01  alert: potential DDoS detected
14:32:03  action: traffic scrubbing initiated
14:32:45  alert: scrubbing capacity exceeded
14:32:46  action: null-route 203.0.113.47/32
14:32:46  status: protection successful

"Protection successful" because the attack stopped hitting their router. My server was unreachable for 6 hours. They called this "mitigation."

Moved to a dedi at HostHatch, no "protection" advertised, just fat pipe. Same attack, no null-route, survived. Sometimes the honest absence of feature beats the lie.

works on my bench ¯\_(ツ)_/¯
#4

Virtualization tax applies here too. Budget "DDoS protection" is often just Voxility or similar upstream, marked up 400%, with no actual configuration. The provider buys a port with basic filtering and resells it as "protection."

OpenVZ makes this worse: no custom iptables, no XDP, no kernel-level mitigation. You're paying for a cgroup limit that dies under load. KVM at least lets you run your own filtering, though the network path remains shared.

Real protection requires:
- Sufficient upstream bandwidth (not oversold)
- Actual scrubbing center with clean pipe return
- Anycast dispersion

None of this exists at $5/month. The virtualization tax on honesty is what kills these offerings.

virsh list --all | wc -l: 47
#5

KVM kate nailed it on openvz, no XDP no hope

#6

Which upstream? Voxility, or did they refuse to name it?

grabs popcorn, checks /r/drama
#7

Same story at my last host. "Protection" meant automatic null-route.

hot air, steady hand, magic smoke
#8
Doug said:
Which upstream? Voxility, or did they refuse to name it?

They never name it. I asked GreenCloudVPS support once, got "we use multiple premium upstreams." Asked KnownHost, "proprietary blend of carriers." It's all NDA theater. The actual upstream is usually whoever owns the IP block lease, and the budget provider has zero SLA leverage.

The real tell: check the ASN path during normal traffic. If it hits Cogent or Telia and then disappears into a /24 with no route diversity, there is no scrubbing center. Just a pipe and a prayer.

virsh list --all | wc -l: 47
#9
kate3 said:
No scrubbing center. Just a pipe and a prayer.

This. I ran a VPS at CloudCone for 8 months. Their "premium mitigation" is literally a Cogent upstream with RTBH. You can see it in the traceroute: cogentco.com hop, then dead. No GTT, no NTT, no path to any scrubber.

The $2/month is markup on a feature Cogent provides free to the datacenter. You're paying for a null-route with branding. Check for yourself — https://bgp.tools

#10
hades1995 said:
A null-route with branding

BEST DESCRIPTION

I want that on a shirt

grabs popcorn, checks /r/drama

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft