Summary

  • APNIC’s new 2 November row records Sarah K 1 Pty Ltd transferring 103.79.159.0/24 and AS140728 to Leap Telecommunications Pty Ltd in one event.
  • The six earlier Leap-recipient rows in the cumulative file transferred IPv4 only; both new resources now show the same APNIC RDAP registrant handle, ORG-LA59-AP.

The latest APNIC transfer export grew by one line. Its previous 31 October snapshot had 8,203 rows; the 2 November snapshot has 8,204. The added row, timestamped 09:42:04 UTC on 2 November, lists Sarah K 1 Pty Ltd as source and Leap Telecommunications Pty Ltd as recipient. One field carries 103.79.159.0 through 103.79.159.255, exactly one /24 or 256 IPv4 addresses. Another carries AS140728. Both sit in the same RESOURCE_TRANSFER row, with APNIC as source and recipient RIR.

That pairing is the new part of Leap’s recorded history. Search the cumulative file for Leap as recipient and seven rows appear. The first six, dated from November 2024 to September 2025, carry IPv4 ranges alone: three from within APNIC and three from ARIN into APNIC. The seventh is the only Leap-recipient row dated 2026 and the only one of those seven with an ASN. It is not a novelty claim for the registry as a whole; APNIC’s 2026 file contains other address-plus-ASN transfers.

Current exact-prefix RDAP supplies a second clock. The /24 record is named LEAP-AU; the ASN record is LEAP-AS-AP. Both are active, both show registrant handle ORG-LA59-AP and the public display name Leaptel, and both have a registration event at 09:42:45 UTC—41 seconds after the transfer-file timestamp. The two systems therefore describe the same pair at two stages of registry recording. The row gives the legal recipient name; the RDAP records supply a common current registrant handle. Contracts and routing history would establish consideration and operational use.

Sources: APNIC 2026-11-02; APNIC 2026-10-31; 103.79.159.0/24 RDAP; AS140728 RDAP.