The /20 subnet, explained.

The /20 subnet uses 255.255.240.0 as its subnet mask — meaning the first 20 bits of every address identify the network, and the remaining 12 bits identify the host within that network. That gives you 4,096 total addresses (4,094 usable on standard RFC math, after subtracting the network and broadcast addresses).

The wildcard mask — the bitwise inverse of the subnet mask — is 0.0.15.255. Wildcards are what Cisco access-control lists and OSPF area definitions use instead of subnet masks; the "1" bits mark "don't care" positions. For a /20, that leaves 12 don't-care host bits.

To find the network address for any IP in a /20 block, perform a bitwise AND between the IP and the subnet mask. To find the broadcast, OR the network address with the wildcard. Modern tools — like our subnet calculator — do this in microseconds, but the underlying mechanics are straightforward binary arithmetic.

A /20 holds 4,096 addresses. AWS uses /20 as a default suggestion for VPC sizing — it gives you 16 /24 subnets across availability zones with plenty of growth room. Also a typical regional cloud allocation.

Cloud-provider quirks matter at every prefix size: AWS and Azure reserve 5 IPs per subnet, GCP reserves 4, and OCI reserves 3. So a /20 on standard RFC math gives you 4,094 usable hosts, but on AWS or Azure that drops to 4,091. The capacity-planning gap bites hardest at small prefixes (a /28 has 14 usable on paper, only 11 on AWS) but exists at every size. Our cloud-aware calculator applies the right math automatically.