Legacy IPv4 holdings reduce compatibility costs—but do not guarantee market wins

IPv4 addresses, once technical identifiers, have become valuable digital assets due to scarcity. Early adopters now hold strategic advantages in service expansion and infrastructure resilience amid slow IPv6 migration.

• IANA exhausted its central stock of unallocated /8 blocks in 2011, but the five regional registries now use different combinations of final-pool limits, recovered-address waiting lists and policy-governed transfers. “All pools are empty” is not an accurate operating description.
• A registered IPv4 holding may reduce acquisition or carrier-grade NAT pressure for a network that still has IPv4-only users and services. It does not by itself create reachability, profitability or resilience; BGP origination, routing authorisation, address reputation, utilisation and IPv6 readiness determine the result.

The central pool ran out; regional policy did not stop

The Number Resource Organization's 3 February 2011 announcement records IANA's allocation of the last five /8 blocks and depletion of the central free pool. That milestone ended the former global supply model, not all allocation activity. ARIN's waiting-list record says its free pool depleted in September 2015 and that returned space can still be distributed. RIPE NCC exhausted its remaining pool in November 2019 and operates a waiting list for recovered /24s. APNIC still describes restricted delegations from its final /8 and returned space. The mechanisms and eligibility rules differ by region and change through community policy.

“Early adopter” is too broad to explain the advantage

IPv4 was standardised and deployed over decades, and legacy or historical holdings arose under several allocation regimes. A holder that received space when supply was easier may face a lower book or acquisition cost than a new entrant, but that fact does not show that it uses the space efficiently or wins customers. Some organisations have surplus blocks; others operate address-intensive access, hosting or enterprise services. The relevant comparison is the address requirement of a specific product and network, not a label applied to every historical registrant.

Registration is not the same as owning digital real estate

ARIN's explanation of its registration agreement says Internet number resources are not freely held property; it describes contractual rights created through registration. Transfer procedures update registry records after policy checks and documentation. Other RIRs have their own contracts and policies. Commercial payments may accompany a transfer or lease arrangement, but calling an address block real estate obscures registry eligibility, contractual limits, the source holder's authority, due diligence and the risk that inaccurate records or unauthorised use will impair the transaction.

A block is useful only when the network can operate it

Registration alone does not make a prefix reachable. An operator needs a routing design, an autonomous system or authorised upstream to originate the route, acceptance by peers and transit providers, accurate registry and routing records, reverse DNS where required, and address space that has not been damaged by spam, fraud or malware history. The Number Resource Organization's RPKI description explains that a holder can create a Route Origin Authorization linking a prefix to an authorised origin AS. A ROA does not guarantee reachability, but it is part of the routing-control surface.

The economic benefit is conditional and prices are opaque

Historical holdings can avoid the immediate cost of obtaining more space, support dedicated public addresses and give an operator time to redesign products. Unused space may have transfer or leasing value where policy and contracts permit. Public RIR transfer logs, however, record registration changes rather than a universal sale price, and private broker quotations vary with block size, region, history, reputation and transaction terms. The reviewed evidence does not support a direct causal link between early allocation and long-run profitability, nor the former article's price series or its purported 2025 hospital transaction.

IPv6 and address sharing change the calculation

APNIC Labs' measurement programme explains why IPv4 exhaustion and IPv6 deployment must be managed simultaneously and measures large differences across countries and networks. IPv6 therefore cannot be treated as a completed cutover, but neither should legacy IPv4 space be treated as a substitute for IPv6. Dual stack, translation and carrier-grade NAT are different architectures. RFC 6888 documents application limitations, port-allocation trade-offs and potentially large logging requirements when many subscribers share public IPv4 addresses.

More addresses can remove one constraint and create others

A sufficiently sized, clean and routable holding can reduce CGN concentration, logging volume or transfer dependence for a particular service. It can also create IP address-management work, registry fees, routing-security duties, abuse response, geolocation corrections and an opportunity cost if scarce space sits unused. A large block does not prevent outages, route leaks, hijacks, security incidents or poor product economics. Network resilience comes from diversified connectivity, sound routing policy, capacity, operations and incident response as well as addressing.

What would demonstrate a real market advantage

The defensible test is operational: measure allocated and active addresses, IPv4-only demand by product, acquisition or lease cost avoided, CGN ports and logs, customer-impact incidents, address reputation, route acceptance, RPKI coverage and the pace of IPv6 capability. Compare those measures with customer growth, service margin and reliability while controlling for network scale and product mix. RIR waiting-list and transfer data can show scarcity and movement; they cannot, without company-level evidence, show that historical holders systematically outperform the market.