DDoS Protection
DDoS protection
Terabit+ scale
We do not route every location through the same protection stack. Europe runs on PletX with Aurologic failover, New York runs on GSL with Gcore failover, and Miami stays in-house because local options that make sense are limited. That split gives us better route quality, cleaner fail behaviour, and tighter control per region.
How the protection is split
Each location uses the stack that makes the most sense for that region.
Frankfurt
PletX
Aurologic failover
PletX is by far the strongest EU fit for us, with Aurologic ready as the regional fallback path.
New York
GSL
Gcore failover
GSL is our best New York option, with Gcore ready as the North America fallback path.
Miami
In-house
Local stays local
Miami stays in-house because there are not many sensible alternatives in that region that are not insanely expensive.
Why this stack is good
PletX fits EU traffic well
PletX is by far the best provider fit for our EU location. Aurologic is kept as the failover so Frankfurt still has a regional fallback path.
GSL is strong for New York ingress
GSL is our best New York provider. Gcore is kept as the North America failover so the region is not tied to a single path.
Miami stays local on purpose
Miami is in-house because the practical alternatives in that region are limited or extremely expensive. The local path stays local instead of forcing the region through a bad fit.
What players actually feel
- Attacks are handled by the region that is actually serving the player traffic.
- Routing stays cleaner because protection is not forced through one global vendor for every location.
- Minecraft traffic benefits from always-on paths instead of delayed diversion during an attack.
- Local control in Miami gives faster operational decisions when a node-specific issue needs intervention.
Miami is intentionally local. That part is about operational control and keeping filtering close to the server layer, not about outsourcing every location to the same upstream mitigation vendor.
Protected by default,
without routing everything the same way
Purpify uses region-specific protection so the EU, New York, and Miami locations can each keep the mitigation path that best matches their traffic and operational model.