IPAM glossary

What is CIDR (Classless Inter-Domain Routing)?

Abstract isometric UI showing network ranges, usage bars, region names (EMEA/APAC), and a purple "Deploy" button
Key takeawaysKey takeaways are generated with AI assistance. Because automated summaries can occasionally contain errors or miss important context, always refer to the full blog post for complete information.

CIDR (Classless Inter-Domain Routing) is an addressing method introduced in the 1990s that allocates IP addresses and aggregates routes using variable-length prefixes in the format address/prefix-length (such as 192.0.2.0/24), replacing the fixed classful A, B, and C scheme to solve IPv4 address exhaustion and routing table growth. The prefix length indicates how many leading bits identify the network while remaining bits identify individual hosts, allowing flexible block sizing on bit boundaries for both IPv4 and IPv6. Poor CIDR management causes concrete failures including overlapping prefixes, misaligned block boundaries, and broken aggregation that complicate routing, VPNs, firewall rules, and peering setups, making accurate address planning essential for network operations.

  • The prefix length in CIDR notation replaces implied class boundaries and works alongside subnet masks to specify exactly how many leading bits identify the network portion, enabling any prefix length such as /22 or /27 rather than the fixed /8, /16, or /24 of classful addressing.
  • Route aggregation through CIDR allows providers to advertise multiple contiguous customer blocks as a single shorter prefix, reducing routing table entries and keeping summary routes efficient when blocks are properly aligned on clean bit boundaries.
  • Common CIDR implementation errors such as overlapping prefixes between sites, off-by-one subnet sizing that fails to account for reserved addresses, and prefix mismatches across DHCP, firewall, and IPAM tools create hard-to-trace faults that break routing and complicate cloud network and VPN connectivity.

CIDR at a glance

AttributeValue
Full nameClassless Inter-Domain Routing
CategoryAddressing and routing method
Defined inRFC 4632, which obsoletes the original CIDR specification in RFC 1519
OSI layerLayer 3 (network layer)
Primary useAllocating IP address blocks of flexible size and aggregating routes
Related termsSubnet mask, Subnetting, IPv4, IPv6, IP address management, Route aggregation

How CIDR works

CIDR expresses a network as an IP address plus a prefix length that states how many leading bits identify the network. The remaining bits identify hosts within that network.

  1. Choose a prefix length: The prefix length, written after a slash, sets the size of the block. A /24 in IPv4 fixes 24 network bits and leaves 8 host bits, so the block holds 256 addresses.
  2. Allocate the block: A registry or provider assigns a block that fits the need, rather than a full class A, B or C network. Blocks can be any size on a bit boundary.
  3. Subdivide as needed: An organization splits its block into longer prefixes for individual subnets. A /24 can become two /25 blocks or four /26 blocks.
  4. Aggregate for routing: Contiguous blocks that share a common leading bit pattern are advertised as one shorter prefix. Two adjacent /24 blocks can be summarized as a single /23 when they align.
  5. Forward by longest match: A router compares a destination address to its table and uses the matching entry with the longest prefix, so a more specific route overrides a broader one.

CIDR notation applies equally to IPv6, where prefixes such as /64 are common for subnets. The prefix length replaces the implied class boundaries and works alongside the subnet mask, which is simply another way to write the same bit count.

Why CIDR matters in enterprise networks

CIDR was introduced to address two problems in the early 1990s: the rapid exhaustion of IPv4 address space under the classful scheme and the growth of global routing tables. The original specification appeared in RFC 1519, and RFC 4632 later replaced it. Variable-length prefixes let allocations match real need, and aggregation lets providers advertise many customer blocks as one route.

For network teams, CIDR is the basis of everyday address planning. Every subnet, firewall rule, route, DHCP scope and cloud virtual network is defined by a prefix. Consistent allocation on clean bit boundaries keeps blocks summarizable, which keeps routing tables smaller and access lists shorter. An accurate address plan also makes it easier to see how much space remains.

Poor CIDR management causes concrete failures. Overlapping prefixes between sites, cloud networks or merged organizations break routing and complicate VPN and peering setups. A wrong prefix length in a firewall rule can expose more addresses than intended or block legitimate traffic. Fragmented allocations prevent aggregation and force renumbering later, which is costly when addresses are hard-coded in many systems.

CIDR vs Classful networks

CIDR allocates and routes blocks of any prefix length on a bit boundary, while classful addressing fixed the network portion to 8, 16 or 24 bits based on the address class. What is Classful networks?

AttributeCIDRClassful networks
Prefix lengthAny length, such as /22 or /27Fixed by class: /8, /16 or /24
Block sizingMatches actual needOften far larger than needed
Route aggregationSupported through shorter prefixesNot supported beyond class boundaries
NotationAddress plus slash and prefix lengthClass implied by the leading bits of the address
Current useStandard on the internet and in private networksHistorical

CIDR vs Subnet mask

CIDR notation and a subnet mask both describe how many bits identify the network, but CIDR writes it as a prefix length and a subnet mask writes it as a dotted-decimal value. What is Subnet mask?

AttributeCIDRSubnet mask
FormatSlash and a number, such as /24Dotted decimal, such as 255.255.255.0
Information conveyedCount of network bitsBit pattern marking network bits
Typical useRouting tables, allocations, firewall rulesHost interface configuration and legacy tools

Common CIDR issues

Two teams allocate blocks that overlap, such as a /23 and a /24 inside it, and traffic reaches the wrong network or fails intermittently. The problem often surfaces when VPNs, peering or cloud networks are connected and routes conflict.

A block is written with a host address that does not sit on the prefix boundary, such as 10.1.1.64/24 when 10.1.1.0/24 was meant. Some platforms reject it and others silently normalize it, which causes confusing mismatches in route and firewall entries.

Planners forget that the first and last addresses in an IPv4 subnet are normally reserved for the network and broadcast, and that cloud platforms reserve more. A subnet sized to fit exactly runs out of usable addresses at deployment.

Allocating blocks without regard to topology leaves addresses scattered across sites, so they cannot be summarized into one route. Routing tables grow and summary routes either cannot be used or attract traffic for addresses that are not present.

A DHCP scope, firewall object and IPAM record each carry a different prefix length for the same network. Hosts get the wrong mask or rules miss part of the range, and the fault is hard to trace because each system looks internally consistent.

See how unified DDI simplifies network operations

Manage DNS, DHCP and IP addresses from one platform with automation, visibility and control built in.

CIDR FAQ

Related terms

Article

Classful networks

A previous network addressing architecture that divided the IP address space for IPv4 into five address classes based on the leading four address bits.

Learn more
Article

Subnet mask

A 32-bit number that masks an IP address, and divides the IP address into network address and host address.

Learn more
Article

IPv4 (Internet Protocol version 4)

The fourth version of Internet Protocol that uses 32-bit addresses to route most of today’s internet traffic; the global supply of IPv4 addresses is exhausted. Learn More

Learn more
Article

IPv6 (Internet Protocol version 6)

The most recent version of Internet Protocol, which uses 128-bit address space; there are 340 undecillion IPv6 addresses.

Learn more
Article

IPAM (IP address management)

A method for planning, tracking, and managing IP address space on a network.

Learn more
Article

RFC 1918 networks

Ranges of IP addresses set aside for private use on TCP/IP networks.

Learn more
Article

BGP (Border Gateway Protocol)

A standardized exterior gateway protocol to exchange routing and reachability information among autonomous systems on the internet.

Learn more
Article

Internet Protocol Address (IP Address)

A numerical label assigned to each device connected to a network that uses IP for communication.

Learn more