--- title: "Private Networks" description: "Create an isolated private network (VPC), attach servers to it, and steer traffic with routes through a firewall, NAT Gateway or appliance." category: "Deployment" language: en source: https://cubepath.com/docs/products/deployment/private-networks updated: 2026-11-17 --- # Private Networks A private network (VPC) gives your servers an **isolated network** they talk over using internal IPs, with nothing exposed to the public internet. Add **routes** on top and you control where traffic for any destination goes: through a firewall VPS, a NAT Gateway, or an appliance you run yourself. ![How private networks work: isolated VLAN, private IPs, custom routes and NAT Gateway](https://cdn.cubepath.com/img/docs/products/0d7dca33-5c67-4c2a-8e70-002feaf7e119.png) It's the building block for multi-tier applications (web in front, database on a private subnet), private clusters, NAT egress, and anything where servers should reach each other without public IPs. ## Create a network ```steps ### Open the create flow On the **Private Networks** page in [my.cubepath.com](https://my.cubepath.com), click **Create Network**. ### Set name, location and range Enter a **name** (3–64 characters), choose a **location**, and set the **IP range** as a CIDR, e.g. `10.0.0.0/24`. ![Create Network form with name, location and IP range](https://cdn.cubepath.com/img/docs/products/424440c2-4c38-4e9b-ae84-f5fe58346b17.png) ### Create Confirm. The network is regional: only machines in the same location and project can join. ``` ### Rules for the range | Rule | Detail | |------|--------| | **Prefix** | Between `/8` and `/24` | | **Range** | Must sit entirely inside a **private** range, `10.0.0.0/8`, `172.16.0.0/12` or `192.168.0.0/16`. Any other range is refused | | **Address** | Must be the true network address for the prefix. `10.0.0.0` is valid for a `/24`, `10.0.0.5` is not | | **Reserved** | `.0` (network), `.1` (gateway), the broadcast address and the two addresses just below it (`.253` and `.254` in a `/24`), which the gateway itself uses. Everything else is assignable | | **Limit** | Up to **3 networks per organization** | > Tip: Pick a range that doesn't collide with anything else you'll ever need to reach, such as your office LAN, another provider's VPC, or a [Kubernetes](/docs/products/deployment/deploy-a-kubernetes-cluster) pod CIDR. Overlaps aren't rejected at creation; they show up later as traffic silently going the wrong way. ## Attach servers Open a machine's Network tab ([VPS](/docs/products/deployment/vps-network) or [baremetal](/docs/products/deployment/bm-network)) and **Attach** it. The server takes the next free internal IP from the range. - The server must be in the **same project and location** as the network, and be **active or stopped**. - **A VPS must be restarted** for the change to take effect. Baremetal applies the switch configuration in the background, but you still have to configure the VLAN inside the OS. > Note: "Attached but they can't reach each other" is almost always a VPS that hasn't been restarted since attaching. ## Routes By default a network only knows how to reach its own CIDR. A **route** tells it to send traffic for some other destination through a next hop you choose. Add one from the network's **Routes** tab with **Add route**. | Field | Meaning | |-------|---------| | **Destination CIDR** | The target CIDR, e.g. `0.0.0.0/0` (everything) or `192.168.50.0/24` | | **Target type** | What the next hop is: an IP, a VPS, or a baremetal server | | **Gateway IP** / **Target resource** | The next hop itself: an address inside the network (for an IP), or the server (for a VPS or baremetal) | Typical uses: send all outbound traffic through a firewall VPS, or route a remote subnet through an appliance's internal address. ### What's allowed - The destination **can't be the network's own CIDR** (that's already connected) and can't sit in a reserved range (`0.0.0.0/8`, loopback, link-local, multicast, `240.0.0.0/4`) or inside CubePath's own public address space. A supernet like `0.0.0.0/0` is fine. A destination with host bits set is saved as its network address (`10.1.2.3/24` becomes `10.1.2.0/24`). - An **IP next hop must be inside the network's CIDR**, and can't be `.0`, `.1`, the broadcast address or the two addresses just below it. - A **server next hop must be in the same project and already attached to this network**, otherwise it's unreachable and the route is rejected. - **Routes are IPv4 only.** An IPv6 destination or next hop is refused. - Up to **30 routes per network**. The same destination can have more than one next hop (treated as equal-cost paths); only an exact duplicate is refused. > Important: Routes created automatically by a [NAT Gateway](/docs/products/deployment/deploy-a-nat-gateway) are managed for you and can't be deleted directly. Delete the gateway and its route goes with it. > Warning: A route steers where the *network* sends traffic. It does not configure the next-hop server. That box still has to be set up to forward, NAT or filter as you intend. Enabling IP forwarding is usually the step people forget. ## What it doesn't do - **It isn't a public network.** Private IPs are reachable only by your attached servers in the same location. For outbound internet from a private-only server, route through a [NAT Gateway](/docs/products/deployment/deploy-a-nat-gateway). - **It doesn't span locations.** A network lives in one location. Connect locations with a routing appliance and routes. ## Troubleshooting | Symptom | Likely cause | |---------|--------------| | "Invalid range" on create | The range isn't the network address for that prefix | | "Must be private" on create | The range is outside `10.0.0.0/8`, `172.16.0.0/12` and `192.168.0.0/16` | | "Limit reached" on create | You already have 3 networks | | Can't attach a server | It's in another project or location, or it isn't active/stopped | | Attached but no connectivity | One or both VPS haven't been restarted since attaching | | Route rejected, next hop outside CIDR or reserved for the gateway | An IP next hop must be an address within the network, and not `.0`, `.1`, the broadcast or the two addresses just below it | | Route rejected, reserved range or CubePath's address space | The destination is a reserved range or part of CubePath's own public addresses | | Route rejected, "must be attached" | The target server isn't on this network yet | | Can't delete the network | A VPS, baremetal server or NAT Gateway is still attached |