Summary

  • RIPE NCC records seven complete /22 IPv4 transfers on 27 October 2026 from three named LLCs to Homepage Universe, Inc. The 7,168 addresses are all marked MERGER_OR_ACQUISITION and PERMANENT.
  • The public register gives exact prefixes, parties and processing date. It does not give a transaction identifier or a corporate relationship chart linking the three outgoing names to the one incoming name.

Seven lines, one date, one destination. That is an unusual amount of order for a transfer table. RIPE NCC’s allocated IPv4 transfer file says Homepage Universe, Inc. received seven /22s on 27 October. Two came from CEG-Rootwelt LLC, one from CEG-NQHost, LLC and four from CEGRGO-DigitalVM LLC. The register labels every line MERGER_OR_ACQUISITION. It then goes quiet precisely where a reader would ask what merged with what.

The addresses are not approximate. Each original block equals its transferred block: 185.52.248.0/22 and 185.53.168.0/22 from CEG-Rootwelt; 185.72.244.0/22 from CEG-NQHost; 45.11.0.0/22, 45.88.40.0/22, 5.180.76.0/22 and 5.183.100.0/22 from CEGRGO-DigitalVM. A /22 holds 1,024 IPv4 addresses. Seven hold 7,168, or twenty-eight /24 units. That is the size of the recorded change in registered address custody, not a valuation of a business.

RIPE’s transfer-statistics glossary makes the date a processing date. Its transfer-type field separates policy transfers from changes to an organisation’s business structure, such as a merger or acquisition. Its IPv4 statistics page says it publishes valid transfers and specifies when business structure is the reason. The label is meaningful. The exact corporate event tying these names together would require a dated transaction document or a registry bundle identifier that the public list does not supply.

The grouping matters more than the count alone. Three distinct legal-name strings feed the same receiver on the same day, with a 2–1–4 distribution. Their names share fragments; the public table gives no ownership tree. The table is unusually good at identifying the resources and unusually spare about the business arrangement that moved them.

There is another easy trap in the two US country columns. RIPE defines them as the countries where the source and receiver organisations were legally registered when the transfer was processed. Server location and route origin would require separate records. The same table records all seven changes as permanent. That is a registry-status description. The route a packet took on 26 or 28 October needs routing evidence.

RIPE’s resource-transfer and merger guide explains why the two kinds of record meet here. A change in corporate structure can trigger a change in the registered holder of number resources. The RIR must get the resource holder right, because the holder is the party with authority to maintain registration and request subsequent changes. A corporate filing could reveal a broader deal; the resource register answers a narrower, harder operational question: which legal name now holds each exact block?

The result is a neat ledger with a ragged edge. Seven /22s are traceable one by one; the business event is reduced to a category. A network operator checking authority can use the ledger immediately. A member trying to understand consolidation across address holdings must reconstruct what the ledger will not name. The missing public fact is a dated document that ties the three outgoing entities and Homepage Universe to the same transaction or distinguishes separate transactions. Until that exists, the headline belongs to the register, not to a claimed corporate takeover.