Summary

  • RIPE NCC’s assignment transfer table records three permanent merger or acquisition transfers from Telecommunication networks Ltd to Telenet Ltd. on 2 November: 109.229.96.0/19, 81.162.32.0/20 and 94.231.128.0/20. Together they contain 16,384 IPv4 addresses. Its ASN transfer table records AS49136 moving between the same parties on the same date.
  • All four exact RDAP objects now point to Telenet’s ORG-TL987-RIPE and show the same last-change instant, 10:23:31 UTC. RIPE RIS saw all three exact prefixes under AS49136 at 323/323 full-table IPv4 peers before that change and 322/322 afterward.

At 10:23:31 UTC, four registry cards acquired the same new organisation reference. A /19, two /20s and their familiar autonomous system moved to Telenet Ltd. in RIPE NCC’s public record. The three address receipts sit in the IPv4 assignment transfer table; AS49136 has its own ASN transfer receipt. Every row says MERGER_OR_ACQUISITION. The public ledger names the parties and the resources, while leaving the corporate paperwork offstage.

The arithmetic is unusually neat. The /19 contains 8,192 addresses; each /20 contains 4,096. No ranges overlap. That makes 16,384 addresses with one accompanying ASN, a complete enough package to test the lazy idea that a registrant change must arrive with a new route origin.

RIPE’s live RDAP objects name Telenet, handle ORG-TL987-RIPE, for each of the four resources. Their descriptive labels still read TELECOM-NETWORKS-NET and TELECOM-NETWORKS-AS. A reader who stops at the label sees the old name. A reader who follows the organisation reference sees the new registrant. The distinction is a registry fact, not a guess about who operated the network equipment.

The public routing snapshots are plainer still. At 00:00 UTC on 2 November, before the recorded update, RIPE RIS saw each exact prefix originating at AS49136 from all 323 full-table IPv4 peers. At 00:00 UTC on 4 November, it saw the same three exact origins from all 322 peers then in the denominator. The peer set lost one member; the observed origin did not change. A dated route trace would settle whether anything changed in the hours between those frames.

RIPE’s merger ledger moved the registrant, its RDAP changed four objects in one second, and the two routing frames kept the network identifier in place. The corporate event and the packet path have different clocks. This time the record lets readers see both without pretending one proves the other.

Official originals: RIPE IPv4 assignment transfers; RIPE ASN transfers; RDAP /19; RDAP first /20; RDAP second /20; RDAP AS49136; RIS /19 before; RIS /19 after; RIS first /20 before; RIS first /20 after; RIS second /20 before; RIS second /20 after.