Choosing a DDoS-protected VPS: eight questions to ask
Always-on or on-demand, TCP and UDP, L7, capacity, null routes and billing: the questions that separate real DDoS protection from a line on a pricing page.
Updated 20 November 2026
Almost every VPS offer now says “DDoS protection included”. The phrase covers everything from a real multi-layer filter to an upstream null route that takes your server offline to protect everyone else. These eight questions tell them apart.
1. Is it always on?
Always-on filtering inspects traffic all the time, so an attack is handled from its first packet. On-demand protection waits until a flood is detected, then reroutes traffic through a scrubber, which can take seconds to minutes during which you are down. For anything players or customers notice, always-on is the one to want.
2. What happens when the attack is bigger than the filter?
Every filter has a capacity. Ask what happens above it. Many providers null-route the target address: the upstream drops all traffic to it, attack and real users alike, for minutes or hours. That protects the provider’s network, not you. Ask how long, and whether you are told.
3. Does it filter UDP, and how?
Game servers, voice and streaming use UDP. Many filters handle TCP well and treat UDP crudely: either everything passes, or whole port ranges are blocked. Ask how game traffic is handled. Good answers mention verifying sources before UDP is accepted and per-source rate limits.
4. What about TCP handshakes?
SYN floods are the most common protocol attack. A SYN challenge (cookies) answered before the kernel or the VM is involved means forged handshakes never cost your server anything. Ask where it runs.
5. Is there a Layer 7 layer?
Network filters cannot see HTTP. Botnets sending valid requests, credential stuffing and scanners pass straight through them. If you run a website, an API or a panel, ask whether there is an L7 option, such as a filtering reverse proxy, and whether you can see why an address was banned.
6. Is attack traffic billed?
On metered plans, a flood can become a bill. Ask whether attack traffic counts toward your transfer, and whether “unmetered” has a fair-use clause that an attack could trigger.
7. Where does the filter run?
Filtering at a far-away scrubbing centre adds latency to every packet. Filtering in the host’s network driver, or at the edge of the provider’s network, adds almost none. For games and real-time traffic, ask how much latency the protection adds, and how they measured it.
8. Can they show you numbers?
Marketing pages quote capacities in terabits. Ask for something you can check: how the filter was tested, what it dropped, and whether real clients kept working during the test. A provider that measured its protection will tell you how.
How we answer them
- Always on, in the network driver of every host.
- Capacity is the port in front of the host; we tell you its size, and what happens above it, before you buy.
- UDP: verified-only game ports with per-source limits on our Game VPS.
- TCP: SYN challenge in XDP on every listening port.
- L7: our hosted proxy with a guard that bans in under a second.
- Attack traffic is never billed.
- Latency: a few hundred nanoseconds per packet.
- Numbers: published with the method on the technology page.