LEONIX /24 route preceded RIPE transfer by 50 days

LEONIX’s /24 Was on the Route. RIPE’s Transfer Receipt Came 50 Days Later

Why it matters

RIPE RIS saw `82.215.76.0/24` behind LEONIX’s AS209843 from 14 September. RIPE NCC dated the transfer from Calltech SAS to LEONIX EVENTS SAS to 3 November. The route beat the registry receipt by at least 50 days.

Theo March4 November 2026Reading Time 2 minLast update: 4 November 2026

RIPE RIS saw LEONIX-origin routing for the /24 in September; RIPE NCC registered its transfer from Calltech on 3 November.

Summary

RIPE NCC dates the permanent /24 transfer from Calltech SAS to LEONIX EVENTS SAS to 3 November; RDAP records the new registration at 16:26:19 UTC.
RIPE RIS already showed the exact route from LEONIX’s AS209843 in a 14 September interval and still saw it at 323/323 full-table peers on 4 November.

The RIPE NCC transfer original puts 82.215.76.0/24 on its 3 November 2026 list: Calltech SAS to LEONIX EVENTS SAS, policy transfer, permanent. Its current RDAP card names LEONIX EVENTS SAS and timestamps the new registration at 16:26:19 UTC that day.

The network had already been showing LEONIX’s hand. In the RIPE RIS 2026 routing history, AS209843 is the origin of the exact /24 in a recorded interval beginning 14 September, when 124 full-table peers saw it. From 18 September through 25 October, the route averaged about 326 full-table peers. The ASN’s exact RDAP names it Leonix-Events and identifies LEONIX EVENTS SAS. The documented route thus precedes the transfer by at least 50 calendar days.

At 00:00 UTC on 4 November, after the RDAP registration event, RIPE RIS still found the exact route at all 323 full-table peers with the same origin. The paperwork caught up with a route already present; it did not create that route.

Official records: RIPE transfer original; exact /24 RDAP; AS209843 RDAP; 2026 RIS history; 4 November RIS status.