Game Hosting

Monsoon Special: save up to 35% on Minecraft & game server plans Up to 35% off games

Claim offer
Understanding the Network Tab: Ports and Allocations
Sep 30, 2026 8 views

Understanding the Network Tab: Ports and Allocations

What an allocation actually is, what extra ports are used for, and how to manage them from the Network tab.

Understanding the Network Tab: Ports and Allocations

Your plan includes a set number of network allocations โ€” each one a specific IP:port combination your server can bind to. The Network tab is where you see and manage them.

What's an Allocation, Really

An allocation is one IP address + port pairing reserved for your server specifically โ€” nobody else's server can use that exact combination while it's assigned to you. Your primary allocation is your server's main connection address (what players/clients connect to); any additional ones are extra ports for secondary services.

What Extra Allocations Are Actually For

  • A proxy alongside your main server โ€” Velocity or BungeeCord needs its own port separate from the backend Minecraft server(s) it routes to.
  • A query port for external monitoring tools or server-list sites that check status on a separate port from the game connection itself.
  • Voice server or companion services โ€” a TeamSpeak/Mumble instance, a bot, or a web-based map viewer running alongside your main game server.
  • Multiple game instances on one service โ€” if your plan and game support it, a second port lets a second server process bind without conflicting with the first.

Using the Tab

  1. Open the Network tab on your service.
  2. You'll see your primary allocation (marked as such) and any additional ones you have.
  3. Some eggs let you set a friendly alias/note per allocation so you remember what each one is for once you have more than one.
  4. If your plan supports it and you have unused ports available, you can add a new allocation directly from this tab; otherwise, buy more via the port allocation add-on.

Connecting To a Non-Primary Port

Your connection address for anything beyond the primary port is the same IP with the different port appended โ€” e.g. yourserver.ip:PORT. Whatever software is meant to listen on that port needs to be configured to actually bind to it (most eggs/startup configs let you specify which allocation a given process should use).

A Note on IP vs Domain

The IP:port shown here is your real connection address. If you've pointed a custom subdomain at your server (see our subdomain guide), that's just a friendlier name resolving to the same underlying IP and port โ€” the allocation itself doesn't change.

Most single-server setups never need more than the one included allocation โ€” this tab really only matters once you're running a proxy, a second process, or external tooling that needs its own dedicated port.

Did you find this blog helpful?

found this blog helpful.