Game 4
A Minecraft or Rust server for a small community.
€122 billed yearly
- vCPU
- 2
- RAM
- 4 GB
- NVMe
- 60 GB
- Port
- 1 Gbps shared
- UDP and TCP filtering in XDP
- SYN challenge on TCP game ports
- Full root, Linux images
FiveM, Minecraft, Rust and CS2 on KVM with NVMe, behind filtering that understands game traffic: verified-only UDP ports, a SYN challenge for TCP, closed ports silent.
Game ports accept UDP only from addresses that completed a real connection, rate-limited per source. Random-source floods die in XDP before your server sees one packet.
Minecraft Java, the FiveM HTTP endpoint, RCON and txAdmin answer a cookie challenge on every new connection. Spoofed handshakes never arrive.
Ports your server does not use drop everything without an answer, and addresses that flood or scan are banned in the network card, longer on every repeat.
Monthly or yearly with 15% off. Every plan: KVM, NVMe, one IPv4, full root and game-aware DDoS filtering.
A Minecraft or Rust server for a small community.
€122 billed yearly
FiveM with resources, modded Minecraft.
€224 billed yearly
Big communities, several servers on one box.
€398 billed yearly
| Plan | Game 4 | Game 8 | Game 16 |
|---|---|---|---|
| vCPU | 2 | 4 | 6 |
| RAM | 4 GB | 8 GB | 16 GB |
| NVMe | 60 GB | 120 GB | 200 GB |
| Port | 1 Gbps shared | 1 Gbps shared | 1 Gbps shared |
| Monthly | €12 | €22 | €39 |
| Yearly | €122 | €224 | €398 |
Prices in euros, excluding VAT. Paid in Bitcoin, Monero, USDT or USDC; yearly saves 15%.
Roleplay servers attract floods from rival communities. The UDP port takes only players who connected, TCP 30120 sits behind the SYN challenge.
Java over TCP with the SYN challenge, Bedrock over UDP with verified sources. Proxies like Velocity or BungeeCord fit on the same VPS.
UDP-heavy games where a flood means rubber-banding for everyone. Filtering happens before the game's network thread sees anything.
Most DDoS protection was built for websites. It inspects TCP handshakes and HTTP requests, and it is good at both. Game servers are different: the traffic that matters is UDP, there is no handshake to check, and a single packet from a forged address looks exactly like a player's. Generic filters either let UDP floods through or block whole port ranges, which takes the game down for real players too.
Our filter treats a game's UDP port as a door that opens from the inside. When a player connects, their address is marked as verified, through the game's own TCP traffic or a completed exchange, and from then on their UDP packets pass. Packets from addresses that never connected are dropped in the network driver, so a flood from a million random addresses costs the server nothing. Verified addresses still have a per-source rate limit, so one compromised client cannot flood you either.
TCP parts of a game, such as Minecraft Java, FiveM's HTTP endpoint, RCON or txAdmin, answer a SYN challenge in XDP. Ports your server does not use answer nothing at all, and addresses that flood or probe are banned in the network card for minutes, then hours on repeat.
All of this runs in the driver of the host your VPS lives on, at a few hundred nanoseconds per packet. The full explanation, with our measurements, is in how DDoS protection works.
No question matches that. Ask us in the chat and we will answer it.