Skip to main content

IPv4 guide

How Much Are My IPv4 Addresses Worth in 2026? A Seller Valuation Guide

Stephanie
ipv4-addresses

If your organization holds unused or underused IPv4 address space, one of the most important questions is:

Table of Contents

How much are my IPv4 addresses worth in 2026?

There is no single fixed market price for an IPv4 address.

The achievable value of an IPv4 block depends on the specific resource being offered, including its block size, Regional Internet Registry (RIR), transfer eligibility, registration condition, reputation, routing history, buyer demand and transaction timing.

For sellers, the strongest valuation is therefore not:

number of addresses × one universal IPv4 price

It is a block-specific assessment based on current market evidence and the operational condition of the resource.

This guide explains how to estimate IPv4 value in 2026, which factors can affect marketability, how to prepare a block for valuation, and how sellers can compare selling with retaining or leasing their IPv4 resources.

Quick Answer: How Much Are IPv4 Addresses Worth in 2026?

An IPv4 block does not have one universal value.

i.lease’s existing 2026 market guidance notes that purchase prices can vary significantly by block size, region and resource quality. Its broader guide to what determines IPv4 pricing describes a market in which block size, scarcity, demand, RIR policy and reputation all influence price.

For smaller resources, i.lease’s dedicated guide to how much a /24 IPv4 block costs in 2026 places a /24 in a broad 2026 range of approximately $6,000 to $15,000, depending on the block and transaction context.

That range should not be applied automatically to larger resources.

A /24, /20 and /16 can have very different per-address market dynamics. Large blocks require larger buyers, while smaller blocks can reach a broader buyer population. Reputation, registry status and transfer readiness can further affect how quickly a block can be evaluated and sold.

The practical answer: use current pricing for a comparable block size, then adjust the valuation for the specific characteristics of your IPv4 resource.

2026 IPv4 Market Activity: What Official Registry Data Shows

Price data is only one way to understand the IPv4 market. Official Regional Internet Registry data also shows that IPv4 resources continue to move between organizations in substantial volumes.

For example, the RIPE NCC reported that 2,874,112 IPv4 addresses were transferred in April 2026. Its June 2026 member update reported another 1,913,088 IPv4 addresses transferred in May, while 713 LIRs remained on the IPv4 waiting list.

See the official RIPE NCC June 2026 Member Update and RIPE NCC IPv4 Transfer Statistics.

ARIN also publishes current-year statistics covering in-region IPv4 transfers and inter-RIR transfers, while APNIC provides statistics and raw transfer data for the Asia-Pacific region.

See ARIN Statistics & Reporting and APNIC Statistics.

These figures do not tell a seller the price of a specific block. Transfer volume is not the same as market value.

What they do show is that IPv4 redistribution remains an active part of Internet resource management in 2026.

How to Value Your IPv4 Block: A Seller Framework

A useful seller valuation can be built in seven steps.

Step 1: Identify Exactly What You Control

Start with the actual prefixes.

Do not begin with:

“We have roughly 20,000 unused IP addresses.”

Instead, create an exact resource inventory.

For each prefix, record:

  • Exact CIDR
  • Prefix length
  • Number of IPv4 addresses
  • Current RIR
  • Registered organization
  • Resource status
  • Legacy status where relevant
  • Transfer history
  • Current routing status

For example:

192.0.2.0/24
198.51.100.0/22
203.0.112.0/20

This matters because 65,536 addresses contained in one contiguous /16 can have a different market profile from the same number of addresses fragmented across many unrelated prefixes.

Step 2: Calculate the Address Count

Step 2: Calculate the Address Count
PrefixIPv4 Addresses
/24256
/23512
/221,024
/212,048
/204,096
/198,192
/1816,384
/1732,768
/1665,536

The address count provides the numerical basis for a valuation, but it is only the starting point.

Step 3: Establish a Comparable Market Benchmark

The next step is to identify a current benchmark for resources of a similar size and transaction profile.

A basic calculation is:

Indicative gross value = address count × comparable current price per address

For example, a /24 contains 256 addresses. If the relevant current benchmark for that specific type of /24 were $30 per address, the indicative gross value would be:

