What Is CIDR? Networking Basics Explained
Understand CIDR notation in plain terms: what the slash number means, how address ranges are sized, and how to read blocks like 192.168.1.0/24.
Your network is 192.168.1.0/24, your office might be 10.0.0.0/8, and a cloud server could sit in 172.31.0.0/16. I used to read those slashes as decoration. They are not — the number after the slash decides how big the network is, and this guide shows you how to read it.
This guide explains CIDR in plain words: what it is, why it replaced the old class system, how the notation works, and the table I use to size a network.
CIDR (Classless Inter-Domain Routing) writes a network as an address plus a prefix, like 192.168.1.0/24. The /24 means the first 24 bits are the network and the last 8 bits are hosts — 256 addresses in total. Most home networks use this size, with the router at 192.168.1.1.
What is CIDR?
CIDR is a method of allocating IP addresses and routing internet packets. It lets network administrators divide address space into pieces of any size, instead of fixed blocks.
I think of it like a postal system: the prefix tells you which street the address belongs to, and the rest tells you which house. The slash number draws the line between the two.

Before CIDR, every network had to fit one of five fixed classes. A company that needed 1,000 addresses had to take a Class B block of 65,534 and waste the rest. CIDR ended that waste in 1993.
Why CIDR was created
In the early 1990s the internet was growing fast, and the old class system was running out of room. It was like having only small, medium, and large shirts when people needed every size in between. I see the same thing on home networks when they run out of room.
CIDR arrived in 1993 to fix that. It slowed the exhaustion of IPv4 addresses and made routing tables smaller, because routers could group many small networks into one route.
The change worked. The internet kept growing on the same 4.3 billion IPv4 addresses, and CIDR is still the system every network uses today, alongside IPv6.
Classful vs classless addressing
The old system split the IPv4 space into five classes, A through E. The first bits of the address set each class. Each class had a fixed split between the network part and the host part. I still check the class first on older networks.
| Class | Example | Network part | Host part |
|---|---|---|---|
| Class A | 10.45.72.89 | 10 | 45.72.89 |
| Class B | 172.16.45.178 | 172.16 | 45.178 |
| Class C | 192.168.1.100 | 192.168.1 | 100 |
| Class D | 224.0.0.1 | Multicast | No host part |
| Class E | 240.0.0.1 | Reserved | No host part |
Classless addressing removes those fixed boundaries. Instead of a class, the prefix length says how many bits belong to the network, so a network can be any size the administrator needs.
The limits of classful addressing
I have seen the class system fail in four ways, and each one is why CIDR replaced it.
- Wasted addresses: a company needing 1,000 addresses had to take Class B with 65,534 hosts, wasting over 64,000.
- Inflexible sizing: there was nothing between Class C at 254 hosts and Class B at 65,534. A company needing 300 addresses had no fitting option.
- Inefficient routing: four Class C networks needed four routing table entries, and thousands of networks meant huge tables.
- Limited growth: a Class C network that needed 50 more hosts had to jump to a whole Class B.
CIDR fixes all four at once: any size, no waste, and routes that group together. That is why the class system is history and CIDR is the standard.
How CIDR notation works
CIDR notation writes a network as an IP address, a slash, and a prefix length. In 192.168.1.0/24, the 24 says the first 24 bits are the network, and the last 8 bits are hosts. I read the slash first whenever I size a network.
The formula for the address count is simple: 2 to the power of (32 minus the prefix length). For /24 that is 2^8, which is 256 addresses in total.
The binary view makes it clear. 192.168.1.0 in binary is 11000000.10101000.00000001.00000000. The first 24 bits are the network, and the last 8 bits are the host part.
Two of those 256 addresses are special: the first names the network itself, and the last is the broadcast address. That leaves 254 usable hosts on a /24 network.
CIDR notation quick reference
I keep this table nearby whenever I size a network. Each step down in prefix length doubles the address count.
| CIDR | Addresses | Subnet mask | Common use |
|---|---|---|---|
| /32 | 1 | 255.255.255.255 | Single host |
| /31 | 2 | 255.255.255.254 | Point-to-point links |
| /30 | 4 | 255.255.255.252 | Small WAN links |
| /29 | 8 | 255.255.255.248 | Tiny subnet |
| /28 | 16 | 255.255.255.240 | Small office |
| /27 | 32 | 255.255.255.224 | Small department |
| /26 | 64 | 255.255.255.192 | Medium department |
| /25 | 128 | 255.255.255.128 | Large department |
| /24 | 256 | 255.255.255.0 | Standard network |
| /23 | 512 | 255.255.254.0 | Large network |
| /22 | 1,024 | 255.255.252.0 | Very large network |
| /16 | 65,536 | 255.255.0.0 | Enterprise network |
The table counts every address in the block. The usable host count is two fewer, because the first address names the network and the last is the broadcast address. The /31 and /32 rows are special cases for links and single hosts.
Common CIDR examples
Three examples cover most of what you will meet in real networks. I use them to check my own math whenever I plan a subnet.
/24 network, like 192.168.1.0/24: 24 bits for the network and 8 for hosts, giving 256 addresses. The range runs from 192.168.1.0 to 192.168.1.255, with the mask 255.255.255.0. This is the size of most home networks.
/23 network, like 192.168.0.0/23: 23 bits for the network and 9 for hosts, giving 512 addresses. The range runs from 192.168.0.0 to 192.168.1.255, with the mask 255.255.254.0. This is a /24 doubled.
/25 network, like 192.168.1.0/25: 25 bits for the network and 7 for hosts, giving 128 addresses. The range runs from 192.168.1.0 to 192.168.1.127, with the mask 255.255.255.128. This is a /24 cut in half.
CIDR in routing: route aggregation
Route aggregation is the quiet reason CIDR matters. It lets routers combine many small networks into one route, which keeps the global routing table from exploding. I check the route count first when a network feels slow.
Take four networks: 192.168.1.0/24, 192.168.2.0/24, 192.168.3.0/24, and 192.168.4.0/24. Without CIDR, each needs its own routing entry — four entries, four times the memory.
With CIDR they group into 192.168.0.0/22, a single entry that covers all four. One route instead of four means faster decisions, less memory, and less overhead on every router in the path.

