In networking, CIDR (Classless Inter-Domain Routing) is the system we use to allocate IP addresses and group them into manageable "blocks."

Before CIDR, IP addresses were handed out in rigid, wasteful "Classes" (A, B, or C). If you needed 300 addresses, you were forced to take a Class B block with 65,000 addresses, wasting the other 64,700. CIDR fixed this by allowing us to cut the address cake into exactly the size we need.

The "Zip Code" Analogy

Think of an IP address like a house address.

• The Starting Number: This is the street.

• The Slash Number (/): This is the size of the neighborhood.

In CIDR notation (e.g., 10.0.0.0/24), the number after the slash tells the computer: "Lock the first 24 bits as the 'Neighborhood ID' and leave the rest for 'House Numbers'."

How CIDR Math Works

An IPv4 address is made of 32 bits. The number after the slash tells you how many bits are "frozen" for the network. The remaining bits are for your devices (hosts).

Pro Tip: As the number after the slash gets smaller, the number of available IP addresses gets larger.

Why Allocation Strategy Matters

In a cloud environment, you don't just pick numbers at random. You have to "allocate" with a plan.

1. Avoiding the "Overlap Trap"

The most common mistake in cloud networking is giving two VPCs the same CIDR block (e.g., both are 10.0.0.0/16). If you ever try to connect them later (VPC Peering), the traffic will get "confused" and crash.

• The Rule: Always ensure your Cloud VPCs don't overlap with each other OR your physical office network.

2. The "Five Reserved IPs"

In the cloud (specifically AWS and Azure), you don't get every IP in your block. They "tax" you 5 IP addresses per subnet for their own management:

• .0: Network Address.

• .1: VPC Router.

• .2: DNS Server.

• .3: Future Use/Reserved.

• .255: Broadcast Address.

• Result: In a /24 (256 IPs), you only have 251 usable spots for your servers.

3. T-Shirt Sizing for 2026

Modern architects use "T-Shirt Sizing" to keep things clean:

• Small (/24): Development and testing subnets.

• Medium (/22): Standard production application tiers.

• Large (/20): Heavy-duty data processing or container clusters.

How to Allocate a Block (The Workflow)

1. Define the VPC Root: Start with a large block like 10.1.0.0/16.

2. Carve Subnets: Use a function (like Terraform's cidrsubnet) to automatically chop that /16 into smaller /24 chunks.

3. Leave "Gaps": Don't use every number immediately. Leave empty CIDR "space" between your subnets so you can expand them later if you run out of room.

The Bottom Line

CIDR block allocation is the blueprint of your house. If you build the rooms too small or put the doors in the wrong place (overlapping addresses), it is very difficult to fix later without tearing the whole thing down.