Buyers need more than an address count. Prefix length shapes subnetting, routing, and expansion. A poor choice can add costs or depend on routes that upstream networks filter.
IPv4 prefix length is the number of leading network bits in a 32-bit IPv4 address, written after a slash in CIDR notation. It determines the total addresses in a block and the boundaries of that range. Buyers use it to assess capacity, subnet design, public routing, transfer eligibility, and future growth before acquiring address space.
In IPv4 CIDR prefix notation, /24 fixes 24 network bits and leaves eight for addresses. The calculation is 2^(32 − prefix length). A shorter prefix contains more addresses; a longer prefix contains fewer.
The following IPv4 block size by prefix values can be used for network planning:
Actual host capacity may be lower because conventional subnets reserve network and broadcast addresses, and cloud platforms may reserve more.
When making a /24 /23 /22 prefix size comparison, network topology and routing requirements must also be considered. A contiguous /22 can form four /24s and be announced as one aggregate. Four unrelated /24s cannot be aggregated into one CIDR route.
For example, 10.20.8.0/22 covers 10.20.8.0 through 10.20.11.255. Its four /24 subnets start at 10.20.8.0, 10.20.9.0, 10.20.10.0, and 10.20.11.0. This private example illustrates valid boundaries.
In global BGP, /24 is the usual practical limit for IPv4 announcements. Many networks filter /25 or /26 routes. These are operator policies, not universal prohibitions; /24 acceptance is not guaranteed.
Before you choose IPv4 prefix length, check:
A ROA for /22 with maxLength /22 does not authorize /24 announcements. The holder must update authorization first.
Deaggregation is the announcement of smaller prefixes from a larger allocation. A network might announce one /22 aggregate and use /24 routes for traffic engineering or a migration between sites. Each extra route needs consistent BGP policy, origin authorization, and monitoring.
Extra routes increase routing-table entries and maintenance. Buyers must confirm their design with upstreams: not every valid subnet is globally routable.
The prefix length for IPv4 buyers is also important when reviewing contract terms and transfer requirements. Confirm the exact CIDR boundaries and transfer eligibility under the relevant Regional Internet Registry (RIR).
Review the following before payment:
Registry transfer does not activate routing; upstream support remains necessary.
To choose an IPv4 block by prefix, estimate usage, growth, segmentation, spare capacity, and sites. A /22 has four times the addresses of a /24.
Larger blocks also require more capital. Smaller, unrelated blocks may mean more route objects and operational overhead. Compare the effective cost per usable address with the flexibility of contiguous space, and ensure a proposed purchase matches your routing plan rather than simply the lowest quoted price.
If demand is uncertain, rent IPv4 addresses for migration or expansion tests. Measure utilization and routing before buying.
For stable workloads, buy IPv4 addresses if long-term control justifies the expense. Check LIR support for resource-management needs. In either case, verify reputation and routing.
How many addresses are in an IPv4 /24?
A /24 contains 256 total addresses. Host availability depends on subnet conventions and any provider-specific reservations.
Can a /22 be advertised as four /24s?
Yes, technically, but the ROAs, route objects, origin ASN, and upstream filtering rules must support the more-specific routes.
Does a shorter prefix always make a better purchase?
No. It increases capacity but may exceed the budget or leave addresses unused. The right prefix matches the network design and credible growth forecast.
Does purchasing a /24 guarantee global BGP reachability?
No. Many networks accept /24 announcements, but valid authorization, routing configuration, and each upstream’s policies still matter.
Selecting a prefix requires a balance of usable capacity, contiguous space, routing policy, and transfer requirements. If you need to expand hosting infrastructure, acquire a routable block, or test capacity through leasing, contact InterLIR. Its IPv4 marketplace offers blocks with different sizes, regions, and prices, while the team can help clarify registry procedures, address history, and deployment requirements. Discuss the expected ASN, routing arrangements, and growth plan before selecting a block so the resource fits both the transaction and the network that will use it.
Vladislava Shadrina
Customer Account Manager
Live chat is provided by Intercom and is loaded only after you enable it. You can also contact us without enabling the chat.