Summary

  • LACNIC and ARIN record 179.238.0.0/15, 131,072 IPv4 addresses, moving from V.TAL to Globenet in ARIN on 20 February 2025. The block did not travel onward as one piece: its lower /16 moved to STARLINK CHILE SPA in LACNIC on 23 June 2026, and its upper /16 moved to Simba Telecom in APNIC on 14 September.
  • Each exit covered exactly 65,536 addresses. The two current exact RDAP objects name STARLINK CHILE SPA and Simba Telecom Pte Ltd. The original /15 is therefore completely accounted for by two adjacent registrations in different RIRs; no single transfer file gives the whole route.

An address block can cross a registry border whole and leave in two equal suitcases. On 20 February 2025, LACNIC's transfer file sent 179.238.0.0–179.239.255.255 from V.TAL - REDE NEUTRA DE TELECOMUNICACOES S.A. to Globenet Cabos Submarinos America Inc. in ARIN. That is a /15, 131,072 IPv4 addresses. ARIN logged the incoming interval too. The old rectangle looked simple enough: one sender, one recipient, one border.

Sixteen months later the lower half took a different exit. LACNIC's file records Globenet in ARIN transferring 179.238.0.0–179.238.255.255 to STARLINK CHILE SPA in LACNIC on 23 June 2026. ARIN records the same lower /16 outbound. Both files specify 65,536 addresses, exactly half the first transfer set. This was 488 calendar days after the /15 went into ARIN. The June row calls the old /15 its original set but names only the lower /16 as its transfer set. Confusing those two fields would make the entire block appear to have returned.

It did not. The upper 179.239.0.0–179.239.255.255 appeared in ARIN's transfer ledger on 14 September as a Globenet-to-Simba Telecom movement from ARIN to APNIC. APNIC independently logged the same /16, with Simba Telecom Pte Ltd as recipient. The two registries timestamp their entries differently on that date; neither timestamp is a record of when packets changed path. What matters for the interval accounting is that the upper /16 contains the other 65,536 addresses. The second exit came 83 calendar days after the first. By September, the two outward rows covered the 2025 /15 without a gap or overlap.

The receiving records give the split a present-tense test. LACNIC's exact RDAP answer for 179.238.0.0/16 identifies STARLINK CHILE SPA and marks registration on 23 June 2026. APNIC's exact answer for 179.239.0.0/16 identifies Simba Telecom Pte Ltd, with a registration event on 14 September and a later change on 16 September. Two independent live objects now occupy the old /15's two halves. Querying a broad historical parent and declaring one present holder would erase what the child records say.

APNIC's source label also shows why the files cannot be read in isolation. Its September transfer row names GCSA-20, not Globenet. ARIN's current RDAP entity for GCSA-20 names Globenet Cabos Submarinos America Inc.; ARIN's own September transfer row names Globenet directly. The handle join connects the APNIC receipt to the middle holder. It does not add another transaction. A dataset that shows only APNIC's receipt starts at the second exit, and LACNIC's dataset ends at the first exit. ARIN holds the middle pages.

The block's path is therefore a three-registry fork, not a tidy round trip. All 131,072 addresses moved from LACNIC administration to ARIN in February 2025. Exactly half came back to LACNIC for STARLINK CHILE SPA in June 2026. The other half went on to APNIC for Simba Telecom in September. Both current exact child registrations match those destinations. ARIN's historical role is visible in its inbound and outbound receipts even though those receipts do not describe the current registrants in one place.

That distinction has practical stakes for anyone trying to verify an asset, a transfer claim or an address inventory. If a search starts with the old /15 transfer, it finds Globenet and ARIN. If it stops there, it misses both later holders. If it starts at LACNIC's June return, it misses Simba. If it starts at APNIC's September receipt, it sees a source handle rather than the original V.TAL departure. The only reliable reconstruction is to join transfer sets by exact numeric bounds, follow both child intervals and check the receiving RDAP objects.

The official rows do not publish a price or an operating timetable; a signed transaction record and dated routing evidence would establish those details. The registry evidence already settles the narrower question: a /15 was registered through one intermediate RIR, then split exactly in half across two other registries. The former whole block survives in history. Its two current halves live in different books.

RIR originals