Summary

  • RIPE NCC's 30 October 2026 transfer tables record Tolvu- og Rafeindapjonusta Sudurlands ehf moving 185.112.204.0/22, 37.205.32.0/21, 2a05:6f00::/29 and AS59396 to Opin Kerfi hf, all labelled MERGER_OR_ACQUISITION.
  • The IPv4 blocks hold 3,072 addresses together. Four current RIPE RDAP objects point to ORG-OKe1-RIPE, Opin Kerfi hf, and were last changed within one second of one another on 30 October.

A single transfer table makes an easy headline and an incomplete inventory. The RIPE NCC IPv4 allocation file has two 30 October rows from Tolvu- og Rafeindapjonusta Sudurlands ehf to Opin Kerfi hf: 185.112.204.0/22 and 37.205.32.0/21. The first contains 1,024 addresses, the second 2,048. Both rows list the whole original block as the transferred block and mark the movement MERGER_OR_ACQUISITION, PERMANENT. That is 3,072 IPv4 addresses in the part of the public record most readers would find first.

The other half of the inventory is filed elsewhere. RIPE's IPv6 allocation table records 2a05:6f00::/29 moving between the same named parties on the same date, also MERGER_OR_ACQUISITION and PERMANENT. The ASN transfer table records AS59396 with those parties and date under MERGER_OR_ACQUISITION. The ASN table has no transfer-status column to borrow the word PERMANENT from the address tables. Four resource identifiers, three files, one visible date.

The live records provide a second test. The RDAP object for 185.112.204.0/22 links to ORG-OKe1-RIPE, displayed as Opin Kerfi hf. So does 37.205.32.0/21, the IPv6 /29, and AS59396. The /21 object says last changed at 09:14:55Z on 30 October; the other three say 09:14:56Z. Those timestamps are an administrative fingerprint of closely timed updates, not a map of packets or customers.

RIPE's transfer-statistics explanation uses the M&A category for a change in an organisation's business structure. The public rows identify the classification and the resources. They do not publish the legal instrument joining them, if one exists. A dated transaction document would answer that question. The four registry objects already answer the practical one: which organisation is registered against each resource now.

This is what a registry ledger is good at when read across its drawers. An IPv4-only view loses the IPv6 allocation and the ASN. An ASN-only view loses 3,072 IPv4 addresses and a /29. The four records do not need to be inflated into an operational merger story. Their simple collective fact is consequential enough: on one date, RIPE's public record attached four different network-resource identifiers to one recipient, and the current database agrees.