Lower ping for TCP and WebSocket games
For studios running their own game servers over TCP or WebSocket: custom MMORPG servers, browser games, Node.js real-time servers and Unity games on a TCP transport. Multiplayer Node puts an edge proxy close to your players and carries the long haul to your server on our route, for lower latency on your multiplayer game server. No SDK, no client rewrite.
- TCP any port
- ws:// and wss://
- PROXY protocol
- 7-day free trial
01 / the problem
Why TCP games freeze on long routes
TCP delivers everything in order. When one packet is lost, everything behind it waits until that packet is sent again and arrives. Players feel it as a freeze: the world stops, then everything lands at once.
The sender only learns about the loss a round trip later, so on a long route across the public internet the freeze lasts longer, and every extra hop is one more place to lose packets. Traffic between Brazil and Europe typically detours through the US at 220-250ms.
Your server's address is the other problem. Anyone who opens the network tab of a browser game, or watches a client's connections, can see where it lives. Behind Multiplayer Node, that address 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
A TCP game server proxy that shortens the part that hurts
Each edge proxy terminates the player's TCP connection. A packet lost on the player's last mile is recovered over the short hop to the nearest edge, not across the whole route, and the long haul to your server runs on our route, with fewer hops to lose packets on.
-
WebSocket, plain or TLS
It works as a WebSocket proxy for games too: ws:// and wss:// both, with no certificate handed to us. Your TLS certificate stays on your server.
-
Any stack behind it
Custom MMORPG servers, Node.js real-time game servers built on Colyseus or Socket.IO, Unity games on Mirror's Telepathy transport. These are examples, not integrations: we forward the connection, whatever speaks TCP behind it.
-
Real player IPs
PROXY protocol if your server can read it; mmproxy, with no change to your binary; a WireGuard tunnel between us and your origin; or, for WebSocket backends, a forwarded header carrying the client address.
Clients that connect by hostname need no change: you point that hostname at us with a CNAME. A client with a hardcoded IP needs one update so it connects to your hostname instead.
03 / setup
Set up in one afternoon
-
01
Send us your origin and ports
Tell us where your server runs and which TCP ports it listens on. We set up a hostname on our edge and send you its IPs.
-
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.
-
03
Firewall the origin
Accept only our edge IPs on your game ports. Your origin's address disappears from the public internet.
-
04
Choose how you get real IPs
PROXY protocol, mmproxy, a WireGuard tunnel or a forwarded header. We help you pick one and set it up.
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 TCP port
You pay one accelerated port per TCP port your game listens on. A game with a login port and a game port needs two.
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, two ports and 2 TB of traffic a month: $80 on Standard ($60 + $20), $300 on Premium ($200 + $100).
7-day free trial. No commitment. See full pricing and how we compare.
05 / faq
TCP and WebSocket questions
Do ws:// and wss:// both work?
Yes, both, with no certificate handed to us. Your TLS certificate stays on your server.
Does my client need an update?
Only if it has a hardcoded IP. Clients that connect by hostname need no change: you point the hostname at us with a CNAME. A client with a hardcoded IP needs one update to connect to your hostname.
How does my server see real player IPs?
With PROXY protocol, if your server can read it. If not, mmproxy hands your server the real address with no change to your binary. A WireGuard tunnel and, for WebSocket backends, a forwarded header are the other options.
Why does one lost packet freeze my game?
TCP delivers in order, so a lost packet holds up everything behind it until it is retransmitted. Our edge terminates the player's connection, so a loss on the player's last mile is recovered over the short hop to the nearest edge, not across the whole route.
Do you integrate with Colyseus, Socket.IO or Mirror?
We don't need to. We forward the connection, so any server that speaks TCP or WebSocket works the same way. Those libraries are examples of what can run behind us, not integrations.