Demystifying IPv4 CIDR and Subnet Masks: The Cloud & DevOps Engineer's Guide

🌐 Setting Up VPCs and Subnets Without Headache

When provisioning an AWS VPC, GCP Subnet, or Azure Virtual Network, you are immediately asked to specify a CIDR block like:

text

10.0.0.0/16 or 192.168.1.0/24

If you miscalculate:

You might allocate too few IP addresses, running out of space for Kubernetes pods or ECS containers.
Or you overlap VPC subnets, preventing VPC peering or VPN site-to-site tunnels from routing properly.

An IPv4 address consists of 32 bits divided into four 8-bit octets (e.g. 192.168.1.1).

The slash suffix (/24) indicates how many bits belong to the Network Prefix, leaving the remaining bits for Usable Host Addresses:

Bits for Hosts = $32 - \text{Prefix}$
Total IP Addresses = $2^{(32 - \text{Prefix})}$
Usable Host Addresses = $2^{(32 - \text{Prefix})} - 2$ (subtracting Network ID and Broadcast IP)

|---|---|---|---|---|

| `/32` | 255.255.255.255 | 1 | 1 (Single Host) | Direct Firewall Whitelist / Elastic IP |

| `/28` | 255.255.255.240 | 16 | 14 Hosts | Small Database Subnet |

| `/24` | 255.255.255.0 | 256 | 254 Hosts | Standard Application Cluster Subnet |

| `/20` | 255.255.240.0 | 4,096 | 4,094 Hosts | Large Kubernetes Node Subnet |

| `/16` | 255.255.0.0 | 65,536 | 65,534 Hosts | Full Enterprise AWS VPC Range |

Calculate full network ranges with the [Omnikite IP Subnet Calculator](https://omnikite.vercel.app/tools/developer/ip-subnet-calculator):

🔍 Complete Range Breakdown: Calculates Network Address, Broadcast Address, First Usable IP, Last Usable IP, Subnet Mask, and Wildcard Mask.
🔟 Binary Bit Representation: Visual breakdown of network vs. host bits.
⚡ Zero Network Calls: Runs in local browser memory with sub-millisecond calculation.