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
281Stories
Story
LACNIC’s Legacy Policy Page Leaves Its No-Consensus Timeline Unclear
LACNIC’s index dates a no-consensus state for LAC-2023-4 version 4 to 29 August, lists an assessment window through 8 September and says the version was not discussed. A separate legacy-recovery proposal appeared on 16 September.
Story
LACNIC’s Canary Guide Puts Grafana’s Detection Clock in Focus
LACNIC’s 7 October guide presents canary tokens as a low-cost warning for exposed secrets. Grafana’s own incident timeline shows what that warning timed: an attacker had already reached stolen credentials before a decoy key was tested, and response and log review came on separate…
Story
LACNIC’s Routing Lab Needs an Operational Receipt
Two event surveys record who said they attended LACNIC’s secure-routing lab. A new session moves from manual BGP checks to RPKI automation; neither record shows whether that workflow left the virtual lab and entered operating networks.
Story
LACNIC 46’s Hybrid Mix Includes 192 Remote Registrations
LACNIC’s event dashboard lists 648 in-person and 192 remote registrations out of 840. The split is a useful planning signal for a hybrid meeting, but it says nothing about who will attend or take part in the policy forum.
Story
LACNIC’s second-place IANA reviewer starts first—and the dates do not line up
Celsa Sanchez finished second in LACNIC’s 2026 election for its IANA Numbering Services Review Committee seats. She is due to take office immediately. The top-ranked candidate, Hernan Jose Arcidiacono, waits until 1 January 2027. One ballot has therefore produced two winners on…
Story
A Loop Is a Path Claim. An ASN Is an Inference.
A RIPE Atlas trace to 45.186.15.13 shows two public addresses alternating at every hop from TTL 9 through TTL 30. That is a striking path pattern. It is not yet an incident report, and the address sequence does not by itself identify who is accountable. LACNIC’s new Dominican…
Story
Five root-server letters, six listed instances: what Panama’s count can tell us
A LACNIC country report names five root-server identities in Panama. Operator site records retrieved later sum to six instances. The figures describe different units and dates; a response-time chart adds a third question: which route and instance did each measurement reach?
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…