How to Read IPv4 Transfer Market Data

Table of Contents

Begin with the question

IPv4 transfer statistics look simple until two reports appear to tell different stories. One may count transferred addresses, another may count approved requests, and a third may cover only one registry region. Each measure can be valid while answering a different question. Useful analysis begins by defining whether the reader wants to understand liquidity, transaction frequency, regional movement, available block sizes, or the continuing effects of address scarcity.

A current review of IPv4 transfer market data shows why that discipline matters. Reported global transfer volume rose from about 30.2 million addresses in 2024 to 33.4 million in 2025, yet remained below the roughly 44.3 million reported for 2022. The series indicates active redistribution, not a smooth or unlimited expansion of supply.

Compare the same metric

The first check is the unit of measurement. Address volume totals the individual IPv4 addresses contained in transferred prefixes. Transaction count records how many transfer events occurred. A single large block can exceed the address volume of hundreds of small transactions, so high volume does not necessarily mean that more organizations completed transfers. Conversely, a busy small-block market can produce many transactions without a striking address total.

Year	Reported transfers	Interpretation
2022	44.3 million	A high-volume year in the series
2023	25.3 million	A sharp year-on-year decline
2024	30.2 million	Volume recovered from 2023
2025	33.4 million	Growth continued but stayed below 2022

These figures are drawn from consolidated regional data discussed in the APNIC annual address review. Analysts should preserve the source’s definitions when updating the series, because an apparent trend can change if transfer categories or reporting methods are mixed.

Check the reporting boundary

Regional Internet Registries operate under separate service regions and policy frameworks. A figure for ARIN, APNIC, RIPE NCC, LACNIC, or AFRINIC is therefore a regional observation, not a direct estimate of the whole market. Inter-RIR transfers add another complication because the same movement may be described from the source region, the recipient region, or both, depending on the report.

Before comparing regions, confirm how the underlying IP address registry system records allocations, assignments, organizations, and transfers. Then note the reporting period, transfer type, direction of movement, and whether organizational changes such as mergers are included. Those details prevent unlike categories from being treated as one market measure.

Expect large monthly swings

Monthly transfer volume can be volatile because block sizes vary widely. RIPE NCC reported about 16.72 million transferred addresses from January through July 2026, with approximately 5.94 million in July alone. July represented more than one third of the seven-month address volume. That concentration may reflect the timing of large transfers rather than a sudden, equally broad increase in demand.

Use a rolling period or a full year when possible. Review the distribution of prefix sizes alongside the total, and identify whether one or two large blocks dominate the result. A monthly spike is a prompt for investigation, not enough evidence for a market-wide conclusion.

Separate activity from price

Registry transfer data is not a price index. Public transfer logs may show that a prefix moved, but they generally do not disclose the commercial terms, service fees, financing, warranties, broker arrangements, or other conditions that affect the transaction. Dividing an estimated market value by the number of addresses can create a precise-looking figure that the source data does not support.

For current operational counts, use registry reporting such as ARIN statistics and reporting. For price analysis, use a source that documents its transaction sample, block-size mix, region, dates, and treatment of outliers. Keep the two datasets separate until their scope is compatible.

Do not confuse turnover with new supply

Transferred addresses already exist within the IPv4 address space. A transfer changes who can use or administer a resource under the applicable framework; it does not create additional IPv4 addresses. Higher turnover can improve access to underused space and move resources toward new operators, but the fixed protocol space remains constrained.

APNIC’s explanation of IPv4 exhaustion and address transfers places transfers in the wider transition from depleted free pools to reuse of existing resources. IPv6 deployment remains the structural path to a much larger address space, even when IPv4 transfers continue to support present-day systems.

Use a repeatable review method

State the decision the data will inform, such as capacity planning, regional sourcing, or transfer timing.
Record the source, reporting period, registry region, transfer category, and direction of movement.
Compare transaction count with address volume and review the prefix-size distribution.
Test whether a few large blocks explain a monthly or annual change.
Keep transfer activity, available inventory, and price evidence in separate measures.
Treat scarcity as a supply constraint and transfers as redistribution within that constraint.

This method produces a narrower conclusion than a headline, but it is more useful. It shows what changed, which part of the market changed, and what the evidence still cannot establish.

Read the trend with its limits

Recent transfer volumes confirm that IPv4 resources continue to move between organizations and regions. They do not show that scarcity has ended, that prices must follow the same direction, or that every operator can obtain the block size it needs on the same terms. The sound conclusion is specific: transfer activity is measurable and active, while interpretation depends on transaction type, block size, region, and time period.