Surplus IPv4 address space can represent significant unrealized value for an enterprise, internet service provider, hosting company or legacy network operator.
However, selling IPv4 is also an operational decision. Address blocks may still be connected to customer services, routing policies, firewall rules, access lists, reverse DNS records and external integrations.
A poorly planned sale can create avoidable downtime, renumbering costs or registry delays. A well-prepared transaction can release capital while preserving the network capacity the organization still needs.
The seller therefore needs to answer two questions: how much is the IPv4 block worth, and can the resource be transferred without disrupting operations?
What It Means to Sell IPv4 Addresses
Selling an IPv4 block normally involves transferring registered Internet number resources from one eligible organization to another through the applicable Regional Internet Registry.
The transaction has two connected components:
1. A commercial agreement between the seller and buyer
2. A registry process that updates the recognized resource holder
The relevant RIR must approve and record the transfer according to its policies. ARIN, RIPE NCC and APNIC each maintain their own transfer procedures and documentation requirements.
A purchase agreement alone does not update the registry. The commercial and registry sides of the transaction must be coordinated.
Why Organizations Sell IPv4 Addresses
The Addresses Are No Longer Fully Used
A company may have received a large allocation when its network architecture was very different. Cloud migration, business restructuring, acquisitions or infrastructure consolidation may have reduced its current IPv4 requirements.
The Business Wants to Release Capital
Surplus IPv4 resources can hold value that is not contributing to current operations. A sale can convert that value into capital for network upgrades, cloud migration, debt reduction, business expansion, cybersecurity investment, acquisitions or general operating requirements.
Registry Administration Is No Longer Strategic
Holding address resources can involve ongoing registry relationships, record maintenance, abuse response and routing administration. An organization that no longer needs the addresses may prefer to transfer the resources rather than continue carrying these responsibilities.
The Company Is Closing or Restructuring a Network
IPv4 sales may form part of a data center closure, service exit, corporate restructuring, merger or liquidation. In these situations, the transfer must be coordinated with both technical shutdown activities and corporate authorization.
Determine Which Addresses Are Truly Surplus
The registry allocation size does not necessarily show how much address space can safely be sold. An organization may appear to hold an unused /16 while individual prefixes inside that allocation are still referenced throughout its infrastructure.
Before offering a block for sale, the technical team should inventory:
• Active BGP announcements
• Customer assignments
• Network address translation configurations
• Firewall rules and VPN endpoints
• DNS and reverse DNS records
• Monitoring systems and API allowlists
• Partner access lists and mail infrastructure
• Disaster recovery environments
• Hardware management interfaces
• Historical or undocumented services
Traffic measurements alone may not identify every dependency. An address receiving little traffic may still be required for a backup connection, security policy or trusted third-party integration.
The organization should classify every prefix as actively required, required temporarily, reserved for a documented project, available for renumbering or genuinely surplus. Only the final category should move directly into a sale process.
Confirm the Registration and Transfer Path
Internet number resources are administered through a hierarchical registry system. IANA coordinates top-level IPv4 allocations, while the Regional Internet Registries manage resources within their respective service regions.
Before attempting to sell a block, the holder should establish:
• Which RIR administers the resource
• Which organization appears in the registry
• Whether the registration information is current
• Whether the resource is covered by the necessary agreement
• Whether the approving person has corporate authority
• Whether the block meets the applicable transfer policy
• Whether a holding period or other restriction applies
• Whether the recipient will be located in the same RIR region
• Whether an inter-RIR transfer is available
Transfer rules are not identical across all registries. The current policy of the relevant RIR should be checked before commercial terms are finalized.
Correct Registry Records Before Marketing the Block
Outdated records can slow due diligence and create uncertainty about the seller’s authority.
Common issues include:
• Former employees listed as contacts
• Inactive email addresses or old company names
• Unrecorded mergers or acquisitions
• Resource records linked to a dissolved entity
• Incomplete corporate documentation
• Disagreement between internal records and RIR data
• Missing account access
• Unclear authorization from directors or officers
These problems do not always prevent a sale, but resolving them can require additional evidence and time. The seller should update administrative information and collect relevant corporate records before asking a buyer to complete due diligence.
Review Routing and RPKI Dependencies
A prefix may still be announced even when the organization believes it is unused. The network team should check:
• Whether the prefix is visible in BGP
• Which autonomous system originates it
• Whether more-specific routes exist
• Whether a Route Origin Authorization covers the block
• Which Internet Routing Registry objects reference it
• Whether a Letter of Authorization remains active
• Whether upstream providers still accept or announce the route
• Whether reverse DNS is delegated
Routing records should not necessarily be removed immediately. They must be handled according to a coordinated migration plan. Removing a route or ROA too early may interrupt active services, while leaving obsolete authorizations in place after completion can create confusion for the buyer.
The transfer plan should identify who will change each routing-related record and when the change will occur.
Investigate the Block Reputation
Address history can affect the practical usability and commercial attractiveness of an IPv4 block. A buyer may examine public blocklists, spam history, malware reports, previous routing activity, geolocation databases, abuse contacts, prior network operators and reverse DNS records.
The presence of a reputation issue does not automatically make a transaction impossible. The seller should disclose known problems instead of allowing the buyer to discover them late in due diligence.
Sellers should also avoid describing a block as completely clean. No organization controls every external reputation database, and historical records may remain after the underlying problem has been resolved.
A more defensible approach is to document which reputation sources were checked, when they were checked, what issues were found, what remediation has been completed and whether any disputes remain open.
Decide Whether to Sell the Entire Block
Selling an entire allocation is not always necessary. An organization may be able to retain the portion it still needs and transfer the surplus portion, depending on registry policy, prefix boundaries and commercial feasibility.
| IPv4 block | Number of addresses |
|---|---|
| /16 | 65,536 |
| /20 | 4,096 |
| /22 | 1,024 |
| /24 | 256 |
Subdivision can make part of a portfolio available while preserving operational capacity. It can also introduce additional planning requirements involving routing, registry records, reverse DNS and renumbering.
The seller should compare the value of selling the whole block with the value of smaller prefixes, the cost of renumbering retained services, buyer demand for each block size, the technical effect of deaggregation and the registry’s rules for partial transfers.
Consider Sale and Leaseback for Active Networks
Some organizations want to release the value of their IPv4 resources but cannot immediately stop using the associated address capacity. A sale-and-leaseback structure may provide an alternative.
Under this arrangement:
1. The organization sells the IPv4 resource.
2. The buyer becomes the recognized resource holder through the applicable transfer process.
3. The seller leases back the capacity required for continued operations.
4. The network migrates to the new operating arrangement under agreed terms.
This structure can separate the financial value of the resource from its operational use. The agreement should define the leased capacity, term, renewal conditions, routing authority, RPKI and IRR management, reverse DNS administration, abuse procedures, support responsibilities, termination rights and future migration requirements.
Organizations looking to release capital, complete a direct transaction or discuss continued use can sell IP addresses to LARUS and request a cash offer based on their blocks, registry region, timing and leaseback requirements.
Direct Buyer or Broker
Brokered Transaction
A broker seeks a buyer and assists with the transaction. The seller may gain access to a wider pool of prospective counterparties, but the process can depend on finding and qualifying a third-party buyer.
The seller should ask whether a real buyer has already been identified, whether the indication of interest is binding, who performs due diligence, how the broker is compensated, who coordinates the RIR transfer and what happens if the buyer withdraws.
Direct Sale
In a direct sale, the seller negotiates with the organization acquiring the block. This can shorten the counterparty chain, provide clearer visibility into the buyer and allow the seller to discuss transaction timing or leaseback with the future operator.
The best structure depends on the seller’s priorities. A theoretical price is not the same as an executable offer from a qualified buyer.
Compare Offers Beyond Price per Address
A high headline price can become less attractive if the transaction contains uncertain conditions. Sellers should compare:
• Total purchase price and payment currency
• Payment schedule and settlement structure
• Due diligence conditions
• Registry approval requirements
• Transaction fees and tax considerations
• Representations and warranties
• Buyer identity and expected completion time
• Leaseback terms if continued use is required
• Responsibility for failed or delayed transfers
Published IPv4 market pricing and statistics can provide useful context, but the value of a particular block will still depend on its size, registry region, transfer eligibility, address history, documentation and transaction timing.
The seller should confirm what happens if the registry rejects or delays the transfer. Legal, accounting and tax advisers may be required, particularly for large portfolios, cross-border transactions or resources connected to corporate restructuring.
Build a Coordinated Transition Plan
A successful IPv4 sale should have a written transition plan shared by the relevant business teams.
| Team | Primary responsibility |
|---|---|
| Network operations | Routing, address use and migration |
| Security | Firewalls, allowlists and reputation checks |
| Legal | Transaction agreement and authority |
| Finance | Valuation, payment and accounting |
| Compliance | Registry and corporate documentation |
| IT applications | DNS, APIs and system dependencies |
| Management | Approval and business timing |
The plan should define the prefixes being transferred, the services that must be migrated, the approval process, the intended transfer date, the payment milestone, the routing-change sequence, the owner of each task, the rollback procedure and the final verification process.
No production route should be withdrawn simply because the commercial agreement has been signed. Technical changes should follow the agreed completion and migration sequence.
IPv4 Seller Readiness Checklist
Before contacting a buyer, confirm that the organization can answer the following questions:
• What exact CIDR blocks are available?
• Which RIR administers each block?
• Which legal entity is the registered holder?
• Are the registry contacts accurate?
• Does the organization have access to the RIR account?
• Is the block eligible for transfer?
• Are any addresses still in production?
• Which routes and more-specific prefixes are announced?
• Which ROAs and IRR objects exist?
• Is reverse DNS still required?
• Are customers or partners using the addresses in allowlists?
• Are there known reputation issues?
• Does the organization want to sell the whole block or only part?
• When can the addresses be released?
• Is continued use required after the sale?
• Who has authority to approve the transaction?
• How should payment and registry completion be coordinated?
Providing this information early can help the buyer evaluate the resource and prepare a more meaningful offer.
Frequently Asked Questions
Can a Business Legally Sell IPv4 Addresses
An organization may transfer eligible IPv4 resources to another organization through the applicable RIR process. The parties can enter into a commercial sale agreement, but the registry must still approve and record the transfer according to its policies. Transfer eligibility and documentation requirements depend on the registry and resource status.
How Much Are IPv4 Addresses Worth
The value of an IPv4 block depends on its size, registry region, transfer eligibility, address reputation, routing history, documentation, buyer demand, transaction timing and whether the block must be subdivided. A market average should not be treated as a guaranteed price for a specific block.
How Long Does an IPv4 Transfer Take
The timeline depends on the RIR, documentation quality, buyer readiness, due diligence and whether the transaction is within one registry region or between two RIRs. Incomplete records, corporate changes and unresolved resource issues can extend the process.
Can a Company Sell IPv4 Addresses That Are Still in Use
A company should not transfer active address space without a migration or continuity plan. Possible options include renumbering services before completion, retaining part of the allocation or negotiating a sale-and-leaseback arrangement.
Should a Seller Use a Broker or Sell Directly
A broker may help locate potential buyers, while a direct sale allows the seller to negotiate with the acquiring organization. The decision should consider counterparty certainty, fees, exclusivity, transaction timing, due diligence and whether continued use is required.
What Documents Are Needed to Sell IPv4 Addresses
Requirements vary, but sellers may need corporate registration documents, proof of authority, current registry account access, resource registration information, transfer agreements, officer acknowledgements, merger or acquisition records, and tax and payment documentation. The relevant RIR and transaction advisers should confirm the exact requirements.
Conclusion
Selling IPv4 addresses can convert an underused network resource into capital, but the quality of the outcome depends on preparation.
The seller must identify which addresses are genuinely surplus, confirm the registry transfer path, correct administrative records and understand every operational dependency attached to the block.
For addresses that remain important to production systems, subdivision, planned renumbering or sale and leaseback may provide a more practical route than an immediate full exit.
The goal is to complete a transaction that releases value without creating an avoidable problem for the network left behind.