Valoo gets RIPE PA /22 and PI /24 in one registration second

RIPE Stamped Two Valoo Blocks at 12:59:16. Only One Can Feed Other Networks.

Why it matters

Two RIPE NCC transfer tables show Suomen Datasafe Oy passing an IPv4 /22 and a separate /24 to Valoo Oy on 3 November. Both exact registry objects were created at 12:59:16 UTC. The /22 is `ALLOCATED PA`; the /24 is `ASSIGNED PI`. Same clock, different authority over the next address.

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

RIPE NCC records two Valoo transfers in one second while classifying the /22 as allocated PA and the /24 as assigned PI.

Summary

RIPE NCC's allocation and assignment transfer originals separately record 185.53.84.0/22 and 193.105.97.0/24 moving from Suomen Datasafe Oy to Valoo Oy on 3 November.
Exact RIPE RDAP records register both at 12:59:16 UTC: the /22 is ALLOCATED PA, the /24 ASSIGNED PI. RIPE's current IPv4 policy gives those statuses different downstream-use rules.

A transfer table can make 1,280 addresses look like one neat parcel. Here the larger 1,024-address /22 sits in RIPE's allocations file; the 256-address /24 sits in its assignments file. Both rows say POLICY, PERMANENT, Finland to Finland, same source and recipient, same date. There is no shared deal number in either public row. The useful join is the registry's own exact objects, not an imagined contract.

Those objects are unusually synchronized. The /22 and /24 each show registration and last change at 2026-11-03T12:59:16Z. Each names Valoo Oy through ORG-AO122-RIPE. Yet the /22 is ALLOCATED PA, with RIPE-NCC-HM-MNT among its registry entities, while the /24 is ASSIGNED PI, with RIPE-NCC-END-MNT. One timestamp did not flatten two classes of number-resource custody into one.

Section 7 of RIPE's current IPv4 policy gives the distinction its teeth. LIRs receive PA space and may sub-allocate and assign it downstream; ASSIGNED PI is for a specific end-user purpose and cannot be used to make further assignments to others. The transfer did not publish any actual downstream assignment from Valoo's /22. A current child inetnum or an assignment agreement would establish one. The two receipts instead show a recipient holding a distributable /22 beside a purpose-bound /24.

Official RIPE records: allocation transfer table; assignment transfer table; exact /22 RDAP; exact /24 RDAP; current IPv4 policy.