Three Vodafone blocks to LACNIC; RDAP names Liberty

RIPE Sent Three Vodafone Blocks to LACNIC. The Recipient’s Name Was Elsewhere.

Why it matters

Three adjoining IPv4 blocks left Vodafone ONO in RIPE’s 3 November ledger. The destination field says only LACNIC; the receiving registry’s exact holder records say Liberty Networks de Colombia.

Theo March3 November 2026Reading Time 2 minLast update: 3 November 2026

RIPE lists three Vodafone ONO blocks headed to LACNIC; exact LACNIC RDAP entities name Liberty Networks de Colombia while the morning transfer export predates them.

Summary

RIPE NCC’s outgoing transfer table lists three permanent policy transfers from VODAFONE ONO, S.A. to LACNIC on 3 November 2026: a /20, /22 and /23 totaling 5,632 IPv4 addresses.
Three exact LACNIC RDAP objects name LIBERTY NETWORKS DE COLOMBIA S.A.S as registrant. LACNIC’s morning transfer export was produced before those registrations and contains none of the three rows.

The sending ledger knows where the blocks went. It will not tell you who received them. On 3 November, RIPE NCC added 2.152.224.0/20, 2.152.240.0/22 and 2.152.244.0/23 to its outward inter-RIR table, each from VODAFONE ONO, S.A. and each with LACNIC as destination. The three intervals touch without overlapping: 4,096, 1,024 and 512 addresses, or 5,632 in all. A reader looking for the recipient in that table finds a registry acronym where a company name ought to be.

The name sits in the other institution’s database. LACNIC’s exact first /20 object, next /22 object and last /23 object each show CO-CNIT-LACNIC as registrant and spell out LIBERTY NETWORKS DE COLOMBIA S.A.S. Their registration times are 12:58:46, 12:59:13 and 12:59:41 UTC. Each object’s boundaries match its RIPE transfer row. The recipient is established by three exact cards, not by guessing from a parent prefix.

LACNIC’s dated 3 November cumulative transfer file was generated at 08:32:01 UTC. It still contains 1,922 rows, with the latest transfer date 29 October, and none of these ranges. That snapshot predates the RDAP registrations by more than four hours. The export and live holder database answer different questions at different moments. To audit this handover from public records today, one must cross RIPE’s outward table with LACNIC’s exact objects. The next LACNIC transfer export can supply the missing file-level recipient row; a shared case log would identify the precise effective handover step.