IPv4 exhaustion has changed how organizations acquire address space.
Businesses that once expected to receive IPv4 addresses directly from a Regional Internet Registry may now need to obtain resources from another organization. In some cases, the buyer and seller are located within different registry service regions, making an inter-RIR transfer necessary.
An inter-RIR transfer moves the registration of IPv4 address space between organizations associated with different Regional Internet Registries. Although this can expand the pool of potential counterparties, it also introduces policy, documentation, technical, and commercial considerations that may not arise in an intra-regional transaction.
Organizations reviewing inter-RIR IPv4 transfer trends in 2026 should consider more than transaction volume. Transfer data becomes most useful when it is evaluated alongside registry compatibility, address quality, operational readiness, and long-term network strategy.
Why Inter-RIR Transfers Matter
The five Regional Internet Registries administer Internet number resources within their respective service regions:
- AFRINIC serves Africa.
- APNIC serves the Asia-Pacific region.
- ARIN serves Canada, the United States, and parts of the Caribbean and North Atlantic.
- LACNIC serves Latin America and parts of the Caribbean.
- RIPE NCC serves Europe, the Middle East, and parts of Central Asia.
These organizations manage registration data and support policy processes covering IPv4 addresses, IPv6 addresses, and Autonomous System Numbers.
The Number Resource Organization provides information about the coordinated RIR system and its role in maintaining an authoritative Internet number registry.
Because available IPv4 resources and market demand are not distributed evenly, an organization may find a suitable address block in another region. Inter-RIR transfer arrangements can connect buyers and sellers who would otherwise be separated by registry boundaries.
This can benefit organizations that need IPv4 addresses for:
- Cloud infrastructure
- Hosting services
- Broadband networks
- Enterprise expansion
- Data center deployments
- Network acquisitions
- Customer-facing applications
- Equipment or services that cannot yet operate entirely over IPv6
However, a larger market does not automatically make a transfer simpler.
An Inter-RIR Transfer Is More Than a Sale
An IPv4 transfer is not equivalent to purchasing ordinary equipment.
IP addresses are Internet number resources administered according to registry policies. A completed transaction generally requires the relevant registries to approve the transfer and update their registration records.
A commercial agreement between two parties does not, by itself, guarantee that a registry will complete the requested change.
The parties may need to demonstrate that:
- The source organization has authority over the resources.
- The address block is eligible for transfer.
- The recipient satisfies the applicable requirements.
- Both participating registries support the transfer path.
- Registration information can be updated correctly.
- Required agreements and supporting documents have been submitted.
- Any policy-based restrictions have been addressed.
Transfer requirements can change as registry communities update their policies. Organizations should verify the current rules with both registries before signing a binding commercial agreement.
Confirm That the Transfer Path Is Supported
The first step is to identify the source and recipient registries.
Not every possible registry pairing necessarily operates under identical rules. A registry may support transfers only with regions that maintain compatible policies or reciprocal arrangements.
Before evaluating a specific address block, the buyer should determine:
- Which RIR currently administers the resources?
- Which RIR will administer them after the transfer?
- Do both registries support that inter-RIR transfer path?
- What eligibility requirements apply to the source holder?
- What requirements apply to the recipient?
- Which organization must initiate the registry process?
- Are there holding periods or transfer restrictions?
- What documents will each registry require?
This review should be completed early. Discovering an incompatibility after negotiating price and contractual terms can delay or terminate the transaction.
Verify the Source Organization’s Authority
The seller’s identity should match the organization shown in authoritative registry records, or the seller should provide documented evidence explaining its legal authority to transfer the resources.
Discrepancies can arise after:
- Mergers and acquisitions
- Corporate reorganizations
- Business closures
- Legal name changes
- Asset purchases
- Insolvency proceedings
- Changes in registry membership
- Historical assignments involving predecessor organizations
Due diligence should establish a clear chain between the registered resource holder and the party signing the transfer agreement.
Relevant evidence may include corporate registration documents, merger records, acquisition agreements, registry correspondence, or authorization from an insolvency administrator.
If ownership or authority cannot be demonstrated clearly, the buyer may face delays, additional legal costs, or rejection by the registry.
Investigate the Address Block’s Operational History
Registry eligibility is only one part of the evaluation. A technically transferable block may still have a problematic operational history.
IPv4 addresses can retain reputational signals from previous use. A block may have been associated with spam, malicious traffic, compromised devices, proxy services, or other activity that caused third parties to restrict it.
Buyers should investigate:
- Email and security blocklists
- Abuse-reporting databases
- Historical routing announcements
- Previous origin ASNs
- Reverse DNS configuration
- Geolocation records
- Existing route objects
- RPKI status
- Unexpected more-specific announcements
- Continued use by the former holder
No single database provides a complete answer. Address reputation should be examined through multiple independent sources.
The buyer should also determine whether major platforms classify the addresses correctly. Incorrect geolocation can affect content availability, fraud controls, licensing, advertising, and user authentication.
Review Routing and RPKI Readiness
After the registry approves a transfer, the new holder must prepare the resources for operational use.
The organization may need to update:
- Internet Routing Registry objects
- Route Origin Authorizations
- Reverse DNS delegations
- Network access-control lists
- Geolocation submissions
- Peering and transit-provider filters
- Monitoring systems
- Internal IP address management records
RPKI requires particular attention. A Route Origin Authorization associated with the previous network may no longer reflect the intended origin ASN.
If the new holder announces the prefix before creating the correct authorization, networks performing Route Origin Validation may classify the route as invalid. This can reduce reachability even when the registry transfer itself has been completed.
The technical team should define the intended origin ASN and prefix lengths before announcing the resources.
Account for Route-Propagation Delays
Registry records, routing filters, reputation databases, and geolocation providers do not all update simultaneously.
A transfer may be complete in the authoritative registry while third-party systems continue displaying outdated information. Some providers may still associate the block with its former organization, country, or autonomous system.
A deployment plan should allow time for:
- Registry changes to become visible
- Route objects to be updated
- RPKI data to propagate
- Transit providers to refresh filters
- Geolocation providers to process corrections
- Security vendors to reassess the block
- Reverse DNS changes to take effect
Organizations should avoid promising immediate production use without accounting for these dependencies.
Understand the Full Transaction Cost
The quoted price per IPv4 address is only one component of the acquisition cost.
Other expenses may include:
- Registry fees
- Brokerage fees
- Legal review
- Escrow services
- Corporate-document preparation
- Address reputation analysis
- Geolocation remediation
- Route and RPKI configuration
- Internal engineering work
- Currency conversion
- Taxes
- Post-transfer monitoring
A lower-priced block can become more expensive if it requires extensive reputation cleanup or if incomplete documentation delays the transfer.
Businesses should compare opportunities using the total expected cost of obtaining clean, usable, properly registered address space.
Use Conditional Contract Terms
A transfer agreement should reflect the fact that registry approval and technical usability may not be entirely under the parties’ control.
Appropriate contractual protections may address:
- Registry approval as a condition of completion
- Accuracy of the seller’s representations
- Authority to transfer the address space
- Absence of undisclosed disputes or encumbrances
- Required cooperation with registry requests
- Payment through escrow
- Inspection or due-diligence periods
- Treatment of rejected transfers
- Responsibility for taxes and fees
- Confidentiality
- Timing and termination rights
Technical due diligence should also be completed before funds are released.
An escrow arrangement can help coordinate payment with registry confirmation, although the parties must define precisely what event constitutes successful completion.
What Transfer Statistics Can Reveal
Inter-RIR transfer data can provide useful market signals when interpreted carefully.
Analysts may examine:
- The number of approved transfers
- Total addresses transferred
- Average and median block size
- Source and recipient regions
- Changes in transfer direction
- Concentration among large transactions
- Activity by month or quarter
- The number of participating organizations
The RIR statistics resources published by ARIN provide access to joint registry reports and historical Internet number-resource information that can support broader research.
However, transaction counts and address totals answer different questions.
A small number of large transfers may represent more address space than many small transactions. Conversely, a rise in smaller transfers may indicate participation by a wider range of organizations.
Public transfer records also do not necessarily reveal:
- The private transaction price
- Broker commissions
- Contractual conditions
- Address reputation
- Whether the addresses were deployed immediately
- The buyer’s intended use
- Transactions that were initiated but never completed
Market conclusions should distinguish recorded registry activity from private commercial information.
Inter-RIR Transfers and IPv6 Strategy
Acquiring IPv4 addresses can solve an immediate operational problem, but it does not eliminate the need for IPv6.
Continued dependence on IPv4 may require:
- Additional address purchases
- Carrier-grade NAT
- Complex address conservation
- Overlapping private-address management
- Ongoing market and compliance costs
Organizations should evaluate IPv4 acquisition and IPv6 deployment together.
A balanced strategy may use acquired IPv4 resources for services that still require them while expanding IPv6 support across networks, applications, monitoring systems, security tools, and customer platforms.
This reduces the risk of treating repeated IPv4 purchases as the only available growth model.
A Buyer’s Inter-RIR Transfer Checklist
Before proceeding, a prospective buyer should confirm the following:
Policy and registry checks
- The source and recipient RIRs support the transfer.
- The address block is eligible.
- The recipient satisfies applicable requirements.
- Any waiting periods or restrictions are understood.
- Required documents have been identified.
Legal checks
- The seller is authorized to transfer the resources.
- Corporate names and registry records are consistent.
- Relevant merger or acquisition documents are available.
- Contract terms are conditional on registry approval.
- Payment and escrow procedures are clear.
Technical checks
- Historical routing has been reviewed.
- Reputation and blocklist status have been assessed.
- Geolocation issues have been identified.
- RPKI and route-object changes are planned.
- Reverse DNS requirements are understood.
- The intended origin ASN and prefix lengths are documented.
Deployment checks
- Transit providers are prepared to accept the routes.
- Monitoring is available from multiple networks.
- A propagation period has been included in the schedule.
- A rollback or incident-response process has been defined.
- IPv6 deployment remains part of the capacity plan.
Conclusion
Inter-RIR IPv4 transfers can help organizations obtain address space from a wider market, but they require coordination across policy, legal, commercial, and technical teams.
A successful transfer is not measured only by registry approval. The acquired addresses must also be routable, correctly registered, operationally clean, and suitable for the buyer’s intended services.
Organizations should verify registry compatibility before committing to a transaction, examine the seller’s authority, investigate the block’s history, and prepare routing and RPKI changes in advance.
Transfer statistics can help businesses understand market direction, but the quality of an individual transaction depends on careful due diligence. By combining market analysis with registry verification and technical planning, buyers can reduce risk and bring acquired IPv4 resources into production more reliably.
