Stay online when
someone wants you offline

Yes. RedM and FiveM both run on the Cfx.re protocol and share a dedicated UDP profile on every Shield plan, with an optional strict deep-packet inspection mode for servers taking sustained pressure. It validates the framework's own handshake, so spoofed sessions and join floods are dropped at our edge before they reach your tickrate.

Usually, yes. Two of our filters are deliberately generic: GameNetworkingSockets, which Valve built, and Steam Query, the A2S protocol behind most server browsers. Between them they cover a wide slice of the Source, Unreal and Unity world. We can have never heard of your game and still recognise how it talks. Where the generic pass is too blunt, ask. We will write you a real profile, no fee and no minimum tier. The 29+ list grew exactly that way, one request at a time.

FiveM and RedM, Minecraft Java, Rust on PC and Console, DayZ:SA and ArmA III, Multi Theft Auto, San Andreas Multiplayer, alt:V, SCUM, SCP: Secret Laboratory, 7 Days to Die, Conan Exiles, Palworld, Mordhau, Battlefield 4, Call of Duty: Black Ops II on Plutonium, S.T.A.L.K.E.R., Enginefall and Hytale. TeamSpeak, WireGuard and OpenVPN have their own profiles too, since voice and tunnels get hit as often as the game itself.

Timing, mostly. A Standard VPS is reactive: an attack has to be detected before filtering engages. That is roughly a five second window where you can see packet loss or a reconnect. Shield keeps every packet crossing the scrubbing layer 24/7, so there is no detection gap to sit through. Shield also adds Layer 7, which reactive Layer 3/4 filtering cannot do at all.

Your traffic crosses the scrubbing layer whether or not anyone is attacking you, and that is the whole design. There is no switchover and no clean path versus attack path, so what you measure on a quiet Tuesday is what you get in the middle of an incident. Nothing changes shape when the traffic arrives.

More than 3 Tbps of scrubbing capacity, with our own XDP filtering in front of it. Volumetric and protocol attacks are dropped at the edge, well before they reach the node your VPS is running on.

Yes, and a fair number of customers do exactly that. The reverse proxy sits in front of your web app with a JavaScript challenge, optional CAPTCHA and JA3/JA4 bot fingerprinting. Rules are per route, so you can leave an API wide open while gating a login page. Checkout sessions ride out a Layer 7 flood and you rewrite nothing.

No. Protection attaches to your VPS IP address, so whatever is listening on that IP is covered from the moment the server boots. There is no separate hostname to point at and no SDK to install.

Included. Open a ticket with the attack signature, the affected service, or just the IP being hit. We adjust the Layer 7 rules, tighten the challenge layer, or write you a custom XDP filter. Most providers bill that as consulting. We do not, and your change never sits in a vendor queue behind someone else's support desk.

Yes, we do it regularly. Contact us with whatever logs you have and we will spec a tier and move you fast. Two things help: the target IP, and a rough idea of the traffic shape. With those we can pre-load the right profile before you cut over, so the protection is already waiting when your DNS moves.

Then mitigation can engage for the entire affected range, which means several customers at once. It is an honest limitation of shared network space and our terms name it as such. It is rare, it is externally caused, and we would rather you read it here than discover it during an incident.

All of them, equally. Every tier from Shield S to Shield Pro gets identical always-on mitigation, the full profile list and the same tuning support. Moving up a tier buys CPU, RAM and disk. It does not buy you a better class of filtering, and we are not going to sell protection back to you in slices.