Best DDoS Protected Rust Server Hosting
For wipe day, 200-pop servers and surviving the query floods aimed at your tick rate. How Rust servers get attacked, what to protect and which hosts hold up.
Rust-Specific Attack Patterns
Rust servers face two problems most games don't. The first is Steam query (A2S) floods against the query port: cheap to launch, invisible to bandwidth graphs, and devastating to server FPS and tick rate. The second is wipe-day timing: competitors and griefers hit you in the 30 minutes after a wipe, when hundreds of players are joining at once and an outage sends them straight to the next server in the browser.
Volumetric UDP floods round it out. Because Rust is UDP-based and latency-sensitive, a host that “mitigates” by adding 50 ms of scrubbing detour is almost as bad as one that null-routes.
Ports to Protect
| Service | Default port | Protocol |
|---|---|---|
| Game | 28015 | UDP |
| Query (server browser) | 28017 (server.queryport) | UDP |
| WebRCON | 28016 | TCP |
| Rust+ companion app | 28082 | TCP |
Query port is configurable; recent Rust versions separate it from the game port.
What Your Host Must Filter
- Layer 3/4 volumetric floods — UDP, SYN, amplification — absorbed upstream so the link never saturates.
- Layer 7 Steam query (A2S) filtering — answering legitimate browser queries while dropping floods aimed at the query port.
- No null-routing at the attack sizes booters actually sell (10–100+ Gbps).
- Low latency to your players — protection is wasted if the scrubbing path adds 80 ms.
Our Picks
1. KoDDoS Rust Hosting
Dedicated Rust plans tuned for high single-thread performance, A2S query filtering by default and ~1 Tbps always-on mitigation. Low-latency LA, NY and Amsterdam locations. Full review.
2. Path.net Gaming
Premium pick for high-pop competitive Rust networks with very large attack profiles. Review.
3. OVH Game
Cheapest real mitigation for EU/Canada Rust servers if you can live with self-service support and OVH's game firewall templates. Review.
Server Specs by Size
| Size | CPU | RAM | Notes |
|---|---|---|---|
| 50 pop | 4 cores, high single-thread | 16 GB | Protected VPS possible |
| 100 pop | 6 cores | 32 GB | Dedicated recommended |
| 200+ pop / modded | 8+ cores (E-2388G / EPYC 4564P) | 64 GB | NVMe RAID |
Hardening Checklist
- Keep WebRCON (28016) closed to the public — allow-list your admin IPs.
- Use a strong RCON password and rotate it after staff changes.
- Keep Oxide/Carbon plugins updated; abandoned plugins are a common DoS vector.
- Schedule wipes with your host so mitigation staff know when peak risk is.
- Avoid publishing the raw IP outside the server browser; use a domain.
Where to Host
EU Rust communities are best served from Amsterdam; US servers from New York (East) or Los Angeles (West). Oceania and Asia players are better on a dedicated regional server than on a protected US one. For the general provider ranking see best DDoS protected game server hosting; for European communities, game servers in Europe.
