Summary

  • On 28 October 2026, RIPE NCC recorded four complete IPv4 allocations moving from TELEFONICA TECH UK MANAGED SERVICES LTD to Telefonica Tech UK Limited under its MERGER_OR_ACQUISITION category. The two /21s and two /23s contain 5,120 addresses.
  • Four database objects changed their organisation reference and netname at the identical timestamp, 09:59:10 UTC. Their ranges, GB country and ALLOCATED PA status stayed put. RIPE's scarce-resource rule starts a 24-month restriction on ordinary onward transfer, with a further merger or acquisition exception.

At 09:59:10 UTC on 28 October, four old address records acquired a new name and a new organisation pointer. The second matters more than the typography. A reader skimming RIPE NCC's transfer table sees four MERGER_OR_ACQUISITION rows from TELEFONICA TECH UK MANAGED SERVICES LTD to Telefonica Tech UK Limited. Each original block exactly matches its transferred block. Nothing in the table looks like a spectacular sale. The spectacular part is how cleanly an entire, unevenly aged portfolio was moved through the registry in one instant.

The four ranges are 188.93.176.0/21, 194.110.124.0/23, 194.110.130.0/23 and 46.28.248.0/21. Two /21s hold 2,048 addresses each; two /23s hold 512 each. That makes 5,120 addresses, with no partial prefix in this transfer set. The two largest allocations date back to 2009 and 2010 in their RIPE objects; the /23 pair dates to 2019. A registry has to carry all three vintages without letting a corporate change turn the address book into a guessing game.

Open the version history of the 188.93.176.0/21 object. Revision 7 points to ORG-AL128-RIPE and calls the network UK-ARCTELLIGENT-20090518. Revision 8 points to ORG-TTUL1-RIPE and calls it UK-TELEFONICA1-20090518. The 46.28.248.0/21 history makes the same move from revision 6 to 7. The first 2019 /23 changes at revision 3; the second at revision 4. All four final revisions carry the same last-modified second.

The two organisation objects sharpen the distinction. The old reference names TELEFONICA TECH UK MANAGED SERVICES LTD and has type OTHER. The new one names Telefonica Tech UK Limited and has type LIR. The holder reference, not merely a display label, has changed. The address spans remain exactly the same, as do GB and ALLOCATED PA. The register records a change in who stands behind the allocations without pretending that the bits themselves went anywhere.

RIPE's business-structure procedure asks for documents supporting such a change and distinguishes it from a legal-name-only update. The public transfer table classifies this case but does not publish the documents, contract price or corporate instrument. That gap is specific: the four database revisions tell us exactly what changed in the registry, while the private papers that justified it are not in the public record. Route announcements or customer service changes would need their own evidence.

There is a clock after the second. Under RIPE's resource-transfer policy, scarce resources such as IPv4 cannot ordinarily be transferred for 24 months after receipt, including receipt through an organisational change. A further merger or acquisition is an explicit exception. RIPE's business-structure page measures the restriction from the registry update. The relevant operational question for a future transferee is therefore not only whether the four ranges sit under the new holder today, but what kind of subsequent transaction RIPE would be asked to register before 28 October 2028.

This is what an accurate registry is for. It preserves the continuity of four address ranges while making a responsibility change visible, dated and inspectable. The transfer table supplies the headline; the object histories supply the working proof. If those histories were missing, the same four rows would be little more than a corporate label on a pile of old addresses.