Minecraft Java · Servers + proxies · TCP
Protect the entrance to your Minecraft Java network.
Keep your server, worlds and plugins. Build the protection around the public Java entry point, with the delivery to your proxy or backend checked before players switch.
Know what the protection covers
Start with the public entry point, then follow the traffic to your server. The agreed delivery must cover every endpoint the players actually use.
- Network traffic
- Upstream DDoS mitigation for the agreed entry point, before traffic reaches your server or proxy. Other exposed addresses and services need their own review.
- Java connections
- Minecraft Java connection filtering and anti-bot controls suited to the selected authentication mode. This reduces unwanted connection pressure; it is not a promise to block every bot.
- Proxy and backend
- Delivery to a Java server, Velocity or BungeeCord must preserve the intended authentication and forwarding behavior. Compatibility is verified for the actual configuration.
The platform’s upstream mitigation capacity is shared infrastructure. It is not bandwidth reserved for this game server.
The delivery path
- PlayersYour community’s usual regions and Internet providers
- Peeryx protected entryNetwork filtering and the agreed game protection
- Your existing serverYour host, resources and administration stay under your control
What we need before deployment
A short technical brief is enough to start. Share private addresses or logs through support, not in public posts.
- A Minecraft Java server or proxy you administer, with its public address and TCP port.
- Server and proxy versions, authentication mode and player-information forwarding settings.
- A backend access policy that prevents unintended direct access while preserving management and required services.
- The list of lobby/backend connections, player regions and a test window for login, server switching and reconnects.
From review to a tested connection
Describe the service
Provide the game version, host and region, public ports, existing proxy and affected player regions.
Confirm the design
Agree endpoint coverage, backend restrictions, return traffic, price and trial conditions. Keep a rollback plan.
Test before switching players
Check a fresh connection, required downloads, gameplay and reconnects. Measure latency and loss from representative networks.
A successful ping is not the acceptance test
Validate the player journey and verify that it still follows the protected entry point. Check legitimate peak traffic, the behavior of any existing proxy and the procedure for a failure or maintenance event.
Before you choose
Is this Minecraft hosting?
No. This offer protects an existing Minecraft Java service. Your game server, worlds, plugins and host remain separate.
Can I keep Velocity or BungeeCord?
These are delivery designs to review, not automatic compatibility promises. Provide versions, authentication mode and forwarding settings so the complete login and backend path can be tested.
Does anti-bot protection replace authentication?
No. Keep the intended authentication and trusted forwarding configuration. Different authentication modes provide different signals; filtering cannot make every unverified identity trustworthy.
Is Minecraft Bedrock included?
The offer described here is for Minecraft Java. Do not assume Bedrock or a protocol bridge is included; request a separate scope and compatibility check.
How is the trial validated?
Check server status, a fresh login, normal gameplay, backend or lobby switching where applicable and reconnects from representative player networks. Confirm forwarding and backend restrictions too.
Will players keep the same latency?
The entry point and backend route can change the path. Measure latency and loss from the player regions you serve before switching the public address.
Useful technical guides
Keep your server. Review the protection path.
Send the current setup to our team, or continue in your client area with this game selected. The review does not order or charge a service.
Technical guides
Plan your deployment.
Routing, tunnels and diagnostics: practical explanations to support your technical decisions.
