RIPE logs Newtec IPv4 and IPv6 transfers; /29 holder record absent

RIPE Logged Newtec’s IPv4 and IPv6 Transfers. Only One Has a Holder Card You Can Find.

Why it matters

Two same-day transfer receipts carry Newtec’s names across RIPE’s public tables. Ask the database for the precise IPv6 allocation, though, and it hands back the registry’s own giant parent block.

Theo March3 November 2026Reading Time 2 minLast update: 3 November 2026

RIPE lists same-day Newtec IPv4 and IPv6 transfers; the exact IPv6 /29 holder entity was not publicly queryable at this check.

Summary

RIPE NCC's IPv4 and IPv6 transfer files each record a permanent policy transfer on 3 November from Newtec Servizi srl to NEWTEC S.R.L.: 185.241.144.0/22 and 2a0c:a380::/29.
The IPv4 RDAP entry names NEWTEC S.R.L. An IPv6 RDAP query for the precise /29 returns RIPE NCC's 2a00::/11 parent; a Whois exact-match query returned no /29 entry.

The transfer desk issued two receipts. The address book has one. RIPE NCC's 3 November tables put a complete IPv4 /22 and a complete IPv6 /29 on the same journey, from Newtec Servizi srl to NEWTEC S.R.L., Italy to Italy. Both rows say POLICY and PERMANENT. They offer no joint case number or explanation for the two similar names.

The IPv4 side is easy to follow. The /22 holds 1,024 addresses. Its exact RDAP response names ORG-NSDP1-RIPE, NEWTEC S.R.L., and records a registration event at 09:42:11 UTC on 3 November. The allocation's old netname, IT-NEWTECSAS-20180116, remains visible as a label; the registrant field is the useful part of the receipt.

The IPv6 side breaks the trail. Query 2a0c:a380::/29 in RIPE RDAP and the response covers 2a00::/11, registered to RIPE NCC. A RIPE Whois query restricted to an exact inet6num match returned “no entries found.” RIPE's own query guide explains the behaviour: without an exact match, an ordinary address query falls back to the smallest enclosing object. A parent covering millions of allocations is not the recipient's /29 holder card.

The /29 was not an invented entry in a transfer spreadsheet. RIPE's 2 November extended delegated file already lists it as an Italian allocation dated 16 January 2018, alongside the IPv4 /22. That earlier file cannot tell us who held either prefix after the 3 November transfer. The transfer tables do name the recipient; the precise public IPv6 database lookup does not.

RIPE's transfer-statistics definitions say the date is when a transfer was processed. The missing receipt is a dated, public /29 registration or case explanation that joins the IPv6 transfer row to a holder record. Until one appears, a reader can follow the IPv4 handover to its registrant and gets only RIPE NCC's umbrella when following IPv6.