Summary

  • LACNIC's 2 November transfer file has eleven IPv4 RESOURCE_TRANSFER rows into EVEO S.A. from ten Brazilian source organisations between 9 May 2023 and 20 October 2026. Their nonoverlapping ranges contain 32,256 addresses.
  • Eleven current LACNIC RDAP records still name EVEO S.A. as registrant for the exact transferred ranges. The largest two /19s account for 16,384 addresses, just over half the total.

EVEO S.A. did not arrive in LACNIC's transfer history with one triumphant superblock. It arrived eleven times. The registry's 2 November cumulative file begins this particular trail with a /22 from GOPLEX TELECOMUNICAÇÕES E INTERNET LTDA on 9 May 2023. It ends, so far, with an /19 from Data Corpore on 20 October 2026. Ten names supplied the blocks; LINSAT - SISTEMAS DE TELEVISAO E DADOS LTDA appears twice. Add the transferred intervals without counting an address twice and the total is 32,256. The number is visible only after someone joins the receipts.

The latest line is large enough to make the pattern hard to miss. Data Corpore's 177.223.192.0–177.223.223.255 moved as an intact /19: 8,192 addresses. Another /19, 177.136.224.0–177.136.255.255, came from V M P TELECOMUNICACOES LTDA on 23 October 2024. Together those two rows account for 16,384 addresses, or about 50.8% of this eleven-row total. The other nine rows range from a 512-address /23 to a 4,096-address /20. This is accumulation by different-sized pieces, rather than a neat, contiguous allocation waiting to be renamed.

One day shows how a portfolio can grow while the public log still looks like errands. On 2 July 2025, four rows came into EVEO: two /22s from LINSAT, a /20 from NETLINE TECNOLOGIA EM TELECOMUNICACOES LTDA, and a /22 from WIID Telecomunicações do Brasil. They total 7,168 addresses in four nonadjacent ranges. LACNIC gave them four separate lines, as a transfer log should. A reader looking for the recipient's cumulative position has to do the arithmetic separately. Transaction-level transparency is useful; portfolio-level visibility requires a second question.

The trail stays inside one jurisdictional frame. All eleven rows identify Brazil for both source and recipient, and LACNIC as both source and destination RIR. There is no cross-RIR handoff in the eleven receipts. The dates span 1,260 days from the first to the latest row. The administrative route is therefore unusually clean for analysis: one registry, one receiving name, exact IPv4 intervals, and a sequence long enough to show an operating pattern rather than a single lucky afternoon.

Current LACNIC RDAP for the latest /19 names EVEO S.A. as registrant and keeps the exact bounds of the transfer. The 2024 /19 does the same. The other nine current RDAP objects also return EVEO as registrant; the exact-prefix receipts appear below. That cross-check matters. A transfer file records what happened at a point in time. The current holder view shows that these eleven blocks still sit under one name in the registry today.

LACNIC's IPv4 transfer policy demands a publicly accessible log with date, source, recipient and addresses, then instructs LACNIC to update holder information after a transfer. It also requires recipient justification and signed supporting documents for transfers within the region. The public record thus gives a strong chain of registered control. The missing piece is the consideration and operational plan behind the eleven transactions; a disclosed agreement or dated deployment record would change what can be said about either.

The registry has done two important things at once. It made each movement checkable, and it made the resulting holder checkable. It did not assemble the answer to the question an operator, buyer or policymaker may ask first: how much transferred space has one recipient accumulated, from whom, and over what period? The raw materials are public, but the join is left to the reader. In a market of scarce, movable identifiers, that extra calculation is the difference between seeing eleven mundane receipts and seeing a 32,256-address portfolio.

Current LACNIC RDAP receipts: