Summary

  • RIPE NCC's public ledger records seven policy transfers from VODAFONE ONO on 18 August 2026. Eight resulting prefixes, totalling 7,168 IPv4 addresses, went to seven organisations in Estonia, Germany, Bulgaria, Armenia, Croatia and Iraq.
  • The breakup is market evidence, not a valuation record. It shows that a legacy holder could separate inventory into lots ranging from 256 to 4,096 addresses, yet discloses no consideration, lease or sale structure, broker, warranty, financing or remediation cost.
  • A 24 August exact-prefix routing check found one of the eight prefixes visibly originated in the returned RIPEstat snapshot. That gap is not proof that the others were unused; it is a warning that registry completion and network activation are different milestones.

Seven receipts, eight pieces

Transfer ledgers rarely look dramatic. Their power lies in the way a bland row can constrain a market story. RIPE NCC records the offering party, receiving party, date, transfer type and the actual subdivided prefixes. For the Vodafone ONO sequence, those fields are enough to reconstruct a small inventory event without pretending to know the private bargain.

Two adjacent /24s, 2.152.78.0/24 and 2.152.79.0/24, moved separately from the same original /22. Bifrost Systems OU received the first; Wunderkopf Technologies GmbH the second. Another original allocation, 2.152.80.0/20, supplied two non-contiguous lots—2.152.88.0/24 and 2.152.92.0/23—to HZ Hosting Ltd. TWS technologies GmbH received 2.152.94.0/23. Telecom Armenia OJSC received 80.173.175.0/24, Pronect Technology LTD received 82.158.188.0/22, and I.Q Online for Internet Services and Communications LLC received the largest piece, 85.155.192.0/20.

The arithmetic is 7,168 addresses: 4,096 in the /20; 1,024 in the /22; two /23s; and four /24s. More important than the total is the distribution. The event cleared a very large difference in lot size on one date. One buyer took 256 addresses. Another took sixteen times as many.

That is what market segmentation looks like when price is absent. Different buyers can have different needs: a contained service, a new hosting cluster, customer assignments, a replacement pool or simply inventory for a planned network. The ledger cannot identify which explanation applies. It can show that the administrative unit of trade was not one indivisible estate.

A transaction ledger without the transaction price

Public address-transfer data are often treated as if they were a thin financial tape. They are not. RIPE NCC verifies and processes a transfer under policy, updates registry holdership and publishes the approved record. Its own transfer guidance says the registry service is provided free of charge. That does not mean the addresses changed hands for no consideration. It means the registry is not charging a processing fee.

The commercial layer remains private. The public rows do not say whether the parties used a sale, lease, option or broader asset agreement. They do not name an intermediary. They do not disclose a per-address price, a payment schedule, escrow, tax treatment, representations about historical abuse, indemnities, renumbering support or the cost of cleaning reputation data. They do not tell us whether a larger commercial agreement was allocated across multiple prefixes.

For market analysts, the distinction is more than legal hygiene. A registry count can measure transferred supply, but it cannot by itself support a price index. Multiplying 7,168 by a quoted broker average would create an estimate whose apparent precision exceeds the evidence. Prefix condition, origin history, geolocation residue, route-object readiness, contractual risk and timing can all change effective value. Even the meaning of “buyer” can vary if the registered recipient is operating for customers or under a financing arrangement.

The right description is therefore narrow: Vodafone ONO was the offering party in seven completed policy-transfer entries. The destination records changed. Everything about consideration remains undisclosed.

Why the breakup matters

The subdivision carries information that a headline total would erase.

First, it reveals a matching function. An IPv4 /20 is not merely sixteen /24s in economic practice. A large contiguous block may suit a network that can route and manage it as one object. A smaller buyer may not want to fund, secure or justify that much inventory. Splitting can widen the buyer set, though it can also introduce engineering and transaction overhead.

