Subnet calculator › Guides
Private IP ranges explained (10.x, 172.16.x, 192.168.x)
The three private IPv4 ranges, special ranges like CGNAT and link-local, and how to pick ranges for office and cloud networks.
The three private ranges (RFC 1918)
These ranges are never routed on the internet, and anyone can use them freely inside their own network.
| Range | Addresses | Count | Typical use |
|---|---|---|---|
10.0.0.0/8 | 10.0.0.0 - 10.255.255.255 | 16,777,216 | Large corporate networks, cloud VPCs |
172.16.0.0/12 | 172.16.0.0 - 172.31.255.255 | 1,048,576 | Mid-sized networks, Docker |
192.168.0.0/16 | 192.168.0.0 - 192.168.255.255 | 65,536 | Home and small office routers |
A common mistake: 172.32.0.1 is not private. The private range runs from 172.16 to
172.31 only.
Special ranges that are not private but matter
| Range | Name | What it means |
|---|---|---|
100.64.0.0/10 | Carrier-grade NAT | ISPs use it to put many customers behind one public IP. If your router’s WAN address is in this range, port forwarding from outside will not work. |
169.254.0.0/16 | Link-local (APIPA) | Self-assigned when no DHCP server answers. Seeing 169.254.x.x on a PC means a DHCP problem. Cloud metadata (169.254.169.254) lives here too. |
127.0.0.0/8 | Loopback | The machine itself. Usually only 127.0.0.1 is used. |
192.0.2.0/24 and two more | Documentation (RFC 5737) | Addresses for manuals and examples. 198.51.100.0/24 and 203.0.113.0/24 serve the same purpose. |
198.18.0.0/15 | Benchmarking | Reserved for network device performance testing. |
Choosing ranges for office and cloud networks
- Avoid 192.168.0.0/24 and 192.168.1.0/24: they are home router defaults, so remote workers on VPN hit overlapping ranges and routing breaks.
- Stay clear of Docker’s range: Docker starts handing out networks from 172.17.0.0/16. If your office uses 172.17.x.x,
servers may not reach office addresses. Change it with
bipanddefault-address-poolsin/etc/docker/daemon.json. - Do not overlap VPCs with each other or with on-prem: VPC peering and VPNs need non-overlapping ranges. Splitting 10.0.0.0/8 by region and environment from day one helps — for example production 10.10.0.0/16, development 10.20.0.0/16.
- Reserve Kubernetes Pod and Service ranges early: they are separate from node ranges and must not overlap the VPC.
Is my IP private?
Enter it into the subnet calculator and check "Address type": it shows private, CGNAT, public and so on. If your router’s WAN (internet) address is private or 100.64.x.x, your ISP is doing another layer of NAT.