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
274Stories
Story
LACNIC Adds ASPA Publishing to MiLACNIC; Uptake Is Still Uncounted
LACNIC Adds ASPA Publishing to MiLACNIC; Uptake Is Still Uncounted 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 Loop Study Moves 59 Cases into Intra-AS Under a Private-Hop Rule
LACNIC’s Dominican Republic measurements leave 41 possible-loop cases unclassified after a second rule shifts 59 from the unknown column into intra-AS. The difference is a choice about how to read a hidden hop, not a count of newly confirmed faults.
Story
LACNIC 46 Registrations More Than Doubled. That Is Not Attendance
The public count moved from 348 to 763–766 in about four weeks. It is a sign of registration momentum before the Mendoza meeting, not a record of who will attend or take part in its policy forum.
Story
The Legacy Host Went Quiet. Its IPv4 Lease Did Not.
A /32 DHCPv4 mask can quiet an old client that cannot use IPv6-Only Preferred. The address it receives, the inbound packets it can still accept and the pool that supplies its lease remain operational questions.
Story
LACNIC’s 47-University Security Metric Leaves Its Denominator Unclear
LACNIC’s September account repeats a striking improvement in the share of Ecuadorian universities rated critically for security. The public record gives the percentages and a cohort description, but not the endpoint counts needed to reproduce the change.
Story
LACNIC Warned About Attendee-Database Emails. That Is Not Yet a Breach Notice.
A sales pitch can prove that somebody was targeted. It cannot, by itself, prove how the sender found the target. LACNIC's warning about emails offering attendee databases is useful precisely because it stops at that boundary. The next useful step is to make the changing evidence…
Story
LACNIC's PDP Draft Asks Which Version Receives Consensus
LACNIC's PDP Draft Asks Which Version Receives Consensus 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…
Story
LACNIC’s XARF Guide Counts Seven Required Fields. The Specification Lists Eight
The missing item is `sender`, the field that separates the complainant from the organization transmitting the report. A validator must name the schema it enforced before “valid” can become operational evidence.
Story
LACNIC's ASN-Only Label Is Not a Test of Network Use
LACNIC's ASN-Only Label Is Not a Test of Network Use 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…
Story
LACNIC’s New Legacy Draft Makes Four Facts Share One Trigger
A legacy block can have current contacts, working reverse DNS and a documented right of use while disappearing from the public routing view. LAC-2026-5 would put those different facts on one path to a Board recovery decision.
Story
LACNIC’s WHOIS Shows the Origin ASNs but Not Their Authorization Boundary
LACNIC’s WHOIS Shows the Origin ASNs but Not Their Authorization Boundary 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…
Story
LACNIC’s New Transfer Draft Is a Policy Map, Not a Checkbox
One sentence in LAC-2026-4 appears to ask whether two registries have compatible rules. Read closely, it asks five different questions—and leaves the most important hand-off between them undocumented.
Story
LACNIC Approved the Security Framework Before Measuring the Baseline. The Next Control Is a Versioned Maturity Receipt
The May board record exposes a useful sequence: authorize the framework, have outside experts measure the current state, and only then choose the destination. That order is not evidence of a security failure. It is a reason to keep approval, implementation, target-setting…
Story
Rapport Counts Outcomes Only After a Requested Test Path Exists
LACNIC’s revised Rapport runner can expand several category and test selectors into a matrix. Yet a requested cell with no matching directory leaves no row in the result: it returns before a test identity is printed or any outcome counter moves.
Story
LACNIC’s Election Upload Test Reads Bytes, Not Excel or PDF
A new compatibility test in LACNIC’s open election system carries two reassuring filenames across a disk boundary. The bytes arrive intact. That is valuable evidence—but it is evidence about transport, not about whether a workbook or a result letter is a valid document, whether…
Story
LACNIC’s Hackathon Repo Sends Agents to an Unpinned Sibling Harness
A September change makes the repository’s agent rules more explicit, yet the rulebook itself still lives behind a 13-byte relative link. The useful control is not another instruction: it is a receipt identifying the external instructions that governed each mutating run.
Story
Rapport’s Forbidden-AKI Test Starts at Barry, Not at the Validator
A conformance test cannot prove that a validator rejected a forbidden certificate field until it proves that the field reached the certificate. A September correction to one LACNIC Rapport fixture makes that dependency unusually visible. The change replaces a scalar value that…
Story
The RIR Draft Counts 1,000 Members, Not 1,000 Votes
The proposed compliance-review threshold uses legal entities, not voting weight. LACNIC’s own election figures show why an auditable denominator must come first.
Story
LACNIC’s Migration Script Reuses a Volume at a Different Path
A persistent Docker volume can survive the container that populated it. LACNIC’s historical migration launcher leaves a narrower question unanswered: does the next application still look where that volume is attached?
Story
FORT’s Provider Cap Checks the Sum Before the Union
FORT’s fixed release checks the combined lengths of two provider lists before removing duplicates. The distinction is visible in code; no affected customer or router withdrawal was observed.