256 × $30 = $7,680

If the relevant benchmark were $40:

256 × $40 = $10,240

This does not mean every /24 is worth $7,680–$10,240. i.lease’s own /24 guide uses a broader 2026 range because different blocks and transactions can produce different results.

The objective is to establish a comparable starting point—not a guaranteed selling price.

Step 4: Evaluate Marketability

Now evaluate the specific block.

Ask:

  • Is the registration clear?
  • Is the current holder accurately reflected in the RIR record?
  • Is the resource eligible for transfer?
  • Does a transfer restriction or holding period apply?
  • Is the block contiguous?
  • Does it have material reputation problems?
  • Are the organization’s registry contacts current?
  • Is the proposed intra-RIR or inter-RIR transfer path available?
  • Is routing history understood?
  • Are RPKI, IRR and reverse DNS records clear?

This stage is what turns a generic market benchmark into a resource-specific seller valuation.

If you are preparing a transaction, use the i.lease IPv4 transfer document checklist to review corporate identity, signatory authority, RIR information, transfer forms and other supporting records before closing.

Step 5: Estimate a Gross Market Range

Once comparable pricing and marketability have been reviewed, estimate a realistic range rather than one exact number.

A useful valuation might say:

Estimated gross market range: $X–$Y based on current comparable pricing, block size, registration condition and transfer readiness.

This is more useful than declaring:

“Your IPv4 block is worth exactly $X.”

IPv4 is not traded on a centralized exchange with one transparent real-time price. Transaction values can vary with buyer needs, block size, resource condition, registry pathway and timing.

Step 6: Estimate Net Proceeds

Gross market value is not necessarily the same as the money the seller ultimately receives.

Depending on the transaction, costs may include:

  • Marketplace or transaction fees
  • RIR fees
  • Escrow costs
  • Legal costs
  • Corporate documentation work
  • Tax considerations
  • Network migration or renumbering costs

The seller should therefore calculate:

Estimated net proceeds = expected sale proceeds − transaction-related costs

For a large allocation, even a small percentage difference between gross and net proceeds can be material.

Step 7: Compare Selling With Retaining or Leasing the Resource

Finally, compare the current sale opportunity with the strategic value of keeping the resource.

Ask:

  • Could the organization need the addresses again?
  • Is immediate capital more valuable than retaining the asset?
  • Could leasing produce useful recurring revenue?
  • Can the organization manage abuse, reputation and routing responsibilities if it leases?
  • What is the opportunity cost of keeping unused IPv4?

For organizations considering recurring revenue rather than a permanent sale, see i.lease’s guide to turning idle IPv4 addresses into recurring revenue.

Why Block Size Affects IPv4 Value

A common valuation mistake is applying one price per address to every block size.

Different prefixes serve different buyer groups.

A /24 contains 256 addresses and can be practical for smaller networks or incremental capacity requirements.

A /16 contains 65,536 addresses and requires a buyer with much larger network requirements and capital capacity.

As a result, smaller blocks can sometimes command a higher price per address even though large blocks are worth substantially more in total.

i.lease discusses this pricing asymmetry in its guide to IPv4 pricing factors.

Seller valuation should therefore compare the block with transactions and demand for a similar prefix size—not simply with the most visible price in the market.

Why Contiguous IPv4 Space Matters

Consider two organizations that each control 65,536 addresses.

Organization A controls one /16.

Organization B controls the same number of addresses distributed across many unrelated smaller prefixes.

These holdings are not necessarily equivalent.

Contiguous address space can simplify:

  • BGP routing
  • IP address management
  • Customer assignments
  • RPKI administration
  • IRR maintenance
  • Network documentation

However, smaller blocks may appeal to more buyers and can have different per-address pricing.

The effect on value depends on current demand and how the seller wants to structure the transaction.

Does the RIR Affect IPv4 Value?

IPv4 resources are registered through one of five Regional Internet Registries:

  • ARIN
  • RIPE NCC
  • APNIC
  • LACNIC
  • AFRINIC

The Number Resource Organization provides an overview of the five-RIR system and their respective service regions.

The RIR should not be treated as a simplistic price premium or discount.

