Summary

  • The exact IPv4 block 152.237.192.0/20 left LACNIC for ARIN on 20 February 2025 and came back on 4 May 2026. V.TAL sent it to Globenet; Globenet sent it to A5X. LACNIC’s two official rows are 438 days apart.
  • LACNIC’s one-year bar on transferring already-transferred addresses supplies a public clock. Today’s RDAP shows A5X and a 13 March 2025 registration event; only the transfer rows reveal the original 2014 registration date and both crossings.

A registry border can be crossed twice without the address moving an inch. LACNIC’s public transfer file supplies the itinerary for 152.237.192.0/20: Brazil to a US organisation under ARIN, then back to a different Brazilian organisation under LACNIC. It is the same 4,096 IPv4 addresses on both tickets. The first recipient was Globenet Cabos Submarinos America Inc.; the final registrant is A5X SA. A current registry lookup tells you where the block is filed. The two transfer entries tell you how it got there.

The first entry is dated 20 February 2025. It names V.TAL - REDE NEUTRA DE TELECOMUNICACOES S.A. as the source, Globenet as the recipient, LACNIC as the source RIR and ARIN as the receiving RIR. Its transfer_set is precisely 152.237.192.0–152.237.207.255, a /20. Its original_set is much larger, 152.236.0.0–152.239.255.255, a /14. The row is a transfer of the /20, not of the whole /14. Confusing those fields would multiply the apparent event by 64.

The return entry is dated 4 May 2026. It names Globenet as the source under ARIN and A5X S.A as the recipient under LACNIC. This time both original_set and transfer_set identify the exact same /20. The transfer dates are 438 calendar days apart. Section 2.3.2.18.6 of LACNIC’s current policy manual bars the full or partial retransfer of previously transferred addresses for one year from the logged transaction date. The second entry sits 73 days beyond a 365-day comparison. The ledger shows the interval and the completed return; it does not disclose the application file or the registrar’s reasoning.

Now open LACNIC’s current RDAP entry. It names A5X SA as registrant of the exact /20. It also records a registration event on 13 March 2025 and a last change on 4 May 2026. That registration date falls 21 days after the first transfer and more than a year before A5X appears in the second row. The first transfer row carries an older source registration date, 15 May 2014; the second carries 13 March 2025. A single RDAP timestamp is a registry event, not an unbroken certificate of one company’s tenure. The resource, its custodial record and its registrant each have a different clock.

This is why the round trip matters beyond the novelty of an address block returning to its starting region. A party checking only today’s RDAP would find the right present holder and the wrong depth of history. A party adding the two public transfer rows can identify the prior holders, the two RIR changes, the exact resource and the cooling interval. LACNIC’s manual requires a public transfer log precisely so a registration change can be read as an event, not merely as a new name on a page.

The record does not publish the price, contract, network cutover or commercial link between these organisations; those documents would be needed to describe the business deal.