What Is Prefix Length and Why Do IPv4 Buyers Care?

An IPv4 block is defined not only by its starting address but also by its prefix length. That value determines how many addresses the block contains, how it can be subnetted and announced, and whether it fits the buyer’s routing and growth requirements.

IPv4 prefix length is the number after the slash in CIDR notation that identifies how many leading bits belong to the network portion of an address. Its purpose is to define block size and routing granularity so buyers can evaluate capacity, announcement options, filtering risk, transfer practicality, and future expansion.

How does IPv4 prefix length determine block size?

IPv4 addresses contain 32 bits. The prefix length shows how many bits identify the network, while the remaining bits determine the number of addresses inside the block.

Common examples include:

/24 with 256 addresses;
/23 with 512 addresses;
/22 with 1,024 addresses;
/21 with 2,048 addresses.

A shorter prefix represents a larger block, while a longer prefix represents a smaller one. Buyers should start with required capacity and network design rather than assuming one CIDR size is automatically correct.

Why does the same address count not always provide the same usability?

Address count alone does not describe how easily a resource fits the network. A company may need one contiguous range for a data center, several independently routed regional pools, or space that can be divided without creating unrelated external prefixes.

A /22 can contain four /24 networks while retaining one larger aggregate. Four unrelated /24 blocks provide the same total address count but require separate routing, registry, monitoring, and operational records.

Why do IPv4 buyers care about routing filters for longer prefixes?

Public routing policies can limit how specific an IPv4 announcement may be. /24 is widely treated as an important practical boundary for global IPv4 routing, while longer announcements such as /25 or /26 may be filtered by some networks.

Before purchase, verify:

the smallest prefix that must be announced independently;
filtering policies of important upstreams and peers;
whether an aggregate can remain announced alongside more-specifics;
whether ROA and IRR records support the intended prefix lengths;
whether the routing design depends on prefixes longer than /24.

Routing acceptance remains a policy decision by individual networks, so no prefix length guarantees global reachability.

How can deaggregation change the operational value of a larger IPv4 block?

Deaggregation means announcing smaller prefixes from a larger aggregate. It can support regional routing, migration, traffic engineering, or multihoming, but it creates additional routing entries and requires authorization to match the more-specific announcements.

A buyer might acquire a /22 but announce four /24 prefixes from different regions. The raw capacity stays the same, but the operational design differs from announcing one aggregate.

What should a buyer verify before transferring an IPv4 block?

The exact CIDR range in the transaction should match the resource the buyer expects to receive and route. Prefix length should be reviewed together with registry data, routing records, and the future origin ASN.

The purchase review should cover:

exact prefix and address boundaries;
required capacity and planned subnetting;
transfer eligibility;
current and planned origin ASN;
relevant IRR route objects and ROAs;
aggregate and more-specific announcement plans;
upstream filtering requirements.

A buyer preparing to buy IPv4 addresses should separate commercial block size from technical usability before completing the transaction.

How does prefix length affect future network growth?

A block that fits current demand may become restrictive as the network adds customers, regions, or services. Buying only the minimum capacity can force the company to add unrelated ranges later and increase routing complexity.

Buying substantially more space than needed can tie capital to unused capacity. Buyers should estimate realistic growth, utilization, segmentation requirements, and the value of contiguous space.

When can leasing help a company test the required block size?

A company may not know immediately whether a larger prefix is needed permanently. It can rent IPv4 addresses while monitoring utilization and confirming whether the routing model works at the chosen size.

Leasing can be useful for temporary expansion, migration, or uncertain growth. Permanent requirements may justify purchase once the organization knows how much contiguous space and routing control it needs.

Which prefix-length questions deserve separate attention?

Is a /24 always globally routable?

No. Individual networks control their own filters, although /24 is commonly treated as a practical IPv4 routing boundary.

Can a /22 be announced as four /24 prefixes?

Technically, yes. The routing policy, ROAs, IRR records, and upstream filters should support those announcements.

Does a larger block always provide better usability?

No. It provides more capacity, but the extra space may not match the topology, budget, or routing plan.

Does prefix length affect the transfer itself?

Yes, because the exact resource and boundaries must match the transaction. Routing acceptance remains a separate issue.

Where can buyers compare IPv4 blocks by size and intended use?

When a buyer needs IPv4 space with a prefix length that matches its capacity and routing requirements, InterLIR can support IPv4 purchasing or leasing. The selected block can then be evaluated against the planned subnetting, announcement model, and future growth.