Instead, it can affect marketability through the transfer pathway.

Important questions include:

  • Is the resource currently transferable?
  • Is the source recognized as the registered holder?
  • Does a holding period apply?
  • Does the recipient need to demonstrate need?
  • Can the resource move to another RIR?
  • Is the proposed inter-RIR pathway currently supported?
  • What documentation will the parties need?

Official transfer guidance is available from ARINRIPE NCCAPNICLACNIC, and AFRINIC.

For a practical 2026 comparison, see i.lease’s guide to which RIRs support inter-RIR IPv4 transfers in 2026.

Transfer Readiness Can Affect Marketability

A block may have a strong theoretical value but still be difficult to transact if the seller is not transfer-ready.

Common problems include:

  • The registered organization uses an old company name
  • The RIR account is controlled by a former employee
  • Corporate succession is not documented
  • The signer cannot demonstrate authority
  • A resource is still subject to a transfer restriction
  • The intended inter-RIR path is not available
  • Registry information conflicts with current company records

These issues do not automatically make a block less valuable.

But they can increase uncertainty, delay completion and narrow the buyer pool.

A seller should therefore review transfer documentation before treating an IPv4 block as ready for market.

Use the i.lease guide What Documents Are Needed for an IPv4 Transfer? for a buyer-and-seller checklist covering company records, authority, RIR accounts, resource information and transaction documentation.

Does IPv4 Reputation Affect Value?

IPv4 addresses develop operational history.

A block may previously have been associated with:

  • Hosting
  • Email infrastructure
  • VPN services
  • Proxy services
  • Customer assignments
  • Automated workloads
  • Abuse incidents
  • Malware or spam activity

Potential buyers may investigate this history before completing an acquisition.

Significant unresolved issues can create additional work involving security classifications, blocklists, email reputation, geolocation and customer acceptance.

For this reason, reputation can influence buyer confidence and marketability.

However, sellers should avoid relying on vague claims such as “100% clean IPs.”

A stronger approach is to provide dated evidence and allow the buyer to complete independent due diligence.

RPKI, IRR, Reverse DNS and Routing History

Registration status is only one part of an IPv4 resource’s operational condition.

Buyers may also ask:

  • Is the prefix currently announced?
  • Which ASN originates it?
  • Does a ROA currently exist?
  • Which IRR route objects exist?
  • Who controls reverse DNS?
  • When will existing routing be withdrawn?
  • What will need to change after transfer?

Clear technical records can make the handover easier to evaluate.

i.lease covers the post-transfer lifecycle in What Happens to IPv4 Records After an IP Address Transfer?, including WHOIS/RDAP, RPKI, IRR, reverse DNS, BGP, geolocation and reputation.

Why Historical IPv4 Prices Can Mislead Sellers

IPv4 values have changed substantially over time.

A price observed during a previous market cycle does not establish what a block is worth today.

This creates two common mistakes:

“IPv4 once sold at a much higher price, so my block must still be worth that amount.”

and:

“I saw one low-priced transaction, so all blocks must now be worth less.”

Neither approach accounts for block size, resource quality, current demand or transaction structure.

For historical context, see i.lease’s IPv4 Address Price History From Exhaustion to 2026.

Historical data is useful for understanding the market cycle.

Current comparable evidence is more useful for seller valuation.

How Much Is a /24 IPv4 Block Worth in 2026?

A /24 contains 256 addresses.

i.lease’s dedicated 2026 /24 pricing guide currently describes a broad range of approximately $6,000–$15,000 per /24, reflecting differences in source, reputation and transaction context.

This should be treated as a planning reference, not a guaranteed offer.

For a detailed breakdown, read How Much Does a /24 IPv4 Block Cost in 2026?.

How Much Is a /20 or /16 IPv4 Block Worth?

A /20 contains 4,096 addresses.

A /16 contains 65,536 addresses.

The correct approach is not to multiply those address counts by a /24 per-address price.

Large-block pricing can behave differently because the buyer pool, transaction size, liquidity and demand profile are different.

For larger holdings, use:

address count × a current benchmark for a comparable block size

