Skip to main content

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

284Stories

A registry operator faces layered access boundaries with separate policy, evidence, security-key and audit-receipt stations before a stable server room.

Story

A Private Registry Still Needs Public Limits

LACNIC is private infrastructure governance with public consequences: legitimacy depends on a bounded mandate, published rules, evidence, review and an operational record that affected networks can understand.

Aug 28, 2026
A sealed legal record remains separate from registry verification materials while live network equipment continues operating.

Story

A Court Order Is Not a Registry Runbook

A court can determine rights and impose duties. It does not thereby describe every safe registry, credential and routing step. LACNIC needs a disciplined bridge from legal command to operational execution.

Aug 28, 2026
Eleven glass observation lenses reveal different fragments of an abstract routing field, each paired with an unlabelled evidence receipt.

Story

LACNIC’s 11 IXP Collectors Need a Vantage-Point Receipt

LACNIC has opened a useful window onto local routing: eleven BGP collector views, public MRT files and charts of prefixes, origin networks and paths. The problem begins only when a window is mistaken for the landscape. The portal does not bind each result to the peer cohort…

Aug 28, 2026
Two separate document sets are reconciled beside live network equipment during an insolvency review.

Story

The Estate Cannot Route Itself

A liquidator can inventory equipment, contracts and claims. That does not make an Internet number delegation an ordinary asset that moves merely because a sale schedule says so. Insolvency creates two records that must meet: the court-supervised estate and LACNIC's…

Aug 27, 2026
A network-resource path passes from an older six-segment timing dial through a visible handoff to a current three-segment dial and controlled recovery point.

Story

LACNIC Cut Its Recovery Window to Three Months in 2015. One Procedure Page Still Says Six

LACNIC has a clean public record of shortening its resource-recovery publication period from six months to three. It also has a current operational page and policy manual that use the shorter clock. The unresolved problem is simpler and more practical: another public procedure…

Aug 27, 2026
Six complete Board-minute documents sit beneath six blank summary cards, connected by a later-approval chain and file-fingerprint marks.

Story

Six Minutes Are Published. LACNIC’s Summary Column Says Nothing

LACNIC’s 2026 Board page presents six meetings, six dates and six links to approved minutes. Beside them sit six empty `Summary of activities` cells. The records exist; the map into the records does not. That difference determines whether a reader can find a decision without…

Aug 27, 2026
Four anonymous groups of geometrically tagged paper inputs pass through a transparent synthesis mechanism toward a bound strategy folio, while deferred material remains in separate trays.

Story

Between Listening and the Map: LACNIC’s Missing Input Trace

LACNIC’s public account names a collective planning process and a route from listening to SWOT and a final strategic map. What the checked documents do not expose is the privacy-safe join that would let a reviewer follow one issue from source class and channel through synthesis…

Aug 27, 2026
An analyst faces three registry clocks beside a separate map of live network routes across Latin America and the Caribbean.

Story

LACNIC’s RDAP Last Changed Event Dates the Registry Record, Not the Network Handover

A timestamp in a registration record can anchor an investigation, but it cannot substitute for the event the investigator actually needs to prove. LACNIC’s live RDAP data makes that boundary unusually visible: a network entity and the entities embedded inside it carry different…

Aug 26, 2026
A hardware access token remains tethered to a transaction folder above a gap leading to an empty receiving tray, with live network fibres behind it.

Story

The Seller’s Last Login: Why a LACNIC Deal Can Close Before Its Addresses Move

A buyer can acquire the shares, the routers and the customer contracts at midnight and still wake up without a completed registry handover. In a LACNIC transaction, the costly interval is the registry gap between legal control of the company and verified control of the number…

Aug 26, 2026
A glass case holding a subnet grid sits between a sealed loan file and a chain of registry and routing checkpoints; one amber gate limits the recovery path.

Story

The Prefix in the Credit File: What a LACNIC Lender Can Actually Recover

An IPv4 block can look valuable on a market screen and still fail a lender’s recovery test. In the LACNIC region, collateral value depends on a chain that joins company authority, applicable secured-transactions law, transfer eligibility, registry recognition and uninterrupted…

