Summary

  • APNIC's 2 November cumulative transfer file has 15 GCSA-20 source rows from August 2025 to October 2026, all ARIN to APNIC, covering 1,511,424 nonoverlapping IPv4 addresses and ten distinct recipient names.
  • The APNIC rows give the source country code as ZZ and a handle in place of a company name. ARIN's current RDAP resolves GCSA-20 to Globenet Cabos Submarinos America Inc.; the public trail takes a cross-registry join to read.

One source can look like a footnote when a transfer file writes its handle instead of its name. In APNIC's cumulative transfer JSON dated 2 November, GCSA-20 appears as the source organisation in 15 rows. The first is dated 26 August 2025, the latest 20 October 2026. Every row runs from ARIN to APNIC and gives the source country code as ZZ. Together, the IPv4 start and end ranges contain 1,511,424 addresses. The ranges do not overlap, so that is also the count of distinct addresses in these records.

The destination side is easier to read. The 15 rows name ten different recipients. Four rows from April, June, August and October 2026 name Bharti Airtel Limited and together cover 86,016 addresses. Other recipients appear in the same cumulative file. The result is not a single large block changing hands once. It is a repeated source handle across dates, destination names and address ranges, all leaving one regional register for another.

The handle has an official home. ARIN's current RDAP entity record for GCSA-20 names Globenet Cabos Submarinos America Inc. and lists a US postal address. The entity was registered on 16 October 2024; its current record shows a last-changed event on 5 October 2026. APNIC's ZZ field and ARIN's present address are different pieces of registry data, not competing measurements of where packets travelled. A reader who stops at the APNIC row sees an identifier. A reader who follows the ARIN handle sees the organisation currently attached to that identifier.

That join is informative but has a date boundary. The APNIC file says its transfer data describe what was accurate when each transfer happened and are not an exhaustive dossier. ARIN's RDAP answer is a current entity view, updated after most of the 15 transfers. It identifies the handle today; it does not preserve a separate dated legal vcard for each event. The public records give no deal price, contract or routing path for these ranges. Those facts would require different original records.

The institutional point is still sharp. APNIC publishes enough machine-readable ranges to count a 1.5 million-address trail, test for overlap and identify destinations. Its source field leaves the human name behind an ARIN handle, while the country field offers ZZ. This is what an inter-RIR transfer really asks of a reader: trace the number through one registry and the source identity through another, then keep the two clocks separate. The public record is substantial. It just does not assemble itself.