Second, the destination pattern shows cross-border demand without proving where packets will ultimately flow. The receiving organisations are registered across Estonia, Germany, Bulgaria, Armenia, Croatia and Iraq. Those country fields locate registry relationships, not necessarily every server, router or customer. Still, one Spanish offering party reaching six destination jurisdictions on the same date is evidence that the relevant clearing market is not merely domestic.

Third, policy changes the inventory clock. RIPE-807 generally prevents transferred address space from being transferred again for 24 months, with defined exceptions. A recipient may route the space, assign it within its network or hold it for deployment, but it cannot ordinarily treat the block as instantly recyclable transfer inventory. That restriction matters to any model of dealer turnover or speculative velocity. The transfer ledger records flow; policy limits how quickly the same units can reappear as flow.

Finally, partial transfers leave remainders. Analysts should resist assuming that an original allocation has been sold in full merely because fragments appear in the table. The correct unit is the listed transferred prefix, not the historical parent. A seller can monetise or redistribute selected portions while retaining other space, and the public record needs to be read at prefix level.

Registration is not activation

After a transfer, RDAP can show the new registration state before the destination network announces the exact prefix—or without the destination ever announcing that exact granularity. That sequencing appeared in the 24 August snapshot.

For 2.152.78.0/24, RIPEstat returned AS48539 as an exact origin and visibility at 327 of 328 RIS peers in the response. For the other seven exact transferred prefixes, the routing-status query returned no exact origin at that moment. The observation is useful precisely because it is limited.

It does not prove that seven lots were idle. A more-specific prefix may be covered by an aggregate. A recipient may be staging filters, route objects, RPKI authorisations, geolocation updates or customer provisioning. A block may be reserved for later capacity. A single observation can also miss changes before or after the query.

What it does prove is that “transfer date” should not be used as a synonym for “revenue-generating route date”. Registry completion establishes a custody and accountability milestone. Route visibility measures a different operational state. Commercial usefulness may require further steps again: acceptance by upstreams, clean abuse reputation, stable geolocation, reverse DNS, customer assignments and application traffic.

A market that reports only completed transfers risks compressing all of those states into one false instant.

The missing price is itself a market feature

The IPv4 transfer market combines a relatively strong public ownership-change trail with weak public commercial disclosure. That asymmetry encourages two errors. The first is to ignore the ledger because it lacks price. The second is to invent price by attaching a generic quote to every transferred address.

The better use is to separate observables. The Vodafone ONO event supplies a volume, a date, a source holder, named recipients, lot sizes, policy type and registered destination jurisdictions. Routing data can add time-stamped operational observations. None supplies consideration.

This separation also improves comparison over time. Analysts can track whether transfers are becoming more fragmented, whether /24s account for a growing share of rows, how often one offering party distributes to multiple jurisdictions, and how long exact-prefix visibility appears to lag registry change. Those are real market measures. They do not need a fabricated dollar value to become informative.

For buyers, the same discipline belongs in due diligence. A transfer approval is necessary evidence, but it is not the whole deliverable. A usable closing checklist should distinguish registry update, authority to route, route-object and RPKI state, reputation screening, geolocation correction, upstream acceptance and actual production announcement. Payment milestones can then attach to evidence rather than to a single administrative date.

What this event does—and does not—say about Vodafone ONO

The seven rows show that Vodafone ONO supplied selected address space to the transfer process. They do not disclose motive. The company may have identified surplus space, reorganised allocations, responded to unsolicited demand or executed a broader portfolio decision. The sources used here do not choose among those explanations.

Nor does the breakup establish that the entire historical parent blocks were available. Several rows are partial transfers. Reading the event as a wholesale exit from IPv4 assets would go beyond the evidence.

The disciplined market conclusion is smaller but durable. A legacy telecom allocation can be separated into buyer-sized lots and redistributed across several jurisdictions through one registry system. The resulting receipt is good evidence of a completed administrative transfer. It is poor evidence of price and incomplete evidence of deployment.

That is not a defect in the ledger. It is a description of what the ledger controls.

Sources