IPv4 capacity planning in 2026 is no longer as simple as asking whether addresses are available.

The underlying IPv4 address space is fixed, but usable capacity continues to move between networks through transfers, recovered address redistribution, leasing, internal reclamation and infrastructure changes.

For network operators, that creates a more complicated planning question: How much IPv4 capacity is realistically available when the business needs it, in the block sizes and operational condition required?

Price matters. But so do waiting times, transfer activity, block size, routing history, reputation and deployment readiness.

Understanding these signals together provides a better picture of IPv4 availability than looking at any single market indicator.

IPv4 Availability Is Not the Same as IPv4 Supply

IPv4 uses a 32-bit address space. That means the Internet cannot simply create additional IPv4 addresses to meet new demand.

What can change is the amount of previously allocated address space that becomes available for reuse. Usable IPv4 capacity may enter circulation through address transfers, recovered resources, returned allocations, corporate consolidation, network restructuring, internal reclamation, leasing and more efficient use of existing address space.

This distinction is important. IPv4 supply in 2026 largely means redistribution of existing resources, not creation of new resources.

LARUS Foundation examines this dynamic in more detail through pricing, transfers, registry waiting lists and secondary-market availability in IPv4 Supply and Demand 2026: Prices, Transfers & Waiting Lists.

Why Price Alone Can Mislead Network Planners

It is tempting to use the market price of an IPv4 address as a simple indicator of scarcity. Real markets are more complicated.

Prices can decline while transaction activity remains active. More address holders may decide to sell unused blocks at the same time that networks continue purchasing address capacity.

A lower IPv4 price is therefore not the same thing as disappearing IPv4 demand. For infrastructure planning, price should be treated as one signal among several.

Waiting Lists Tell a Different Story

Regional Internet Registry waiting lists provide another view of IPv4 demand.

RIPE NCC continues to redistribute recovered IPv4 addresses through a waiting list. Its policy allows qualifying LIRs that have not previously received an IPv4 allocation from RIPE NCC to request one /24, representing 256 addresses.

In August 2026, RIPE NCC reported 757 LIRs on the IPv4 waiting list, with the organization at the front of the queue having waited 467 days.

That does not mean every organization requiring IPv4 will join a waiting list. The allocation size is limited, eligibility conditions apply and business requirements may not allow an organization to wait more than a year for capacity. But the queue is still an important signal: organizations continue seeking IPv4 space outside commercial transfer markets.

ARIN Also Redistributes Recovered IPv4 Resources

ARIN operates its own waiting-list process for qualifying organizations.

ARINs public status page reported that its most recent distribution took place on 2 July 2026, with another distribution scheduled around 1 October 2026. The organization also explains that the order in which requests can be fulfilled depends on the sizes and quantities of IPv4 blocks returned to its inventory.

This highlights another feature of recovered IPv4 supply: availability is unpredictable.

For a network operator with an immediate deployment deadline, this creates a difference between potential future supply and deployable capacity available now.

Transfer Activity Provides Another Signal

Transfers reveal another part of the IPv4 availability picture.

A transfer does not create additional address space. Instead, it moves previously allocated resources toward another organization that can use them.

Transfer activity can therefore increase effective market availability even though total IPv4 supply remains fixed.

RIPE NCC monthly statistics demonstrate that transfer volumes can vary considerably from one month to another, showing why a single snapshot is not enough to describe market availability.

Block Size Changes the Availability Question

Not all IPv4 supply is interchangeable.

An organization needing one /24 has a very different requirement from an operator looking for a /16. A /24 contains 256 IPv4 addresses, while a /16 contains 65,536 addresses.

There may be many smaller blocks available while suitable larger contiguous blocks remain relatively difficult to source. This is why network planners should ask whether the block size they actually need is available, rather than simply whether IPv4 addresses are available.

Address History Can Affect Effective Supply

A block may technically be available but still be unattractive for a particular workload.

IPv4 addresses accumulate operational history. Previous users may have operated hosting platforms, email systems, VPN infrastructure, residential networks, cloud services, automated traffic, proxy networks or other applications.

After the resource changes user, third-party systems may still retain information associated with its previous history. This can affect spam reputation, fraud scoring, geolocation, application access, email deliverability and security filtering.

An available IPv4 block is therefore not necessarily a deployment-ready IPv4 block.

Routing History Matters Too

Network operators should also review routing history before treating available address space as usable inventory.

Useful questions include which ASNs previously originated the prefix, whether the block is currently routed, whether it recently changed origin, whether there are unexpected more-specific routes, and whether the intended routing arrangement matches the documentation.

Routing history does not establish ownership or registry control, but it provides useful information about how the resource has operated on the Internet.

RPKI Should Be Checked Before Deployment

RPKI adds another practical requirement.

Before deploying a transferred or newly leased IPv4 prefix, operators should confirm whether existing Route Origin Authorizations are compatible with the intended origin ASN.

If the block was previously authorized for AS64500 but will now be announced by AS64550, the relevant routing authorization may need to change.

