Summary

  • RIPE NCC's 1–2 October 2026 transfer originals list 120 IPv4 rows from Invitech ICT Services Kft. and 114 from DIGI Tavkozlesi es Szolgaltato Kft. to 2Connect Telecommunications Infrastructure & Network Services Ltd. The 234 transferred IPv4 ranges do not overlap and hold 941,312 addresses. Three IPv6 /29 allocations and six ASNs accompany them in separate RIPE files.
  • RIPE RIS saw 85.66.0.0/15 originate from AS20845 and 212.108.192.0/18 from AS12301 at 30 September, 3 October and 3 November 08:00 UTC snapshots. The first ASN is among the six transferred to 2Connect and its current RDAP names 2Connect; current RDAP for AS12301 names One Hungary Ltd.

The IPv4 allocation transfer file looks like a paper avalanche. On 1 October 2026, 120 rows name Invitech ICT Services Kft. as source and 2Connect as recipient. On 2 October, 114 rows name DIGI Tavkozlesi es Szolgaltato Kft. as source and the same recipient. Every row is MERGER_OR_ACQUISITION and PERMANENT. RIPE NCC's field guide defines the date as the day it processed a transfer. The calendar measures registry work, not a simultaneous cable-room cutover.

The address arithmetic has teeth. Invitech's 120 transferred IPv4 ranges contain 308,736 addresses. DIGI's 114 contain 632,576. None of the 234 ranges overlap; together they amount to 941,312 addresses. One DIGI /15, 85.66.0.0/15, holds 524,288 of them—more than half the entire IPv4 total. Yet a count of rows alone would give the smaller Invitech side the larger share of the story. The two measures describe different burdens: resource volume and the number of distinct registry entries.

The other resource classes sit in different drawers. RIPE's IPv6 allocation file lists one /29 from Invitech and two /29s from DIGI on the same respective dates. Its ASN assignment file lists three ASNs from each source. That makes 243 rows across the three files, not 243 separate transactions. The ASN list includes AS20845 from DIGI. It does not include AS12301.

Now put two large IPv4 rows beside the route collectors. The DIGI /15 became a 2Connect registry object: exact /15 RDAP names 2Connect. RIPE RIS shows its BGP origin as AS20845 at 30 September, 3 October and 3 November, each at 08:00 UTC. Current ASN RDAP names 2Connect too. Here the address holder, the transferred ASN and the observed route origin line up after processing, while the origin number itself never changes in those snapshots.

The Invitech example draws a different map. RIPE lists 212.108.192.0/18 among the 1 October transfers and its exact RDAP now names 2Connect. RIS sees AS12301 as origin at 30 September, 3 October and 3 November. Current AS12301 RDAP names One Hungary Ltd. The /18's resource holder and its sampled route-origin ASN therefore sit under different current organization names. The three RIS snapshots do not reveal any changes between their sampling times; a continuous route history would answer that narrower question.

This is the point at which a registry receipt stops being a network diagram. RIPE can certify the processed movement of address and ASN records. BGP can show who originated a sampled prefix at a given moment. One large example aligns those identities; the other separates them. Neither pattern should be projected onto the other 232 IPv4 rows without inspecting their routes. The public record's value is that it allows the two clocks to be compared instead of assumed to strike together.

RIPE NCC originals: IPv4 transfers, IPv6 transfers, ASN transfers, transfer fields and RIS method.