LACNIC · RIR Watchdog
Story
BTW reporting and context linked to this RIR. For the proposal-by-proposal history, the people involved and their changing positions, start with Policy.
Story
Latest stories
341Stories

Story
LACNIC knows how to write a reason. For LAC-2026-3 it wrote two words.
One proposal carries its author's name, his problem statement and five attributable replies, and then a policy register closes it with a date and no ground — while the same registry's board minutes name the directors, the resolution and even the man who left the room.

Story
LACNIC’s Recovery Clause Failed. Its December Deadline Kept Walking.
A proposed route to reclaim disputed legacy resources failed to win consensus on 11 November. The registry's separate six-month call to holders still points to 16 December. The difference is where this story lives.

Story
DE-CIX Mexico Counts Thirty Networks. The Registry Counts Zero.
DE-CIX Mexico Counts Thirty Networks. The Registry Counts Zero. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…

Story
LACNIC’s 80% ROA gate failed consensus. Two days later, the gate was gone.
A proposal would have made route-origin paperwork a condition for getting more addresses. The public record now shows two decisions, two days apart.

Story
LACNIC Took Conciliation Out of Its Directors' Dispute Route
The registry changed a small clause with a large institutional meaning. A director who quarrels with LACNIC under the new commitment meets a three-arbitrator process in the contract text. The previous agreement first sent the parties to conciliation. The Board also wrote down…

Story
A University’s IPv4 Block Went Eight Ways. LACNIC Kept the Receipts.
The 2026 transfer file shows eight specified pieces of a Mexican university’s `148.224.0.0/16` address space going to seven named recipients. One /18 accounts for three quarters of the visible addresses. The record is precise about the blocks and much less helpful about the…

Story
LACNIC Filed Two /22 Transfers. Their Routes Rose in Lockstep.
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…

Story
LACNIC Has 39 TIM-Labeled Receipts for One /16. The Smallest Pieces Hog the Page.
Twenty-seven /24 transfers dominate the line count inside `186.196.0.0/16`. Four larger entries carry more than half the addresses. A registry ledger needs both denominators.

Story
LACNIC Logged One /22 Transfer. The Routes Changed Hands in Two Acts.
The registry recorded a single 1,024-address transfer to Fiber Box. RIPE's routing snapshots show the upper half moving to the new origin first, while the lower half briefly slipped from most of its observed peers.

Story
A /15 Went to ARIN. Its Halves Ended at LACNIC and APNIC.
V.TAL sent 131,072 IPv4 addresses to Globenet in one piece. Two later receipts and two exact live registrations show where every address went.

Story
LACNIC Has 160 Published ASPAs. A Hundred Give Operators More Than One Provider to Keep Straight.
LACNIC opened the ASPA publishing controls in MiLACNIC. Its own repository now shows what that button has to carry: 160 customer-AS declarations, most with more than one authorized provider.

Story
LACNIC Logged Eleven IPv4 Ranges Twice. Two Names Don’t Join.
The same eleven ranges returned to LACNIC’s transfer ledger after 438 to 2,402 days. Two party chains break on names; one old /22 now answers as four /24s.

Story
EVEO Collected 32,256 IPv4 Addresses. LACNIC Filed Eleven Separate Receipts.
Eleven transfers from ten Brazilian sources put 32,256 addresses under EVEO S.A. The current RDAP records still match all eleven ranges, but the log makes readers assemble the total.

Story
LACNIC Moved 17,408 IPs to One Holder. RIS Sees the Small Block, Not the Big One.
Two October transfers have the same source and recipient. The larger /18 last appeared in RIPE’s routing view in August; the /22 is visible to 320 of 322 peers.

Story
LACNIC Logged a Transfer with No Address. The Blank Is 297 Days Old.
A university-to-DIGY transfer has names, date and no IPv4 range in LACNIC’s public file. The only such row in 1,922 has survived since January.

Story
A /20 Left LACNIC for ARIN. It Came Back 438 Days Later to Someone Else.
The same 4,096 addresses crossed the registry border twice. A current registration names the final holder; two transfer rows explain the round trip.

Story
LACNIC’s Security Demo Stops at Brazil’s Platform Border
At LACNIC 46, ASPA, delegated RPKI and incident reports shared one teaching deck. The member portals did not share one route.

Story
SERRA Got Half a /22 in Two Slips. ANDRA Kept the Other Half.
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.

Story
LACNIC Charges $200 to Apply for an IPv4 List It Keeps Behind a Door
The registry offers a place for sellers, buyers and intermediaries to find one another. Entry has a fee, visibility is restricted, and LACNIC expressly declines to audit the intermediaries it lists.

Story
LACNIC Sent Two Equal TIM Address Batches Through Different RIR Doors
Four June rows say ARIN; five September rows say RIPE NCC. Each batch contains exactly 327,680 IPv4 addresses, and today the June lookups also end at RIPE.
