Summary

  • RIPE NCC records 80.43.0.0/18 leaving for APNIC on 3 September 2026 and the adjacent 80.43.64.0/18 plus 80.43.128.0/17 leaving for ARIN on 14 September. The three pieces exactly fill 80.43.0.0/16, or 65,536 IPv4 addresses.
  • APNIC's matching transfer row names CV. Rumahweb Indonesia as the transfer-time recipient but gives the source as ORG-OTIS1-RIPE. RIPE's organisation record resolves that handle to TalkTalk Communications Limited.

There is a pleasingly blunt way to test a registry story: put the intervals next to one another and see whether any addresses escape. In RIPE NCC's inter-RIR outgoing IPv4 record, 80.43.0.0/18 left TalkTalk Communications Limited for APNIC on 3 September 2026. Eleven days later, 80.43.64.0/18 and 80.43.128.0/17 left the same named source for ARIN. The first piece has 16,384 addresses, the second another 16,384, the third 32,768. Together they form the entire 80.43.0.0/16: 65,536 addresses, without an overlap or a gap.

That complete fit is the story. A reader seeing one September transfer might picture a small disposal from a much larger holding. The two later rows turn it into a full partition of one source prefix across two regional registries. RIPE labels each row POLICY and PERMANENT and gives the source country as GB. Its outbound table supplies the destination registry, but no destination organisation name. It is a resource ledger, not a transaction announcement with a buyer, price and sales pitch attached.

The APNIC side fills one of those blanks. Its cumulative transfer file dated 2 November records the exact first interval, 80.43.0.0–80.43.63.255, at 06:41:22 UTC on 3 September. It names CV. Rumahweb Indonesia, country ID, as the recipient at transfer time. For the source, however, APNIC gives ORG-OTIS1-RIPE and country code ZZ. That is a rather unhelpful answer if the reader expects the company name shown by RIPE's outgoing table.

The handle is not a dead end. RIPE's current organisation record spells out TalkTalk Communications Limited. It was registered in April 2004 and last changed in May 2026, before the September transfer. The two transfer files therefore describe the same address interval with different source identifiers: one prints the company name, the other prints the RIPE organisation handle. Following the handle restores the human name. The country codes do different work too: RIPE's GB is attached to its source row; APNIC's ZZ is the value in its own source field. Neither is a measurement of where the packets were routed.

There is one more clock to keep in view. APNIC's current RDAP answer covers exactly the transferred /18 and labels the network CRI-ID, with an Indonesian country field and a registration event at 06:41:57 UTC on 3 September. The 35-second difference from APNIC's transfer timestamp describes two recorded events; the cited records do not give an end-to-end processing sequence. Nor do they supply a name-change chain connecting the transfer-time recipient text to the current network label. Treating those labels as interchangeable would turn a useful audit trail into a made-up corporate history.

The public evidence is narrower and stronger than that. RIPE records the complete three-way exit from one /16. APNIC independently records the first /18 entering its region and names its recipient at that moment. RIPE's organisation directory resolves the handle APNIC chose for the source. The records do not state a sale price, a routing change or the present ARIN-side recipients. Those would need their own original files. What the records do establish is unusually tidy: one continuous block, three exact administrative pieces, two receiving registries and eleven days.