Will IPv4 Prices Rise or Fall in 2026? What Operators Can Actually Control

The honest answer comes before the forecast

IPv4 prices can rise in one segment and fall in another at the same time. A /24 used by a network that needs it next month is not the same decision as a large block held for optional expansion. Region, transfer eligibility, routing history, reputation, block size and timing all change what a buyer is actually buying.

So the useful answer to “will IPv4 prices rise or fall in 2026?” is not a confident arrow. It is a decision method. Before you accept a quote, ask what problem the address space solves, what evidence supports the price and what happens to the business if the resource becomes difficult to transfer, route or replace.

Scarcity is real, but the market is not the registry

The IANA registry records how IPv4 space is designated and delegated; it does not publish a universal market price or turn an address into political property. Regional registries apply their own policies to allocation, registration and transfers. APNIC describes the remaining supply as limited and points operators toward IPv6 as the long-term way to grow, while RIPE NCC and ARIN describe transfer processes with region-specific conditions.

That distinction matters. An address is a technical identifier. A registry entry is a coordination record. A sale or lease is a commercial arrangement. A route is an operational fact. Confusing those layers makes a quote look like ownership of more than the transaction can actually deliver.

Check the current IANA IPv4 Address Space Registry

Read Note 45, On the Manufactured Narrative of IPv4 Scarcity

Four signals tell you more than a headline price

A responsible evaluation keeps four questions together. None of them predicts a market perfectly. Together they show whether a price is connected to an operating need or only to a story about scarcity.

• Need: which services, customers or transition plans require the addresses, and for how long?
• Liquidity: can the resource be transferred under the relevant registry rules, and what evidence or waiting period applies?
• Quality: do route history, abuse records, reverse DNS, geolocation and reputation fit the intended use?
• Substitution: what can IPv6, NAT, dual-stack design, better address management or a lease do instead?

If an evaluation cannot answer these questions, a low price may simply be hiding work that will appear later. A high price may be charging for a capability the business does not need.

Buying and leasing solve different problems

Buying can make sense when a network has a durable requirement, a clear continuity plan and the capability to carry the record, routing and reputation work that comes with the resource. It also ties up the buyer's capital and leaves the buyer responsible for quality risk and future transfer decisions.

Leasing can make sense when timing is uncertain, demand is temporary or capital is better kept for the service that uses the addresses. It does not remove registry risk or operational responsibility. The contract still needs to make the resource, routing support, abuse handling, replacement path and end-of-term process understandable.

The right comparison is therefore not simply purchase price versus monthly rent. Compare total cost, reversibility, continuity and the work your team can actually control.

Note 66 explains why the broker question is really a registry-risk question

Three scenarios are useful only when they change your preparation

A stable market would still contain regional and block-size differences. A rise could come from a time-sensitive compatibility need, a transfer constraint or a temporary supply shock. A fall could come from more available blocks, weaker demand or real IPv6 deployment. These are scenarios, not promises.

The point of a scenario is to decide what you will do before it arrives. If you need addresses in the next quarter, establish the route and transfer facts now. If your requirement is optional, measure the cost of waiting. If your service can move toward IPv6, do that work before an IPv4 quote becomes the only plan.

• Stable or mixed: keep more than one sourcing path and review the operational baseline regularly.
• Short-term increase: avoid panic buying by defining the minimum usable block and the continuity deadline.
• Long-term decrease: do not mistake a lower quote for a reason to postpone IPv6 and better records.

Test the block before you buy the story

A block can be cheap and still be expensive to operate. Test it in an isolated environment and inspect the evidence that will matter after deployment: current registration, transfer eligibility, route origin, routing history, reverse DNS, abuse history, geolocation, block size and the provider's response when something goes wrong.

Then test the business path. Can the address be announced when promised? Can the record be corrected? Can a customer move without losing a recognised endpoint? Can the operator explain which responsibilities remain with the seller, the lessor, the registry and the network team? A transaction is not complete because money changed hands. It is complete when the service can operate and recover.

Review the current ARIN transfer conditions

Review the current RIPE NCC transfer conditions

What operators should do now

Start with an inventory you can verify. Identify idle space, overlapping plans, records that no longer match reality and services that cannot tolerate a change of address. Put a date and owner on each decision. Build IPv6 into new services rather than treating it as a distant research project, and keep IPv4 as a consciously managed compatibility layer where it is still required.

If the address is part of customer continuity, document who can change the record, who can change the route and how the relationship ends. Lu Heng's Note 68 describes the economic value created by network identity and customer continuity; that value is a reason to design a change path, not a reason to make one administrator irreplaceable.

Read Note 68, The Economics of Network Identity

The decision is bigger than the direction of a price chart

IPv4 pricing is a visible symptom of a longer transition: finite identifiers remain embedded in services, records and customer expectations while the Internet keeps growing. The practical goal is not to guess the next headline. It is to keep the business able to operate when a supplier changes, a policy changes, a route is rejected or a better protocol becomes available.

Choose the smallest resource that solves the real problem. Test the evidence before the contract. Preserve the records that make continuity possible. And keep a path open to change coordinators, providers and protocols. That is how an operator turns a volatile market into a manageable engineering decision.

Continue with Note 72, The Bill of Rights of Uniqueness Coordination