RFC 1918 Private IP Address Ranges

RFC 1918 defines three blocks of IPv4 addresses for private use — networks that are not routed on the public internet. These ranges let organizations build internal networks of any size without consuming scarce public IPv4 space, and they are the foundation of NAT, home networks, and enterprise internal addressing. For a quick reference, see the private IP ranges reference.

Built by a network engineerCalculations run locally in your browserNo signup requiredNetwork information is not transmitted to our servers

The three private ranges

RangeCIDRPrefixAddressesClassful equivalent
10.0.0.0 – 10.255.255.25510.0.0.0/8/816,777,2161 × Class A
172.16.0.0 – 172.31.255.255172.16.0.0/12/121,048,57616 × Class B
192.168.0.0 – 192.168.255.255192.168.0.0/16/1665,536256 × Class C

Key rules

  • Not globally routable. ISPs filter RFC 1918 sourced from or destined to the public internet.
  • Reusable. Any organization can use these ranges — they are not unique globally.
  • Free. No registration or allocation required.
  • Requires NAT to reach the public internet (source NAT / PAT).

Choosing a range by scale

Network sizeRecommended rangeTypical use
Large enterprise / campus10.0.0.0/8Thousands of subnets, multi-site
Mid-size org172.16.0.0/12Regional network, branch offices
Small office / home192.168.0.0/16Single site, flat or few VLANs
Carrier-grade NAT100.64.0.0/10 (RFC 6598)ISP shared address — not RFC 1918

Subnetting the 10.0.0.0/8 block

The /8 block is enormous. A common enterprise scheme uses /16 regional blocks carved into /24 VLANs:

10.0.0.0/16   — Site A (HQ)
  10.0.0.0/24   — Users VLAN 10
  10.0.1.0/24   — Servers VLAN 20
  10.0.2.0/24   — Voice VLAN 30
  10.0.254.0/24 — Management VLAN 99

10.1.0.0/16   — Site B (Branch)
10.2.0.0/16   — Site C

This gives 256 /16 site blocks, each with 256 /24 VLANs — room for 65,536 VLANs total. Use the VLAN sizing calculator to plan.

NAT configuration

Cisco IOS PAT (overload)

interface GigabitEthernet0/0
 ip address 10.0.0.1 255.255.255.0
 ip nat inside
!
interface GigabitEthernet0/1
 ip address 203.0.113.2 255.255.255.248
 ip nat outside
!
ip nat inside source list 1 interface GigabitEthernet0/1 overload
access-list 1 permit 10.0.0.0 0.0.0.255

Linux (nftables masquerade)

nft add table ip nat
nft 'add chain ip nat postrouting { type nat hook postrouting priority 100 ; }'
nft add rule ip nat postrouting oifname eth0 masquerade

Overlapping private ranges and VPNs

Because RFC 1918 addresses are reused, two organizations merging or connecting via VPN often have overlapping subnets (both use 192.168.1.0/24). Solutions:

  • NAT translation (NAT-T / twice-NAT) — translate one side's range to a non-overlapping block.
  • Re-addressing — renumber one side to a different RFC 1918 block.
  • Policy routing — route around the overlap with more-specific routes.

Other special-use ranges (not RFC 1918)

RangeRFCPurpose
100.64.0.0/10RFC 6598Carrier-grade NAT (shared)
169.254.0.0/16RFC 3927Link-local (APIPA)
127.0.0.0/8RFC 990Loopback
224.0.0.0/4RFC 1112Multicast
198.18.0.0/15RFC 2544Benchmark testing

Related guides

Technically Reviewed By

Senior Enterprise Network Engineer — 25+ years of IT and network infrastructure experience, including enterprise Cisco switching, routing, wireless, firewalls, VPN, network access control, SD-WAN, and large-scale network operations.

Last reviewed: 2026-09-02

Calculations are performed using standards-based formulas and verified against known reference values. All computation runs client-side in your browser.