IP Subnet & CIDR Calculator
Comprehensive IPv4 subnetting utility: calculate network addresses, broadcast addresses, usable host ranges, wildcard masks, and binary bit masks with one click.
IPv4 Address & CIDR Prefix
Common CIDR Subnet Cheat Sheet
| CIDR | Subnet Mask | Total Addresses | Usable Hosts | Typical Use Case |
|---|---|---|---|---|
/32 | 255.255.255.255 | 1 | 1 | Single host / Loopback |
/30 | 255.255.255.252 | 4 | 2 | Point-to-point router links |
/28 | 255.255.255.240 | 16 | 14 | Small office / DMZ segment |
/24 | 255.255.255.0 | 256 | 254 | Standard LAN / Wi-Fi network |
/20 | 255.255.240.0 | 4,096 | 4,094 | Cloud VPC Subnet (AWS / GCP) |
/16 | 255.255.0.0 | 65,536 | 65,534 | Enterprise Campus / Large VPC |
/8 | 255.0.0.0 | 16,777,216 | 16,777,214 | Tier 1 ISP / National Carrier |
Comprehensive Guide to IPv4 Subnetting & Network Architecture
Every device connected to an Internet Protocol version 4 (IPv4) network is assigned a 32-bit logical address, traditionally represented as four decimal octets separated by dots (e.g., 192.168.1.100). In binary, this represents a string of 32 ones and zeros.
An IP address is split into two logical segments: the Network Portion (which identifies the physical network segment where the device resides) and the Host Portion (which uniquely identifies the specific interface or computer on that network). The Subnet Mask acts as a binary stencil that informs routers and network cards exactly where the network portion ends and the host portion begins.
The Bitwise Mathematics Behind Subnet Calculation
Routers perform a fundamental Bitwise AND logic operation between the incoming destination IP address and the configured Subnet Mask to determine whether a packet should be delivered locally or forwarded to a default gateway:
Because the host portion contains 8 bits, the total addresses are 2^8 = 256. Subtracting the network address and broadcast address leaves 254 usable host addresses (from 192.168.1.1 to 192.168.1.254).
Subnetting in Cloud Environments (AWS, Azure & Google Cloud)
Cloud infrastructure requires disciplined IP planning to ensure seamless peering between VPCs, Kubernetes clusters, and on-premises corporate datacenters:
AWS Reserved IPs
Always account for the 5 IP addresses AWS reserves in each subnet (e.g. in a /24 subnet with 256 total addresses, AWS only allows 251 usable EC2 instances).
Non-Overlapping CIDRs
Never use overlapping CIDR blocks across multiple VPCs or corporate VPNs. Once allocated, changing a VPC's primary CIDR range requires rebuilding the entire network.
Kubernetes Pod Sizing
In Amazon EKS (using AWS VPC CNI), every Kubernetes pod consumes a real VPC IP address from the node's subnet. A /24 subnet can easily be exhausted by a handful of nodes running many pods.
Comprehensive CIDR Subnet Reference Table
| CIDR | Subnet Mask | Total Addresses | Usable Hosts | Typical Real-World Use Case |
|---|---|---|---|---|
/32 | 255.255.255.255 | 1 | 1 | Single host route, VPN client address, Loopback interface |
/30 | 255.255.255.252 | 4 | 2 | Legacy point-to-point router links |
/28 | 255.255.255.240 | 16 | 14 | Small office network segment, database DMZ cluster |
/24 | 255.255.255.0 | 256 | 254 | Standard office LAN, Wi-Fi hotspot subnet, AWS public subnet |
/20 | 255.255.240.0 | 4,096 | 4,094 | Enterprise department VPC, large container cluster |
/16 | 255.255.0.0 | 65,536 | 65,534 | Complete AWS VPC network root, corporate headquarters campus |
/8 | 255.0.0.0 | 16,777,216 | 16,777,214 | Tier 1 Internet Service Provider (ISP), entire Class A block |
Frequently Asked Questions
Explore Related Tools
Hand-picked utilities and calculators related to this tool.
