Two LACNIC /22 transfers reach RIPE RIS peers in lockstep

LACNIC Filed Two /22 Transfers. Their Routes Rose in Lockstep.

Why it matters

VIP Network handed two separate IPv4 /22s to LINQ on LACNIC's 27 October transfer ledger. Both exact RDAP cards changed at 11:24:12 UTC. RIPE's routing monitors then saw the same sequence for each block: zero full-table peers at 16:00, 39 at midnight, and all 322 sampled peers a day later.

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

Two independent LACNIC /22 transfers show the same three-stage RIPE RIS peer-visibility sequence.

Summary

LACNIC's cumulative transfer original records two 27 October RESOURCE_TRANSFER rows from VIP Network to LINQ: 131.0.36.0/22 and 138.99.24.0/22, a total of 2,048 addresses.
RIPE RIS reports the same full-table-peer sequence for both exact /22s: 0/322 at 27 October 16:00 UTC, 39/322 at 28 October 00:00, and 322/322 at 29 October 00:00, with AS266539 as origin in the last two snapshots.

The two LACNIC rows are not fragments of one address block. Each is a complete /22, and they sit far apart in IPv4 space. Both rows name the same Brazilian source and recipient; the original and transferred bounds match exactly. LACNIC's exact RDAP cards now name LINQ on both blocks and show the same last-change second, 2026-10-27T11:24:12Z. Their original registration dates remain 2014 and 2015. The ledger supplies two receipts and one visible update clock.

The routing clock has three harder ticks. At 16:00 UTC on 27 October, RIPE RIS's full-table sample reported zero of 322 peers seeing either exact /22. Eight hours later it reported 39 of 322 for each, both originated by AS266539. At 00:00 UTC on 29 October, both were visible at 322 of 322 peers, still with AS266539. LACNIC's ASN record names LINQ as the registrant of AS266539. Two disjoint ranges crossed the same observed thresholds at the same sampling times.

RIPE's Routing Status documentation defines these counts as full-table RIS peer observations at scheduled collection times. The exact change minute between samples is absent. A dated LINQ network change log would identify how the two announcements were coordinated. What the public evidence already shows is a matched registry update followed by matched public routing visibility for two distinct resources.

Official records: LACNIC transfer file; RDAP first /22; RDAP second /22; AS266539 RDAP; RIPE RIS method; first /22 at 27 Oct 16:00; first /22 at 28 Oct 00:00; first /22 at 29 Oct 00:00; second /22 at 27 Oct 16:00; second /22 at 28 Oct 00:00; second /22 at 29 Oct 00:00.