Lower ping for UDP games

For studios running Unity, Unreal or custom UDP game servers. Multiplayer Node puts an edge proxy close to your players and carries the long haul to your server on our route. One accelerated port per game port, no SDK, no client rewrite.

  • UDP game ports
  • Unity and Unreal
  • no SDK
  • 7-day free trial

01 / the problem

Why UDP games rubber-band on long routes

UDP does not wait for lost packets. Your netcode does the work instead: it interpolates, predicts and corrects. When packets arrive late, unevenly or not at all, players see rubber-banding, enemies that teleport and shots that do not register.

A long route across the public internet adds all three: more delay, more jitter and more places to lose packets. Traffic between Brazil and Europe typically detours through the US at 220-250ms, and a ping that swings is harder on prediction than a ping that is merely high.

Your server's address is exposed too: anyone can see which IP a game client sends its packets to. Behind Multiplayer Node, that IP is our edge, and your origin stays private.

And some of your players already pay every month for ping booster apps like ExitLag, NoPing or GearUP to get a better route. Everyone else stays on the default path.

02 / how it fits

How Multiplayer Node fits a UDP game server

Players send their packets to the nearest edge proxy over a short hop. From there, the long haul to your server runs on our route, with fewer hops to add jitter and loss.

  • Unity netcode

    Mirror, FishNet, Netcode for GameObjects: whatever carries your game's traffic over UDP. These are examples, not integrations. We forward the traffic, not the library.

  • Unreal and custom engines

    An Unreal dedicated server listens on port 7777 by default, and a custom UDP server on whatever port you choose. Each game port is one accelerated port.

  • Real player IPs

    Our edge sends each player's address with PROXY protocol v2. If your server cannot read it, mmproxy in front of it hands over the real IP, with no change to your binary.

Clients that connect by hostname need no change. A client with a hardcoded IP needs one update to connect to your hostname.

03 / setup

Set up in one afternoon

  1. 01

    Send us your origin and ports

    Tell us where your server runs and which UDP ports it listens on. We set up a hostname on our edge and send you its IPs.

  2. 02

    Point a CNAME at us

    From the hostname your clients use to the one we give you. A client with a hardcoded IP gets one update to use your hostname.

  3. 03

    Firewall the origin

    Accept only our edge IPs on your game ports. Your origin's address disappears from the public internet.

  4. 04

    Turn on PROXY protocol

    In your server if it reads PROXY protocol v2, or in mmproxy in front of it. We set it up with you.

Today we set this up with you after you request a trial. A self-serve Client Area integrated with Pterodactyl is on the way.

04 / pricing

One accelerated port per game port

You pay one accelerated port per UDP port your game listens on. A server with one game port needs 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, one port and 2 TB of traffic a month: $50 on Standard ($30 + $20), $200 on Premium ($100 + $100).

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

05 / faq

UDP questions

Which Unity netcode libraries work?

Any that carries your game's traffic over UDP to a port, such as Mirror, FishNet or Netcode for GameObjects. These are examples, not integrations.

Do I need to change my client?

Only if it has a hardcoded IP: one update to connect to your hostname. Clients that connect by hostname need no change.

Can my server see real player IPs?

Yes. Our edge sends each player's address with PROXY protocol v2. If your server cannot read it, mmproxy in front of it hands over the real IP, with no change to the binary.

Does it work for Minecraft Bedrock?

Yes. Geyser lets Bedrock players join a Java server, and our edge relays its port over TCP and UDP. The Minecraft page has the settings.