Aug 26, 2026
A sealed transaction folder, a processing token and a calendar ledger sit separately beneath a transparent IPv4 registry grid.

Story

Three LACNIC Numbers an IPv4 Accounting Memo Must Not Collapse

An IPv4 transfer can produce a private price, a registry-processing charge and a recurring membership invoice. They may arrive in the same transaction folder, but each number proves something different.

Aug 26, 2026
A finite grid of dark address tiles is linked by five brass verification seals to a glass registry ledger beneath an unlabeled map of Latin America.

Story

LACNIC Turns IPv4 Value Into a Chain of Proof

An IPv4 block may attract a price, but a board cannot rely on that value until authority, eligibility and the registry change can survive diligence.

Aug 26, 2026
An unlabeled network module waits in one transparent cradle beside an empty transfer cradle in a registry operations room.

Story

At LACNIC, the Most Valuable IPv4 Option Is Waiting

At LACNIC, the Most Valuable IPv4 Option Is Waiting 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…

Aug 26, 2026
Two engineers in a small Latin American ISP network room review an IPv6-first design with a limited IPv4 segment.

Story

At LACNIC, a New ISP Must Prove Need Before It Can Pay $8,000 for IPv4

LACNIC’s rules ask a first-time operator to show that customers and equipment already justify an address block. Exhaustion then sends that approved need into a private market. The rule is neutral on paper; the sequence is not neutral between a network starting from zero and one…

Aug 26, 2026
Editorial illustration of a long line of identity-bound application folders passing review and quarantine gates toward a small recovered IPv4 block.

Story

LACNIC’s Last Waitlist Applicant Faces 12 Years for at Most 1,024 Addresses

LACNIC’s IPv4 queue does not preserve a block for every approved applicant. It preserves an identity-bound place in a sequence whose supply, order, final approval and address quality remain unsettled until recovered space is actually released.

Aug 26, 2026
Three sealed evidence plates feed an anonymous classification node, which separates a ranked blank-candidate ledger at a seat cutoff from a future quota-eligibility gate and a transparent review receipt.

Story

LACNIC’s Election Commission Can Assign a Candidate to a Country They Are Not a Citizen Of

In 2025, LACNIC published an Electoral Commission candidate as a citizen of Uruguay and a resident of Brazil, then ruled that his long residence and economic activity meant he would occupy Brazil’s country slot. The official result and current roster continue to list him as…

Aug 25, 2026
Two identical five-stack result plates sit before and after two transparent audit gates, while an empty document slot breaks the line to the official-state plate.

Story

LACNIC's ASO AC Result Became Official Without a Closure Receipt

At 18:00 UTC on 20 August, one public election table crossed a consequential boundary. The names and 144 votes did not change. The page's status did: the provisional result became the official result after two audit windows. What did not appear beside that new status was the…

Aug 23, 2026
A split editorial ledger overlays a Latin America and Caribbean address grid: eight state columns sit on the left, while a separate append-only event ribbon waits across a visible semantic gap on the right.

Story

LACNIC's Anti-Fake-IXP Log Has No Event Column

LACNIC has made a scarce IPv4 reserve unusually visible. Its public file can show who holds an issued interval and how much of the pool remains reserved. What it cannot say in one row is what happened. A log commissioned to cover assignments, recoveries and returns still…

Aug 23, 2026
Three distinct national registration records align toward an empty five-slot brass evidence matrix.

Story

Three National Registers Expose the Gap Behind LACNIC's No-Consensus Result

Brazil calls an individual entrepreneur a natural person doing business in their own name. Argentina opens its simplified tax register to `personas humanas`. Uruguay describes a one-person monotributo business as a natural person registering before economic activity begins.…

Aug 22, 2026
A maintained walnut archive of blue-glass legacy records is reached by an active evidence-inspection rail, while a separate cobalt policy frame remains one component short; five service couplings connect to a preserved state and reversible brass bridge.

Story

LACNIC's Legacy Deadline Is Running Ahead of Its Policy

Prior BTW reporting describes legacy IPv4 holders answering an administrative request while the community rule that would govern the same evidence is still being debated. That sequence does not make the outreach illegitimate. It makes the label on every decision unusually…

Aug 22, 2026