DDoS Protected Discord Bot Hosting
Discord bots rarely get attacked through Discord — they get attacked through everything around them: web dashboards, interaction endpoints, webhooks and leaked VPS IPs. Here is how to keep a bot and its dashboard online.
What Actually Gets Attacked
A bot connected to Discord's gateway makes an outbound connection, so Discord itself shields it from most traffic. The exposure is elsewhere: the web dashboard on the same VPS, an HTTP interactions endpoint if you use one, webhook receivers for Patreon/Top.gg/Stripe, and the VPS IP itself if it ever leaks through a dashboard, an image proxy or an error message. Once the IP is known, a volumetric flood takes down the gateway connection too and the bot goes offline in every server at once.
Ports to Protect
| Service | Default port | Protocol |
|---|---|---|
| Gateway (outbound) | 443 | TCP outbound |
| Dashboard / API | 80 / 443 | TCP |
| Interactions & webhooks | 443 | TCP |
| SSH | 22 (move it) | TCP |
What Your Host Must Filter
- Layer 3/4 volumetric floods — UDP, SYN, amplification — absorbed upstream so the link never saturates.
- HTTP flood (Layer 7) filtering for dashboards, interaction endpoints and webhook receivers.
- No null-routing at the attack sizes booters actually sell (10–100+ Gbps).
- Low latency to your players — protection is wasted if the scrubbing path adds 80 ms.
Our Picks
1. KoDDoS VPS
From $14.99/mo with Layer 7 HTTP filtering on by default — enough to run the bot, its database and a dashboard on one protected IP. Six regions; Amsterdam or New York sit close to Discord's infrastructure. Review.
Get a KoDDoS VPS for your bot →
2. JavaPipe VPS
From $3.99/mo with real Layer 4 mitigation — fine for small bots without a public dashboard. Review.
3. Split setup
Run the bot on a cheap private VPS and only the dashboard on a protected IP or behind a reverse proxy.
Server Specs by Size
| Size | CPU | RAM | Notes |
|---|---|---|---|
| Small bot (<100 servers) | 1 vCPU | 1–2 GB | Any protected VPS |
| Mid bot (1k–10k servers) | 2 vCPU | 4 GB | Add Redis cache |
| Large / sharded bot | 4–8 vCPU | 8–16 GB | Separate DB and dashboard |
Hardening Checklist
- Never reveal the VPS IP: proxy images, avoid raw-IP links, sanitise error messages.
- Put the dashboard behind a protected IP or reverse proxy; allow only proxy ranges on the origin.
- Verify signatures on interaction endpoints and webhooks and rate-limit them.
- Move SSH off port 22 and use keys only.
- Keep the bot token out of the dashboard server if they are on separate machines.
Where to Host
Discord's gateway is globally distributed; US-East and Amsterdam both work well. Choose the region closest to your database and dashboard users. For the general provider ranking see best DDoS protected game server hosting; for European communities, game servers in Europe.