CIDR blocks: IPv4 and IPv6
IPv4 uses 32-bit addresses, so prefixes run from /0 to /32, with about 4.3 billion addresses in total. Most real subnets sit between /24 and /16. I compare IPv4 and IPv6 by prefix length, not by address size.
IPv6 uses the same idea with 128-bit addresses. Common prefix lengths are /48, /56, and /64, and a /64 is the usual size for a single network. The address space is so large that running out is not a practical worry.
Each step down in prefix length doubles the addresses. That rule works the same in IPv4 and IPv6, and it is the fastest way to sanity-check a block size.
How CIDR shows up on your home network
Your home network is a CIDR block, even if you never see the slash. Most routers hand out 192.168.1.0/24, which gives 254 usable addresses for your phones, laptops, and smart devices. I check the mask first when a home network acts up.
You can see it on your own device. On Windows, run ipconfig and look at the subnet mask next to your address: 255.255.255.0 means /24. On a Mac, the mask shows in the network details.
If you are not sure which address is your router, our Router IP Finder walks you through the check. Your public address, the one the internet sees, is different — check it with our What Is My IP tool.
Real-world uses of CIDR
CIDR is everywhere in modern networking, from the cloud to your living room. I meet it in five places more than anywhere else.
- Cloud computing: when you set up a virtual private cloud, you pick a CIDR range that sizes the network.
- Enterprise networks: companies size each office and branch with its own prefix, like /22 for HQ and /26 for a small site.
- Internet providers: ISPs hand out customer ranges in CIDR blocks, sized to what each customer needs.
- Data centers: server networks are organized into CIDR blocks so routing stays fast and simple.
- Home networks: even your router uses CIDR rules to hand out addresses to your devices.
Once you can read the slash, every network makes more sense. The prefix tells you the size, the mask tells you the split, and the table above does the rest.
CIDR and subnet masks: what users ran into
Two PCs on the same network cannot see each other
A Meraki user on a /23 network found 192.168.2.x and 192.168.3.x devices could not reach each other. Community members said one side likely still had a /24 mask or the wrong gateway.
Widened to /23 and one laptop still fails
A Netgate forum user changed a VLAN from /24 to /23 and a laptop at .51.100 could not reach a server. The fix was updating the mask on every static device, since leftover /24 settings break the route back.
How to check a mask fast
Run ipconfig /all on Windows or ip addr on Linux and compare the mask on every device. One device with a different mask is enough to break local traffic.










