Summary

  • RIPE NCC lists the full 45.80.144.0/22 as a permanent merger transfer on 15 January 2025 and again on 30 October 2026: two moves of the same 1,024 addresses.
  • Versions of ORG-AA2239-RIPE connect Advania Vestfold AS, ADVANIA NORGE 51 AS and Advania Focus AS; the current inetnum/RDAP trail ends with ADVANIA NORGE AS.

The same IPv4 block entered RIPE NCC's transfer ledger twice. In January 2025, 45.80.144.0/22 moved from Advania Vestfold AS to ADVANIA NORGE 51 AS. In October 2026, the same 1,024 addresses moved from Advania Focus AS to ADVANIA NORGE AS. Both rows say MERGER_OR_ACQUISITION and PERMANENT. Read only the two lines and the middle of the story looks like a missing person case: how did a recipient called NORGE 51 become a source called Focus?

The answer sits one archive away from the transfer table. RIPE's organisation object ORG-AA2239-RIPE carried the name Advania Vestfold AS in version 12. Version 13, last modified on 15 January 2025, called the same object ADVANIA NORGE 51 AS. Version 14, last modified on 25 February 2025, called it Advania Focus AS. The identifier did not change with the sign on the door. Its version 17, dated 30 October 2026, still used the Focus name. Two transfer rows and three names are one traceable registry chain, once the organisation versions are joined.

The address object adds the other half. The earlier inetnum version for 45.80.144.0–45.80.147.255 points to ORG-AA2239-RIPE. On 30 October 2026, the next version changes its org field to ORG-SCA1-RIPE. Current RIPE RDAP names ADVANIA NORGE AS as the registrant over those exact bounds. The transferred resource is the whole /22 both times. Counting both rows as newly acquired distinct space would turn 1,024 addresses into a fictitious 2,048; this is a chain of control over one block, not two blocks.

RIPE published the ingredients in two different ledgers. Its cumulative transfer file records the two formal handoffs, including the later Norway-to-Norway country codes. Its database history records the intervening name changes and the organisation handle that survives them. The missing February line in the transfer table is no mystery to solve with speculation: a change of name on an existing organisation object is visible in object history, while that table lists resource transfers. A reader who treats the two instruments as interchangeable will either invent a third transfer or lose the link between the first and second.

The public records establish dates, fields, names and registry identifiers. A corporate agreement would establish the transaction terms; a dated routing or customer record would establish how the block was operated. Neither is needed to identify the registered resource and the succession of names. The registry can make this continuity easier to see by joining transfer rows to historical organisation handles. Without that join, it has handed readers an unusually tidy puzzle and hidden the connecting piece in a different drawer.

Primary RIPE records