and then adjust for:

  • RIR and transfer route
  • Registration condition
  • Contiguity
  • Reputation
  • Routing history
  • Documentation readiness
  • Current buyer demand

This is why a seller with a /16 should request a current large-block valuation instead of extrapolating from small-block pricing.

Should I Sell My IPv4 Addresses in 2026?

There is no universal answer.

Official RIR data confirms that IPv4 transfers remain active in 2026, but market activity alone does not determine whether selling is right for a particular organization.

A sale may make sense when:

  • The resources are genuinely surplus
  • The organization does not expect to need them again
  • Immediate capital is strategically useful
  • The business wants to reduce future resource-management responsibilities
  • The current buyer market supports an acceptable valuation

Retaining the addresses may make more sense when they remain important to the organization’s infrastructure or future expansion.

The better question is not:

“Will IPv4 prices go up or down?”

It is:

“What is the best use of this IPv4 resource for our organization under current conditions?”

Sell or Lease IPv4?

Organizations with surplus IPv4 have another choice: lease rather than sell.

Selling

Selling generally provides:

  • A one-time capital realization
  • Permanent transfer of the resource
  • Reduced future responsibility for the block after completion

Leasing

Leasing can provide:

  • Recurring revenue
  • Retention of the underlying IPv4 resource
  • Future optionality

But leasing also introduces continuing responsibilities around abuse, reputation, routing, customer use and renewal.

For the detailed leasing model, see How to Turn Idle IPv4 Addresses Into a Recurring Revenue Stream with i.lease.

IPv4 Seller Valuation Checklist

Resource Information

  • Exact CIDR prefix or prefix list
  • Total address count
  • Current RIR
  • Registration status
  • Resource history
  • Legacy status where relevant
  • Transfer restrictions reviewed

Organization Information

  • Current legal company name
  • RIR organization record
  • Registry account access
  • Authorized contacts
  • Signatory authority
  • Corporate succession records where applicable

Technical Information

  • Current origin ASN
  • RPKI / ROA status
  • IRR route objects
  • Reverse DNS status
  • Routing history

Reputation

  • Abuse history reviewed
  • Relevant blocklists checked
  • Email reputation considered where relevant
  • Geolocation reviewed
  • Third-party classifications understood

Commercial Decision

  • Preferred transaction timing
  • Internal future IPv4 needs reviewed
  • Comparable market benchmark identified
  • Gross and net value separated
  • Transaction costs considered
  • Sell versus lease compared

Common IPv4 Valuation Mistakes

Using One Price for Every Block

A /24 and /16 do not necessarily trade at the same price per address.

Using an Old Peak Price

A historical price does not automatically represent current market value.

Ignoring Transfer Eligibility

A headline valuation is less useful if the proposed transaction cannot proceed under the relevant RIR rules.

Ignoring Reputation

Operational history can affect buyer confidence and deployment effort.

Confusing Gross Value With Net Proceeds

Transaction-related costs should be included in the seller’s decision.

Assuming Registry Transfer Equals Operational Handover

RPKI, IRR, reverse DNS, BGP, geolocation and other records may still require work after the registry transfer.

How i.lease Supports IPv4 Sellers

i.lease provides a structured marketplace process for organizations considering the sale of surplus IPv4 resources.

The seller workflow includes:

  1. Asset assessment and valuation
  2. Reputation review
  3. Buyer matching
  4. Managed RIR transfer coordination
  5. Escrow-supported payout

A useful seller assessment should answer more than:

“What is today’s price per IP?”

It should help establish:

  • Which resources are being sold
  • Whether they are transfer-ready
  • How their block size affects the buyer pool
  • Whether reputation or registration issues need attention
  • What current buyers may pay for comparable resources
  • What the seller may receive after transaction costs

If your organization holds surplus IPv4 resources, review Sell IPv4 Addresses through the i.lease Marketplace to start an asset assessment.

Frequently Asked Questions

1. How much is one IPv4 address worth in 2026?

There is no single fixed price. IPv4 value can vary according to block size, RIR, transferability, reputation, registration condition, buyer demand and transaction timing. Sellers should compare their resource with current pricing for a similar block size rather than use one universal per-IP figure.

