Minecraft DDoS protectionYour Minecraft network, still online after the flood.

Minecraft servers are a favourite target for cheap floods. Templass scrubs floods in Frankfurt and sends clean player traffic to the host you already use.

Why Minecraft servers are a target

A public Minecraft server is easy to find. It sits on a server list, its address is in every player's client, and anyone with a grudge can rent a flood for less than a rank costs. A few minutes of downtime during peak hours is enough to send players to another network.

The attacks themselves are rarely clever. They are UDP floods, amplification and TCP floods that fill the uplink or exhaust connections before your proxy or plugins ever see a packet. No plugin can fix that. The traffic has to be dropped upstream.

How the protection works

Players join through an address Templass announces on AS208743. All traffic for that address lands at the Templass edge in Equinix FR5, Frankfurt, where Layer 3 and Layer 4 floods are dropped or limited. What is left, your real players, is forwarded to your server.

The usual handoff for Minecraft is a GRE tunnel to your existing machine. Your host does not change, your world files stay where they are, and you can start without ordering anything in a data center.

Scrubbing is always on. There is no on-demand mode that waits for an attack to be detected, so players do not get kicked while protection spins up.

Setting it up for Java and Bedrock

  1. Request a quote with your peak clean Mbps and GRE as the connection type.
  2. Bring up the tunnel with the endpoint and inner addresses Templass provisions.
  3. Open your ports under Port requests. Java usually needs TCP, Bedrock needs UDP, and a network running both needs both.
  4. Move DNS and SRV records to the protected address once the tunnel passes a test, and update any server list entries.

If you run a proxy such as BungeeCord or Velocity, protect the proxy's public address. Backend servers should not be reachable from the internet at all.

Keep the origin hidden

Protection only works if attackers cannot reach the server some other way. The most common leaks are an old A record, a forgotten subdomain, a plugin or website that exposes the host IP, and backend servers answering on a public address. Check those before you announce the move.

During an attack, open Attacks in the Panel to confirm the event is being recorded. Do not spin up a new VPS and post its IP as a quick fix. That just gives the attacker a fresh target.

Pricing that fits a server budget

You pay for the clean traffic your players actually use, measured at the 95th percentile. Attack volume is not billed. See DDoS protection pricing for the tiers and the monthly floor, or the broader game server DDoS protection page if you host other games too.

Questions

Can I keep my current Minecraft host?

Yes. Templass delivers clean traffic over a GRE tunnel to a public IPv4 address you control, so the server can stay with your current provider as long as it can terminate GRE and route the protected address through the tunnel.

Which ports do I need to open?

The ones your server actually listens on. Java Edition defaults to TCP 25565 and Bedrock to UDP 19132, but use whatever your config says. Open them in the Panel under Port requests, with Minecraft as the purpose.

Players still see my real IP. What went wrong?

Usually DNS, an SRV record or a server list still points at the origin, or the origin answers on another public interface. Move every public record to the protected address and make sure the origin is not reachable around Templass.

What does it cost for a small server?

Billing is on 95th-percentile clean Mbps, with indicative rates of €0.33 to €0.45 per Mbps and a €39 monthly floor on quiet months. Attack traffic is not billed. Send a quote request with your peak clean Mbps for an exact number.

Related

Send your edition, peak clean Mbps, and where the server lives. We reply with a quote.

Request a quote