Private IP ranges

The three private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16. RFC 1918 sets them aside, and they aren't routed on the public internet. For a cloud network, take a random /16 from 10.0.0.0/8: home routers and Docker already crowd the other two.

What are the three private IP ranges?

Block
First
Last
Subnet mask
Addresses
Old class
10.0.0.0/8
10.0.0.0
10.255.255.255
255.0.0.0
16,777,216
A
172.16.0.0/12
172.16.0.0
172.31.255.255
255.240.0.0
1,048,576
B
192.168.0.0/16
192.168.0.0
192.168.255.255
255.255.0.0
65,536
C

The class names are leftovers from before CIDR. The middle block is 16 old class B networks in a row, so it's a /12, not a /16.

Is this IP address private?

The table answers most cases. These three are easy to get wrong:

  • 172.16.1.1 is private. So is every address up to 172.31.255.255.
  • 172.32.0.1 is public. It sits just past the end of 172.16.0.0/12.
  • 100.64.0.1 isn't private either. It's in the carrier block in the next table.

For any other address, the CIDR calculator tells you which range it's in.

What other IP ranges aren't public?

A few more blocks stay off the public internet. You'll see them in configs and logs, but only one of them is meant for numbering your own network, and it's IPv6.

Range
What it's for
Number a network from it?
100.64.0.0/10
Shared address space for carrier-grade NAT (RFC 6598).
No.
169.254.0.0/16
Link-local. Routers must not forward it (RFC 3927).
No.
127.0.0.0/8
Loopback: a machine talking to itself.
No.
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, 198.18.0.0/15
Examples in documentation (RFC 5737) and network benchmarking (198.18.0.0/15).
No.
fd00::/8
IPv6 unique local addresses: fc00::/7 with the local bit set (RFC 4193).
Yes, for IPv6: fd plus a random 40-bit ID gives you a /48.

Where do Docker, Kubernetes and clouds already sit?

You know the three ranges. The trouble is that common software and clouds already claim the obvious parts of them.

Range
What's there
Matters if you
Docker's default pools for new networks: every /16 from 172.17 to 172.31. The default bridge is usually 172.17.0.0/16.
Run Docker on a machine in the network
192.168.0.0/16, in /20s
More of Docker's default pools
Run Docker on a machine in the network
10.0.0.0/8, in /24s
Docker swarm's pool for overlay networks
Run Docker swarm
10.96.0.0/12 (10.96 to 10.111)
kubeadm's default Service range
Build Kubernetes clusters with kubeadm
10.42.0.0/16, 10.43.0.0/16
k3s defaults: pods on 10.42, Services on 10.43
Run k3s
10.244.0.0/16
The pod network in Flannel's manifest
Run Flannel
192.168.0.0/16
The pod range in Calico's install manifest
Install Calico without changing it
10.8.0.0/24
OpenVPN's sample server config
Built your VPN from that sample
100.64.0.0/10
Tailscale device addresses
Use Tailscale
172.31.0.0/16, a /20 per zone
AWS's default VPC
Connect to an AWS default VPC
10.128.0.0/9 (10.128 to 10.255)
Google Cloud's auto mode subnets
Connect to a Google Cloud auto-mode VPC
10.229.0.0/16, 10.244.0.0/16, 10.245.0.0/16, 10.246.0.0/24
Reserved by DigitalOcean in every region
Run on or connect to DigitalOcean
Where defaults sit inside 10.0.0.0/8 and 172.16.0.0/12Two bars, each one private block split into /16s. In 10.0.0.0/8 (256 /16s) the shaded stretches are 10.8 for OpenVPN's sample config, 10.42 to 10.43 for k3s, 10.96 to 10.111 for kubeadm Services and 10.128 to 10.255 for Google Cloud auto mode; the rest is unshaded. In 172.16.0.0/12 (16 /16s) Docker's default pools shade 172.17 to 172.31, leaving only 172.16, and AWS's default VPC sits at 172.31.10.0.0.0/8: 256 /16s10.010.12810.25510.8.0.0/24 OpenVPN sample config10.42–10.43 k3s pods and Services10.96–10.111 kubeadm Services10.128–10.255 Google Cloud auto mode172.16.0.0/12: 16 /16s172.16172.24172.31172.17–172.31 Docker default pools172.31 AWS default VPC
Each bar is one private block on its own scale. Ranges from OpenVPN's sample config, the k3s and kubeadm docs, Google Cloud's VPC docs, Docker's networking docs and AWS's default VPC docs. Not drawn: Docker swarm's pool, which is all of 10.0.0.0/8 in /24s.

Which private range should you use for a cloud network?

Start with where other people's networks already are. In June 2025 Ben Cox counted the LAN addresses of WD Cloud NAS devices: 1,602,092 devices on 192.168.0.0/16, 149,901 on 10.0.0.0/8 and 22,132 on 172.16.0.0/12. 192.168.1.0/24 alone had 647,220.

  • Skip 192.168.0.0/16. It's where home routers put their networks by default. If your cloud network uses the same block as a teammate's home network, their VPN to it will clash with that home network. Docker's pools and Calico's install manifest sit there too.
  • Be careful with 172.16.0.0/12. Home networks barely touch it, and most that do stay in 172.16. But Docker's pools cover the other fifteen /16s. Docker tries to avoid ranges already in use on the host, and its own docs say you may still need to change its pools. AWS's default VPC sits on 172.31 too.
  • Use 10.0.0.0/8. In Ben's words, "10.0.0.0/8 is huge, and outside of many subnets, is also deserted." Docker swarm's pool is the only default that can land anywhere in it, and Google Cloud's top half only matters if you'll connect to an auto-mode VPC.

RFC 1918 says to "choose randomly from the reserved pool", so do that. Pick a /16 inside 10.0.0.0/8 at random and skip any the table says you'll run into. Don't take 10.0 or 10.1 just because they come first: first is the opposite of random. Something like 10.73.0.0/16 has the right shape, but pick your own, because an example on a public page gets copied.

Give every network you might ever connect its own /16. One of our customers built several networks on 10.1.1.0/24, then hit IP conflicts connecting one monitoring server to all of them. A /16 holds 65,536 addresses, plenty to cut into tiers, and the subnet cheat sheet lists what each tier size gives you.

Don't borrow 100.64.0.0/10 because it looks empty. It's carrier space, and RFC 6598 says anyone using it for something else is "likely to experience problems" with carrier-grade NAT service. Tailscale already lives there.

How do you plan the network on American Cloud?

Take the /16 you picked to the CIDR calculator and split it into subnets. Then create a VPC with that block as its CIDR and add a tier per subnet. Each tier takes a gateway and a netmask: for 10.73.0.0/24, that's 10.73.0.1 and 255.255.255.0. Do the picking first, since moving a network to a new block later usually means building a new one. A VPC is $12 a month, flat, and if something won't connect, our support replies in under 2 minutes.

Contact us