The reserved IPv4 blocks, complete

These are all the IPv4 ranges that aren't publicly routable on the internet. Memorizing the top three (RFC 1918) covers 95% of real-world use, but the other rows occasionally bite you.

RangeCIDRRFCUse
10.0.0.0 – 10.255.255.25510.0.0.0/8RFC 1918Private — large networks
172.16.0.0 – 172.31.255.255172.16.0.0/12RFC 1918Private — mid-size networks
192.168.0.0 – 192.168.255.255192.168.0.0/16RFC 1918Private — home and small office
100.64.0.0 – 100.127.255.255100.64.0.0/10RFC 6598CGNAT (carrier-grade NAT)
127.0.0.0 – 127.255.255.255127.0.0.0/8RFC 1122Loopback (localhost)
169.254.0.0 – 169.254.255.255169.254.0.0/16RFC 3927Link-local (APIPA — DHCP failure)
0.0.0.0 – 0.255.255.2550.0.0.0/8RFC 1122"This network" — unspecified source
224.0.0.0 – 239.255.255.255224.0.0.0/4RFC 5771Multicast
240.0.0.0 – 255.255.255.254240.0.0.0/4RFC 1112Reserved (Class E)
255.255.255.255255.255.255.255/32RFC 919Limited broadcast
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24RFC 5737TEST-NET (use in documentation)
198.18.0.0 – 198.19.255.255198.18.0.0/15RFC 2544Benchmark testing

RFC 1918 — the three you'll actually use

For private networks behind NAT, pick from these three. The choice usually comes down to:

VPN tip

If you ever VPN into your home network from a coffee shop, hotel, or relative's house, your home subnet will conflict with theirs if both use 192.168.1.0/24. This is the #1 cause of "VPN connects but I can't reach anything" issues. Pick something less common at home (10.42.0.0/24, 172.20.0.0/24, etc.) to dodge the conflict.

CGNAT (100.64.0.0/10) — why your router shows a "weird" IP

If your home router's WAN side shows an address starting with 100.64–100.127, your ISP is using CGNAT. They're sharing one public IP across many customers. Implications: