DDoS Protected TeamSpeak & Mumble Hosting
Voice servers are small, cheap and attacked constantly — usually by someone who was just kicked from a channel. Here is what to protect on TeamSpeak 3 and Mumble and which hosts keep voice clear during floods.
How Voice Servers Get Attacked
Voice is the most latency- and jitter-sensitive traffic you can host: a flood that a web server shrugs off turns TeamSpeak into robot noise. Attacks are usually UDP floods on the voice port from cheap booters, plus ServerQuery abuse on TeamSpeak's query ports (connection floods and login brute-forcing) and file-transfer port abuse. Gaming clans, esports teams and streamer communities are the usual targets, often right before a match.
Ports to Protect
| Service | Default port | Protocol |
|---|---|---|
| TeamSpeak 3 voice | 9987 | UDP |
| TeamSpeak file transfer | 30033 | TCP |
| TeamSpeak ServerQuery (raw / SSH / HTTP) | 10011 / 10022 / 10080 | TCP |
| Mumble (voice + control) | 64738 | TCP + UDP |
Keep ServerQuery ports allow-listed to your bots and admin IPs.
What Your Host Must Filter
- Layer 3/4 volumetric floods — UDP, SYN, amplification — absorbed upstream so the link never saturates.
- Voice-aware UDP filtering that drops floods without adding jitter, plus rate limits on TeamSpeak ServerQuery.
- 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
Protected VPS from $14.99/mo comfortably runs TeamSpeak or Mumble for hundreds of users, with filtering for voice and query ports and six low-latency regions. Review.
2. JavaPipe
Cheapest real L4 mitigation for small clan voice servers. Review.
3. OVH
Budget EU option behind OVH's anti-DDoS backbone. Review.
Server Specs by Size
| Size | CPU | RAM | Notes |
|---|---|---|---|
| Up to 50 users | 1 vCPU | 1 GB | Tiny footprint |
| 50–500 users | 1–2 vCPU | 2 GB | Bandwidth matters more than CPU |
| Multiple virtual servers | 2–4 vCPU | 4 GB | One protected IP, many instances |
Hardening Checklist
- Allow-list ServerQuery (10011/10022/10080) to your bots and admin IPs.
- Use a server password or privilege keys for private communities.
- Enable anti-flood settings in TeamSpeak and limit connections per IP.
- Run music and moderation bots from the same protected network.
- Use a domain (and SRV record) so you can move IPs after a leak.
Where to Host
Put the server where most speakers are: Amsterdam for EU clans, New York or Los Angeles for North America. For the general provider ranking see best DDoS protected game server hosting; for European communities, game servers in Europe.