2. How do I calculate what my IPv4 block is worth?

Identify the exact prefix and address count, establish a current benchmark for a comparable block size, then evaluate transfer readiness, reputation, registration condition and buyer demand. Finally, subtract expected transaction-related costs to estimate potential net proceeds.

3. How much is a /24 IPv4 block worth?

A /24 contains 256 addresses. i.lease’s dedicated 2026 guide describes a broad market range of approximately $6,000–$15,000 for a /24, depending on source, quality and transaction context. It should be used as a planning reference rather than a guaranteed valuation.

4. Does the RIR affect IPv4 value?

The RIR can affect the available transfer path, eligibility requirements, documentation and potential buyer pool. It is more useful to evaluate the specific transaction pathway than to assign a universal premium or discount to an RIR.

5. Does IPv4 reputation affect value?

Reputation can affect marketability and buyer confidence. Significant unresolved abuse, blocklist or security-history issues can require additional due diligence or remediation. Sellers should use dated evidence rather than broad claims that a block is “clean.”

6. Are larger IPv4 blocks worth more?

Larger blocks contain more addresses and can therefore have much greater total value, but their per-address price may differ from smaller blocks. Buyer population, liquidity and demand vary by block size.

7. Is 2026 an active year for IPv4 transfers?

Yes. Official registry data shows continued transfer activity. The RIPE NCC reported 2,874,112 IPv4 addresses transferred in April 2026 and 1,913,088 in May 2026. ARIN and APNIC also continue to publish current transfer statistics and transfer data. Transfer volume does not determine the price of a particular block, but it demonstrates continued redistribution of IPv4 resources.

8. Can I lease my IPv4 addresses instead of selling them?

Yes. Selling typically provides a one-time payment and transfers the resource, while leasing can provide recurring revenue while the holder retains the address space. The better strategy depends on cash-flow goals, risk tolerance, operational capability and future IPv4 requirements.

Final Thoughts

The question “How much are my IPv4 addresses worth?” cannot be answered responsibly with one universal price.

A stronger seller valuation considers:

Current comparable pricing + block size + transferability + RIR pathway + registration condition + reputation + operational clarity + transaction timing

Official 2026 registry data confirms that IPv4 transfers remain active. At the same time, i.lease’s own pricing guidance shows why block size and resource quality matter when estimating value.

Before selling:

  1. Inventory the exact prefixes.
  2. Verify registration and corporate authority.
  3. Confirm transfer eligibility.
  4. Review routing and reputation.
  5. Use a current comparable benchmark.
  6. Estimate gross and net proceeds separately.
  7. Compare selling with retaining or leasing the resources.

Then make the decision based on the value of your specific IPv4 resources, rather than an outdated headline price.

Have unused or surplus IPv4 resources? Request an IPv4 asset assessment through i.lease and evaluate your options based on block size, transfer readiness and current buyer demand.

1. Does WHOIS automatically change after an IPv4 transfer?

The relevant RIR updates registration information as part of an approved transfer according to its procedures. Buyers should still verify the resulting WHOIS or RDAP records after completion to confirm that the expected organization and contact information is visible.

2. What happens to a ROA after an IPv4 transfer?

The exact process depends on the RIR. Existing authorization associated with the source may be removed or cease to apply, and the recipient may need to create a new ROA for the IPv4 prefix and intended origin ASN. ARIN, for example, removes transferred resources and their associated ROAs from the source’s RPKI certificate.

3. Do PTR records transfer with an IPv4 block?

Not necessarily. Reverse DNS authority and PTR configuration should be reviewed during the handover. In some inter-RIR transfers, reverse DNS delegation is removed from the source registry and must be recreated through the receiving registry.

4. Does IPv4 geolocation update automatically after a transfer?

No. Geolocation is maintained by multiple third-party providers and platforms. Registry transfer information may be one signal, but operators may need to publish geofeed data or submit corrections to individual providers.

5. Does an IPv4 transfer remove the block's previous reputation?

No. Historical reputation data is maintained independently by third-party systems. Buyers should check the reputation and abuse history of an IPv4 block before acquisition and continue monitoring it after deployment.