Private Network FAQ

What is a private network for?

It lets your instances talk over internal IPs directly — build clusters, run database replication, or wire backend services together — without using public bandwidth and more securely. See the Private network guide.

Where do I create / join a private network?

Go to Console → VPS → instance detail → Network, where you can: create a private network, join the current instance to an existing one, view its assigned internal IP, or remove the instance from it.

Who assigns the internal IP? Can I pick my own?

Internal IPs are assigned automatically by the platform (as shown on the Network page); custom assignment isn't supported yet.

I joined but can't ping the internal IP.

Check each item: both instances are in the same private network, the OS firewall isn't blocking the internal subnet, and a freshly joined instance's internal IP may take a moment to take effect (retry shortly). Still stuck? Open a ticket with both instance IDs.

Are there region requirements?

Yes. A private network generally requires instances in the same region; instances in different regions can't join the same internal network.

I bought a bundle — do I still need to set up networking?

No. Some bundles wire up the internal network automatically, so they're interconnected on delivery with no manual step.

Does using a private network affect public access?

No. The internal IP is an extra internal channel; your instance's existing public IP / access is unaffected — the two run in parallel. Dedicated servers can also join a private network to talk to your VPS instances (same region required).