Summary

  • RIPE NCC’s 2 November 2026 transfer file lists AS213354 and AS50935 moving from INTERNATIONAL HOSTING SOLUTIONS LLP (GB) to Iryna Oliinyk (UA), both under POLICY.
  • The two current RDAP objects link their registrant to ORG-IO80-RIPE, named Iryna Oliinyk, yet both still carry International-Hosting-Solutions-AS as their descriptive name. RIPE defines that name and the organisation link as different fields.

A nameplate can outlive the handover it describes. On 2 November, RIPE NCC’s ASN transfer file recorded two autonomous system numbers moving from INTERNATIONAL HOSTING SOLUTIONS LLP to Iryna Oliinyk. The rows are AS213354 and AS50935, each marked POLICY. Both source country-code cells read GB; both recipient cells read UA. These are two resource rows with the same parties and date. The file offers no contract identifier to join them into one commercial deal.

Open the present records and the split becomes sharper. AS213354’s RDAP object and AS50935’s RDAP object each point to registrant organisation ORG-IO80-RIPE, whose displayed name is Iryna Oliinyk. Both objects were changed at exactly 2026-11-02T14:29:11Z. Yet each object’s name field still reads International-Hosting-Solutions-AS. A reader who treats that string as the holder would assign the resources to the source named in the transfer file, even while the current holder link says otherwise.

RIPE’s database field documentation explains why this is possible. as-name is a descriptive name attached to an AS number. The org attribute points to an organisation object, and in a resource object it represents the holder; org has one value in an aut-num object. The two fields answer different questions. One gives the AS a compact label. The other identifies the party linked to the resource. The current record displays both at once, without forcing the label to become a legal-name mirror.

The two numbers have different histories before this shared date. AS50935 was registered on 11 July 2016; AS213354 on 17 April 2020. Their transfer rows converge on 2 November 2026, and their live objects share a last-change timestamp down to the second. That is the useful clock for the administrative handover visible here. The source file’s POLICY category says how RIPE classifies these rows; it does not publish the parties’ agreement or describe the networks’ route announcements. A dated agreement and routing history would answer those separate questions.

This is a small test of how an address book should be read. Autonomous system numbers are stable identifiers for routing domains; their descriptive names can survive a change in the registered party. A search result or dashboard that extracts only International-Hosting-Solutions-AS will tell a plausible but outdated ownership story. The transfer file supplies the event. The org link in the current RDAP objects supplies the present registration. Neither requires the reader to infer anything about Iryna Oliinyk beyond the public resource record.

RIPE published enough to see the tension. The same old firm’s words are still stamped on both AS objects, while the holder link now points elsewhere. The fields are legible when kept in their proper order: number, transfer row, current organisation. The trouble begins when a descriptive label is promoted into an owner’s name.