/16 CIDR Subnet Mask Calculator (255.255.0.0 — 65,534 Hosts)

Calculate /16 CIDR blocks (subnet mask 255.255.0.0, wildcard 0.0.255.255). 65,536 total IPs (256 × /24 subnets) for AWS VPCs, Kubernetes pod networks, and campus LANs.

Network Architecture Presets:
IPv4 Class:Class A
Routing Scope:Private (RFC 1918)
Subnet Mask:255.255.0.0 (0xFFFF0000)
Wildcard (Inverse) Mask:0.0.255.255
Network Address
10.0.0.0/16
Broadcast Address
10.0.255.255
Usable Hosts
65,534
Total IP Addresses: 65,536
Usable Host IP Range
10.0.0.1 — 10.0.255.254

32-Bit Binary Bitmask Architecture

IP Binary (10.0.0.0)
00001010000000000000000000000000
Mask Binary (255.255.0.0)
11111111111111110000000000000000
Network Binary (10.0.0.0)
00001010000000000000000000000000
Network / Subnet Bits: 16 bits
Host Bits: 16 bits

Subnet Hierarchical Division Matrix

/17 Subnets (2 subnets • 32,766 Usable Hosts / Subnet)
Subnet (CIDR)Usable Host RangeBroadcast
10.0.0.0/1710.0.0.1 - 10.0.127.25410.0.127.255
10.0.128.0/1710.0.128.1 - 10.0.255.25410.0.255.255
/18 Subnets (4 subnets • 16,382 Usable Hosts / Subnet)
Subnet (CIDR)Usable Host RangeBroadcast
10.0.0.0/1810.0.0.1 - 10.0.63.25410.0.63.255
10.0.64.0/1810.0.64.1 - 10.0.127.25410.0.127.255
10.0.128.0/1810.0.128.1 - 10.0.191.25410.0.191.255
10.0.192.0/1810.0.192.1 - 10.0.255.25410.0.255.255
/19 Subnets (8 subnets • 8,190 Usable Hosts / Subnet)
Subnet (CIDR)Usable Host RangeBroadcast
10.0.0.0/1910.0.0.1 - 10.0.31.25410.0.31.255
10.0.32.0/1910.0.32.1 - 10.0.63.25410.0.63.255
10.0.64.0/1910.0.64.1 - 10.0.95.25410.0.95.255
10.0.96.0/1910.0.96.1 - 10.0.127.25410.0.127.255
10.0.128.0/1910.0.128.1 - 10.0.159.25410.0.159.255
10.0.160.0/1910.0.160.1 - 10.0.191.25410.0.191.255
10.0.192.0/1910.0.192.1 - 10.0.223.25410.0.223.255
10.0.224.0/1910.0.224.1 - 10.0.255.25410.0.255.255

/16 CIDR Block (255.255.0.0) for Cloud VPCs & Kubernetes Clusters

An IPv4 /16 CIDR prefix locks the first two octets (16 network bits, binary 11111111.11111111.00000000.00000000, subnet mask 255.255.0.0) and leaves 16 host bits (2^16 = 65,536 total IPv4 addresses, or 65,534 usable hosts). In AWS, GCP, and Azure cloud networking, /16 is the recommended root VPC allocation (such as 10.0.0.0/16 or 172.31.0.0/16) because it cleanly partitions into 256 independent /24 subnets or 16 larger /20 availability-zone subnets.

Container orchestrators including Kubernetes (k8s), EKS, GKE, and Docker Swarm also rely on /16 blocks (such as 10.244.0.0/16 or 192.168.0.0/16) for cluster-wide Pod CIDR ranges, assigning each worker node its own non-overlapping /24 pod subnet.

  • 65,536 Total Addresses (256 × /24 Subnets): Spans from X.Y.0.0 (network ID) through X.Y.255.255 (broadcast), providing 65,534 usable host addresses.
  • Cloud VPC Tiering Pattern: Carve a 10.0.0.0/16 VPC into /20 public/private AZ subnets (4,096 IPs each) while keeping spare /24 blocks for transit gateways and RDS/ElastiCache clusters.

Preventing RFC 1918 Peering Overlaps Across Multi-Region /16 VPCs

When designing multi-account or multi-region cloud topologies interconnected via AWS Transit Gateway, VPC Peering, or IPSec/WireGuard site-to-site VPNs, every /16 VPC must occupy a unique second octet inside the 10.0.0.0/8 RFC 1918 private space (for example: 10.10.0.0/16 for us-east-1 production, 10.20.0.0/16 for eu-west-1 production, and 10.30.0.0/16 for staging). Leaving everyone on the default 10.0.0.0/16 block prevents BGP route propagation between peered networks.

Inside each /16 supernet, BGP and OSPF area border routers can summarize all 256 internal /24 VLANs into a single /16 summary route advertisement, dramatically shrinking core routing tables and isolating link-state flaps.

  • Non-Overlapping 10.X.0.0/16 Allocation Plan: The 10.0.0.0/8 private block holds 256 distinct /16 networks (10.0.0.0/16 through 10.255.0.0/16) for conflict-free VPC peering.
  • Route Summarization & Wildcard 0.0.255.255: Aggregates 256 contiguous /24 routes into a single /16 prefix entry in BGP, OSPF, and enterprise firewall rulebases.

Practical Real-World Use Cases

Platform and network teams allocate /16 supernets when designing long-lived cloud and container topologies:

  • Terraform Multi-Account AWS VPC IPAM Allocation: Assign distinct 10.X.0.0/16 supernets per environment and region (Prod, Staging, Shared Services) so Transit Gateway peering never hits overlapping CIDR conflicts.
  • Kubernetes Pod & Service Overlay Networks (Calico / Cilium): Size cluster-wide podCIDR blocks (e.g., 10.244.0.0/16) to support up to 256 worker nodes each receiving an isolated /24 pod slice.
  • Enterprise Campus & Data-Center OSPF Area Summarization: Summarize an entire regional campus or branch hub into a single /16 route advertisement across SD-WAN and MPLS backbones.

Frequently Asked Questions

How many /24 subnets fit inside a single /16 CIDR block?

Exactly 256 subnets of size /24 fit inside one /16 CIDR block (2^(24 - 16) = 2^8 = 256), where the third octet (0 through 255) identifies each individual /24 subnet.

Why is /16 recommended for AWS VPCs and Kubernetes Pod CIDRs?

A /16 block (65,536 IPs) is the largest standard IPv4 CIDR block allowed for a primary AWS VPC allocation, providing ample room to allocate multi-AZ /20 subnets for autoscaling compute and Kubernetes pods without IP exhaustion.