DDoS Protection

Every Micronode server is protected by OVH's game-grade DDoS mitigation system. Here's how it works and what it means for your server.

What is a DDoS attack?

A Distributed Denial of Service (DDoS) attack floods your server with junk traffic, often millions of fake connection requests per second, until it can't respond to real players. Game servers are a common target because downtime directly affects the player experience.

How OVH VAC works

All Micronode nodes sit behind OVH's VAC (Volumetric Attack Counter) mitigation system. Here's the flow when an attack hits:

1. Attack traffic arrives at OVH's network edge, before it reaches your server
2. VAC detects the traffic pattern as malicious within seconds
3. Attack traffic is routed to a scrubbing centre and filtered out
4. Clean, legitimate traffic continues to your server normally
5. When the attack stops, normal routing resumes automatically

This process happens automatically with no action required from you. Your server stays online during most attacks.

Game-specific protection

OVH's VAC includes specific profiles for common game protocols including Minecraft (Java & Bedrock), Rust, Source engine games, and more. This means it understands what legitimate game traffic looks like and can filter more accurately than generic protection.

What it protects against

Attack type	Protected?
UDP floods	✅ Yes
TCP SYN floods	✅ Yes
Volumetric attacks (Gbps scale)	✅ Yes
Amplification attacks (DNS, NTP, SSDP)	✅ Yes
Application-layer attacks (login spam)	⚠️ Partial: use plugins for this

If you're still experiencing disruption

Large or sophisticated attacks may cause brief mitigation delay (typically under 30 seconds) before VAC kicks in. During this window you may see lag or brief disconnects.

If disruption persists for more than a few minutes:

• Check your server console for errors. The issue may not be DDoS-related.
• Verify your server isn't running out of RAM or CPU (check the gauges in Console)
• Contact us at [email protected] with your server identifier and the time the issue started