LACNIC: SERRA gets two /24s, ANDRA retains adjacent /23

SERRA Got Half a /22 in Two Slips. ANDRA Kept the Other Half.

Why it matters

LACNIC’s 26 October transfer file has two /24 receipts, not one /23. Current RDAP leaves the adjoining /23 with the source and makes the split exact.

Theo March2 November 2026Reading Time 2 minLast update: 2 November 2026

Two LACNIC /24 transfers put 512 addresses under SERRA CLOUD; the adjoining /23 remains under ANDRA TELECOM.

Summary

Two 26 October LACNIC rows transfer adjacent 131.255.160.0/24 and 131.255.161.0/24 from ANDRA TELECOM to SERRA CLOUD LTDA: 512 addresses in two separate records.
Current RDAP shows those two /24s under SERRA and the adjacent 131.255.162.0/23 under ANDRA, exactly partitioning 131.255.160.0/22 in equal address halves.

A clean 50–50 address split arrived in an untidy number of records. On 26 October 2026, LACNIC’s transfer export lists two rows from ANDRA TELECOM to SERRA CLOUD LTDA. One covers 131.255.160.0/24, the next 131.255.161.0/24. Each row has its own /24 as both original_set and transfer_set; each contains 256 IPv4 addresses. The two rows share the same date and recipient, but the file does not combine them into a /23.

Put the addresses on a number line. .160.0 through .161.255 is the lower 512 addresses of 131.255.160.0/22. The upper 512 addresses are .162.0 through .163.255. Current exact-prefix LACNIC RDAP returns one object for each transferred /24, both naming SERRA CLOUD LTDA as registrant, and one object for the upper 131.255.162.0/23, naming ANDRA TELECOM. Those three objects cover all 1,024 addresses of the mathematical /22 without a gap or overlap. The /22 is an accounting frame here, not an original_set field in the two transfer rows.

The RDAP objects keep their 27 November 2014 registration event, while their last changed entries on 26 October 2026 are 11:23:18, 11:24:18 and 11:25:19 UTC for the two /24s and retained /23 respectively. The clocks show three updates on transfer day; they do not supply a contract. A registry change log and routing history would establish why the lower half remained two /24 objects and how the space was used.

Sources: LACNIC 2026-11-02; 131.255.160.0/24; 131.255.161.0/24; 131.255.162.0/23.