Best DDoS Protected Assetto Corsa Server Hosting
For AC and ACC league servers where a 30-second flood during the race start ruins three months of championship.
Why Racing Sim Servers Get Attacked
Racing attacks are surgical, not constant. Nobody floods an empty practice server — they flood the qualifying session or the championship decider, because in sim racing a brief spike of packet loss at turn one causes a pileup that cannot be un-crashed. League admins report the same pattern every season: suspiciously timed “lag” exactly when a rival team needs a result. Jitter tolerance in sim racing is far tighter than in shooters, so even small floods that would not register elsewhere decide races here.
| Service | Default port | Protocol |
|---|---|---|
| Assetto Corsa game | 9600 | UDP + TCP |
| AC HTTP/entry list | 8081 | TCP |
| ACC game | 9231 | UDP |
| ACC TCP | 9232 | TCP |
Our Picks
1. KoDDoS
Always-on filtering (not detect-then-divert, which takes 30–60 seconds to kick in — an eternity in a race) and consistently low jitter make it the safest choice for league infrastructure. A modest protected VPS handles a full grid. Full review.
Get protected AC/ACC hosting →2. OVH
Good budget pick for EU leagues — their always-on protection has improved, and most sim racers are in Europe anyway. Review.
Spec Recommendations
- AC, 24-car grid: 2–4 cores, 4 GB RAM — the original AC server is very light.
- ACC, full 30-car grid: 4 cores at high clock, 8 GB RAM; ACC's physics-authoritative server is heavier.
- Server Manager / results processing: add 2 GB RAM if you run a web manager (Emperor, ACSM) on the same box.
League-Night Checklist
- Do not publish the server IP in public Discord channels — distribute via role-gated channel on race day.
- Keep a pre-configured backup server at a second location; swapping the entry list takes minutes, re-mitigating mid-race does not work.
- EU-based grid? An Amsterdam location keeps most of Europe under 30 ms — see protected game servers in Europe.