For capacity planning purposes, supply should not be evaluated solely as whether the prefix can be obtained. The better question is whether the prefix can be obtained, authorized, routed and operated reliably.

Registry Region Can Affect Transfer Planning

Registry relationships may also affect how quickly or easily a transaction can be completed.

IPv4 transfer requirements differ across Regional Internet Registries. A transfer involving organizations within one registry environment may follow a different process from an inter-RIR transaction involving two registries.

Network planners should therefore identify the current RIR, intended recipient RIR, transfer eligibility, required documentation and likely administrative dependencies early in the process.

Leasing Adds Another Source of Capacity

Purchase transfers are not the only way organizations gain operational IPv4 capacity.

Leasing can provide access without permanently transferring the underlying resource. That creates another layer of IPv4 supply that may not be visible in ordinary transfer-volume statistics.

For organizations with temporary workloads, rapidly changing infrastructure, short planning horizons, uncertain long-term requirements or limited capital budgets, leasing may be considered alongside purchase or registry allocation options.

Internal Reclamation Is an Invisible Source of Supply

Some of the most important IPv4 supply never enters a public market.

Large organizations may discover underused address space within their existing infrastructure, including retired applications, abandoned data centers, old customer assignments, oversized internal allocations and workloads migrated to IPv6 or private addressing.

Reclaiming these addresses can reduce the need to purchase or lease additional space. Because this activity occurs internally, it may not appear in transfer-market statistics.

IPv6 Changes the Equation, but Does Not Eliminate IPv4 Planning

IPv6 deployment remains the long-term solution to IPv4 address limitations.

But IPv6 adoption does not immediately eliminate the operational need for IPv4. Many organizations continue supporting both protocols because customers still connect over IPv4, external services remain IPv4-dependent, legacy systems require IPv4, partners use IPv4 allowlists, or public services need compatibility with both protocol families.

Capacity planning in 2026 therefore often means determining where IPv4 remains necessary, rather than assuming every workload requires the same amount of public IPv4 space.

Five Signals Network Operators Should Monitor

1. Market Inventory How much address space is actually available from sellers or lessors?
2. Block-Size Availability Are suitable CIDR blocks available for the intended deployment?
3. Registry Conditions Are waiting lists, recovered allocations or transfer channels relevant to the requirement?
4. Operational Quality Does the candidate prefix have acceptable routing, reputation, geolocation and security characteristics?
5. Deployment Timing Can the resource be transferred, routed and placed into production before the capacity is needed?

A Practical IPv4 Capacity Planning Checklist

• How many addresses do we actually need? Estimate the workload rather than purchasing capacity based only on historical assumptions.
• What block sizes are operationally useful? Determine whether multiple smaller blocks are acceptable or contiguous space is required.
• When is the capacity needed? Waiting-list allocation and commercial acquisition operate on very different timelines.
• Can existing IPv4 be reclaimed? Audit internal utilization before obtaining additional resources.
• Can some workloads move to IPv6? Reduce IPv4 dependency where technically practical.
• Should the organization buy or lease? Consider duration, capital requirements, portability and operational control.
• Has the address history been reviewed? Check registry, routing and reputation information.
• Is the intended routing authorized? Review RPKI and related routing records before production use.
• What is the exit plan? Understand how the resource can be returned, replaced, transferred or migrated when requirements change.

Why the Best Metric Is Deployment-Ready Supply

Traditional economic discussions often define supply as inventory available in a market.

For network infrastructure, a more useful concept may be deployment-ready supply.

An IPv4 block becomes genuinely useful when it can be legitimately obtained, accurately registered, routed through the intended network, correctly authorized, accepted by external systems, supported operationally and deployed within the required timeframe.

That definition explains why two IPv4 blocks containing the same number of addresses may have very different practical value to a network operator.

Conclusion

IPv4 availability in 2026 cannot be understood through one number.

Market prices provide one signal. Transfer activity provides another. Registry waiting lists reveal demand that exists outside commercial markets. Leasing adds operational capacity that may not appear in transfer statistics. Internal reclamation creates supply that may never appear publicly. And IPv6 can reduce IPv4 requirements without eliminating them completely.

For network operators, the useful question is therefore not whether IPv4 is still available, but which IPv4 capacity is available, in the required block size, with acceptable operational history, on the timeline the network actually needs.

IPv4 may be fixed in numerical supply. But its effective availability continues to change as existing address space is recovered, transferred, leased, reused and redeployed.

For a broader analysis of 2026 pricing, transfers, registry queues and changing supply conditions, see IPv4 Supply and Demand 2026: Prices, Transfers & Waiting Lists.

You May Also Be Interested In

• Americas Uranium Corp. Advances Ford Lake Uranium Project with Integration of Multiple Independent Geophysical Datasets
• AGF Reports September 2026 Assets Under Management and Fee-Earning Assets
• Life Insurance Coverage Guidelines For Texas Households Explained In HelloNation Featuring Insurance Expert Jamie Smith