Attacks stop before they reach you
Every Apex Cloud service sits behind always-on mitigation. Hostile traffic is identified and dropped at our edge, while the players and users who belong on your server keep their session.
What happens to an attack
A live sketch of the path traffic takes through our network: profiled on arrival, matched against the baseline, and dropped at the scrubbing layer if it does not belong.
source profiled
rate + entropy
pushed to edge
clean traffic only
inspected
812 Kpps
blocked
0 pps
reached you
812 Kpps
Edge is profiling every source against the learned baseline.
Every packet is profiled
Traffic entering our network is classified by source, protocol and behaviour before it is allowed anywhere near your machine.
Anomalies surface in seconds
Rate, entropy and session patterns are compared against the baseline your server normally produces, so a flood stands out immediately.
Rules reach the edge
Matching signatures are pushed to the filtering layer, where hostile packets are dropped at line rate instead of being forwarded.
Your players never notice
Legitimate sessions keep flowing through the same path with no reconnect, no queue and no manual switch to flip.
Filtering at every layer that matters
Volumetric attacks and application-layer abuse are different problems. Both are handled before your service sees them.
Volumetric floods stop at the edge
Amplification, SYN and UDP floods are absorbed by the filtering layer in front of the network. The capacity sits with us, not with your plan, so a large attack is our problem to handle rather than yours to survive.
Application-layer abuse is matched by rule
Crash payloads and request floods aimed at the game itself are inspected against signatures written for each platform we host.
Mitigation without a latency tax
Scrubbing runs inside the same São Paulo facility as your service, so protection costs a fraction of a millisecond, not a hop across the continent.
Always on, never triggered by hand
There is no window between an attack starting and protection engaging, because nothing needs to engage. Traffic is filtered continuously, and the team is paged when an event needs a human decision.
No add-on to buy
Protection is part of the plan. There is no premium tier that unlocks it later.
No traffic threshold
Filtering is always on. You are not asked to absorb an attack before it engages.
Game-aware filtering
Rules understand FiveM, Minecraft and MTA traffic, so anti-crash rules do not break normal play.
Watched by people
Automation handles the first seconds; our team reviews anything that looks unusual afterwards.
Frequently asked questions
Protection you never have to think about
Pick a game server or a VPS and the filtering layer is already there, on the first day and every day after it.