How it works
When a flood of junk traffic is aimed at your server’s IP address, the network filtering detects it and drops attack traffic while passing legitimate traffic through to your server. This happens automatically. Filtering reduces the impact of an attack, but no protection can promise zero disruption. A very large or unusual attack can still cause slowdowns or brief interruptions.What is covered?
The filtering targets network- and transport-level (Layer 3 and Layer 4) floods, such as:- TCP SYN floods
- UDP floods
- ICMP (ping) floods
- Reflection and amplification attacks, for example over NTP, DNS or SSDP
What isn’t covered?
Layer 7 (application) attacks: Layer 4 filtering doesn’t inspect web requests, so it can’t stop HTTP floods from bots that imitate real browsers. If you host a public website, put it behind a reverse proxy or CDN with web application filtering, such as Cloudflare, and tune your web server’s rate limits.
If your server is under attack
- Check the Graphs tab of your server in the Billing Portal for unusual network traffic.
- Check status.flashrdp.com for a network incident.
- Open a ticket with the server, the time the problem started (in UTC) and what you see.