Lower ping for your Minecraft server

Multiplayer Node puts an edge proxy between your players and your Minecraft server, Java and Bedrock. Players join the nearest edge over a short hop, and the long haul to your server runs on our route. Three things set it apart: an edge in Brazil, real player IPs through PROXY protocol, and a server IP that stays private.

  • Java and Bedrock
  • edge in Sao Paulo
  • PROXY protocol
  • 7-day free trial

01 / the problem

Why players far from your server lag

If your network runs in the US or Europe and some of your players are in Brazil or elsewhere in LatAm, each of them crosses the public internet to reach you, rarely on the short route. Traffic between Brazil and Europe typically detours through the US at 220-250ms. In Minecraft that shows up as blocks that come back after you break them, late hits and rubber-banding in PvP. Brazilian networks with players in Europe have the same problem the other way round.

Then there is your server's IP: anyone who resolves the address your players type gets it.

Some of your players already pay every month for ping booster apps like ExitLag or NoPing. Only the players who pay get the better path.

02 / how it fits

A Minecraft proxy built around the route

  • An edge in Brazil

    Players in Brazil connect to our edge proxy in Sao Paulo. From there, traffic rides our routes, including Sao Paulo to Madrid over the EllaLink cable at 109.5ms on the Premium plan, against 220-250ms on the typical route through the US.

  • Real player IPs

    Your proxy sees each player's real IP through PROXY protocol, so IP bans, alt checks and per-IP limits keep working. Velocity, BungeeCord, Paper and Geyser each support it with one setting.

  • A server IP that stays private

    The address players type points at our edge, not at your host. Your firewall accepts only our edge IPs, so the only traffic that reaches your server is what we forward.

Java Edition connects over TCP, on port 25565 by default. Bedrock players join through Geyser, on its own port, 19132 by default, over TCP and UDP, and Floodgate lets them in without a Java account. Our edge relays both protocols. Your host, plugins and proxy stay as they are, and players keep the same address.

About TCPShield: our comparison of public docs, as of September 2026, lists it as Minecraft only, with no South America presence. Multiplayer Node is about the route, and works for any TCP or UDP game.

03 / setup

Set up your Minecraft network in one afternoon

  1. 01

    Send us your server's address

    Tell us where your Velocity or BungeeCord proxy, or your Paper server, listens, plus Geyser's port for Bedrock. We set up a hostname on our edge and send you its IPs.

  2. 02

    Point a CNAME at us

    From the address players type, such as play.yournetwork.com, to the hostname we give you. Players join exactly as before.

  3. 03

    Firewall the origin

    Let only our edge IPs reach your Minecraft ports. Your server's IP disappears from the public internet.

  4. 04

    Turn on PROXY protocol

    Switch it on where players connect first. The settings are below.

Real player IPs on Velocity, BungeeCord, Paper and Geyser

  • Velocity: in velocity.toml, under [advanced], set haproxy-protocol = true.
  • BungeeCord: in config.yml, set proxy_protocol: true on the listener your players connect to.
  • Paper on its own, with no proxy in front: in config/paper-global.yml, set proxies.proxy-protocol: true.
  • Geyser, for Bedrock players: in its config.yml, under advanced and then bedrock, list our edge IPs in haproxy-protocol-whitelisted-ips. Listing them turns PROXY protocol on.

If Velocity or BungeeCord sits in front of your Paper servers, turn it on in the proxy only. The backends keep the player forwarding they already use.

Once it is on, your server rejects connections that do not start with a PROXY header. That is why step 3 lets only our edge reach your server: nobody can connect straight to it with a made-up header. We switch it on together with you.

We are also starting to host Minecraft servers on our own network. If you would rather have us run the server too, tick the hosting box when you request a trial.

Today we set this up with you after you request a trial. A self-serve Client Area integrated with Pterodactyl, the panel many Minecraft hosts already use, is on the way.

04 / pricing

What a Minecraft network costs

Java Edition uses one TCP port: one accelerated port. Geyser's port for Bedrock players, TCP and UDP, is a second one.

Standard

Global coverage

  • Per accelerated port $30/month
  • Optimized path cost $0.01/GB

Premium

Direct trans-Atlantic route

  • Per accelerated port $100/month
  • Optimized path cost $0.05/GB
  • Brazil to Europe, direct Atlantic path (November 2026) 109.5ms

Worked example, Java and Bedrock, two ports and 2 TB of traffic a month: $80 on Standard ($60 + $20), $300 on Premium ($200 + $100). Java only is one port: $50 and $200.

7-day free trial. No commitment. See full pricing and how we compare.

05 / faq

Minecraft questions

Does it work with Velocity, BungeeCord and Paper?

Yes. We forward plain TCP, so any Java Edition setup works. To see real player IPs, turn on PROXY protocol wherever players connect first, with the settings above.

Can Bedrock players join?

Yes, through Geyser, with Floodgate so they need no Java account. They connect to Geyser's port over TCP and UDP, and our edge relays both, with PROXY protocol so Geyser sees their real IPs.

My server is in Europe and my players are in Brazil. What changes?

Players in Brazil join our Sao Paulo edge, and the Atlantic crossing runs on the Premium route: 109.5ms from Sao Paulo to Madrid over EllaLink, against 220-250ms on the typical route through the US.

How do I go back to my old setup?

Turn PROXY protocol off, open your firewall again and delete the CNAME. Players are back on the old route in minutes.