IPv4 subnet calculatorNetwork, host range, broadcast, mask and wildcard for any IPv4 blockIPv6 subnet calculatorPrefix ranges, /64 counts, splits and a ULA prefix generatorVLSM calculatorSize subnets by host count, with AWS, Azure, GCP and OCI rulesVisual subnet plannerSplit and join blocks, label them, then share or export the planCIDR and IP range calculatorTurn any start and end address into the fewest CIDR blocksSupernet and route summarySummarise networks into one route or merge them exactlyWildcard mask calculatorACL wildcards, matched ranges and ready Cisco linesSubnetting practiceExam-style questions, checked instantly with the working shownSubnet mask cheat sheetEvery prefix from /0 to /32 with mask, wildcard and hostsIPv6 cheat sheetPrefix sizes, address types and the reserved rangesGuidesHow subnetting works, explained with worked examples

Private IP address ranges and how to choose one

Three ranges are set aside for private networks, plus a fourth for carrier NAT. Here is how big each one is, what else is reserved, and how to choose a range that will not clash later.

Updated Nov 20, 20267 min readFigures tested
Address space that never routes on the internet 10.0.0.0/816,777,216RFC 1918172.16.0.0/121,048,576RFC 1918192.168.0.0/1665,536RFC 1918100.64.0.0/104,194,304RFC 6598 CGNAT Bar length on a log scale. Counts are total addresses.
Key facts
  • 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 are private (RFC 1918).
  • 100.64.0.0/10 is shared space for carrier-grade NAT (RFC 6598).
  • Private addresses are not routed on the public internet.
  • Pick an unusual range to avoid clashes with home networks over VPN.
CIDR and IP range calculator

Turn any start and end address into the fewest CIDR blocks

Open the tool

The three RFC 1918 ranges

RFC 1918, from 1996, reserves three blocks for use inside private networks. Anyone may use them without asking a registry, and routers on the public internet drop them.

RangeCIDRAddressesOld class equivalent
10.0.0.0 to 10.255.255.25510.0.0.0/816,777,216One class A
172.16.0.0 to 172.31.255.255172.16.0.0/121,048,57616 class B
192.168.0.0 to 192.168.255.255192.168.0.0/1665,536256 class C
172.16.0.0/12 ends at 172.31.255.255. Addresses like 172.32.0.1 are public. This is one of the most common mistakes in firewall rules.

Carrier-grade NAT: 100.64.0.0/10

RFC 6598 set aside 100.64.0.0/10 (100.64.0.0 to 100.127.255.255, 4,194,304 addresses) for internet providers that put customers behind a second layer of NAT. It exists so that providers do not have to use RFC 1918 space, which would clash with the customer's own network.

You will see it on mobile networks and some broadband connections, and some overlay VPNs use it inside their own networks. Treat it as not yours to use on a corporate LAN.

Other special ranges

RangePurposeDefined in
127.0.0.0/8Loopback, never leaves the hostRFC 1122
169.254.0.0/16Link-local, self-assigned when DHCP failsRFC 3927
192.0.2.0/24Documentation (TEST-NET-1)RFC 5737
198.51.100.0/24Documentation (TEST-NET-2)RFC 5737
203.0.113.0/24Documentation (TEST-NET-3)RFC 5737
198.18.0.0/15Network benchmarkingRFC 2544
224.0.0.0/4MulticastRFC 5771
240.0.0.0/4ReservedRFC 1112

The IPv4 calculator labels every address with its range, so you can paste an address and see straight away whether it is private, shared, reserved or public.

Choosing a range that will not clash

Address clashes show up when two networks join: a VPN from a home network, a merger, or a link to a partner. Most home routers use 192.168.0.0/24 or 192.168.1.0/24, and many use 10.0.0.0/24. If your office uses the same range, remote users cannot reach it over VPN.

  • Avoid the defaults. Skip 192.168.0.x, 192.168.1.x and 10.0.0.x for anything people will reach remotely.
  • Pick a random second octet in 10/8. Something like 10.137.0.0/16 is unlikely to match anyone else.
  • Plan the whole block. Reserve a /16 per site and carve it with the subnet planner, so sites summarise cleanly.
  • Check overlaps before you build. The overlap checker tells you if two ranges collide.

Private ranges in the cloud

Cloud VPCs and VNets use the same RFC 1918 ranges, so the clash rules matter even more. A VPC peered with another VPC, or connected back to the office, must not overlap with either. AWS allows VPC blocks between /16 and /28, and many teams give each environment its own /16 from 10/8. See cloud reserved IPs for how subnets inside a VPC are sized.

The IPv6 equivalent

IPv6 has unique local addresses, fd00::/8 in practice, defined in RFC 4193. Instead of everyone sharing the same few ranges, each network picks a random 40-bit ID, so clashes are very unlikely. Generate one with the ULA generator.

How we check this page

Every figure on this site comes from the same calculation engine as the tools, and that engine is tested on each build against more than 6,600 cases generated by Python's standard ipaddress module. Rules are taken from the RFCs and vendor documents listed under Sources. Last reviewed November 20, 2026.

Sources

  1. RFC 1918: Address Allocation for Private Internets
  2. RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space
  3. RFC 6890: Special-Purpose IP Address Registries
  4. RFC 5737: IPv4 Address Blocks Reserved for Documentation
  5. IANA IPv4 Special-Purpose Address Registry