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
Story
LACNIC Ratified the Sub-Assignment Rule. An Operating Log Still Needs Its Own Receipt.
LACNIC records LAC-2025-5 as ratified on 24 March 2026. Its final text calls for a WHOIS link and a public start-and-end movement log for qualifying IPv4 sub-assignments. Those are consequential commitments, but a ratification history is not itself a record of an individual…
Story
LACNIC and the economics of rough consensus
Consensus is not the absence of conflict. In a regional Internet registry, it is the work of turning conflict about scarce, shared infrastructure into rules that operators can recognize as legitimate.
Story
LACNIC and the economics of transition architecture beyond RIRs
A transition test built around functions, records and authority—not around the fantasy that scarce network resources can govern themselves.
Story
LACNIC’s Bogon Guide Has Three Different Data Clocks.
A BGP filter can reject a route without saying why that route was rejected. Treating every rejected route as one security statistic may be convenient for capacity reporting, but it is too coarse to explain what the underlying evidence meant at the moment of the decision.
Story
LACNIC's Board Is Nine Members. Its Public Description Still Says Seven
A public governance page can be right in its detailed account and wrong in the sentence built to travel furthest. LACNIC's current English Board record offers that small but revealing split: its description says the honorary Board has seven directors; the record's body says nine…
Story
LACNIC’s FORT Guide Skips the Signature Published Beside Its Tarball
The guide checks the validator after installation. It never checks the archive before extraction, even though the release already offered a digest, a detached signature and a public keyring.
Story
LACNIC Calls Postman Its Current API. The Website Still Says ROAs Change by Serial Number
LACNIC gives an API operator two public descriptions of the same control surface. Its Registration API page says Postman holds the most current v3 documentation, while the route table beside that instruction describes modifying or removing one ROA by `serialNumber`. Follow the…
Story
LACNIC Published a 98% Outreach Score. The Response Count Is Missing
LACNIC says more than 330 organizations attended its 2025 member gatherings and that 98% of the feedback it received fell in the highest satisfaction levels. Both statements may be accurate. The public post does not disclose the number of responses, so the percentage cannot be…
Story
LACNIC Reported 99.5% Completion. An Earlier 98% Minute Also Recorded 6% Cancelled Actions
LACNIC's Board has approved unusually high strategic-completion figures. The numbers may be sound. What the two checked minutes do not supply is the calculation bridge that would show whether cancelled, replaced or reweighted work remained in the denominator, left it or…
Story
LACNIC’s TAL Page Shows Two URLs and Links to Two Others
LACNIC’s trust-anchor page presents two addresses as TAL downloads. A reader who clicks them reaches distinct, valid TAL files through legacy Innovaportal targets. A reader or script that copies the addresses printed on the page instead receives the same HTML application shell…
Story
LACNIC's Delegation File Declares 49,894 Records. It Contains 48,214
A daily file built for machines fails the counting rule printed in its own specification, while its automatic alias and its dated signature offer two different paths to trust. The discrepancy is not evidence of missing Internet resources. It is a test of whether a registry…
Story
LACNIC’s Revocation List Shows a /23 in 2023 and a Nested /24 in 2026
The same first address appears twice in LACNIC’s public revoked-resources table, first as a 512-address block and three years later as its lower 256-address half. That visual repetition invites the wrong question: was the same resource revoked twice? Six official daily snapshots…
Story
LACNIC's Four-Vendor BGP Claim Needs the Configuration Column
One malformed Prefix-SID attribute reportedly met three different actions as it crossed the Internet: discard, propagation and session reset. LACNIC's new routing-security article makes the divergence visible. To make it reproducible, the comparison now needs to name the release…
Story
One LACNIC Office Has Three Public Calendar States
LACNIC’s contact record describes one Montevideo office, one set of weekday opening hours and one institutional doorway. Change the language, however, and its public holiday calendar changes year. Spanish presents thirteen dates in 2026; English leaves three in 2025; Portuguese…
Story
LACNIC’s 70% Pass Mark Is Not a Candidacy Receipt
LACNIC’s Board-election rules contain a consequential distinction: a person can pass the mandatory competency assessment and still not become a validated candidate. The Electoral Commission receives the score and remote-proctoring incident evidence, but the public process does…
Story
LACNIC and the economics of legitimacy after scandal
A balance-sheet test for how a regional Internet registry could restore trust after a verified governance failure without risking continuity.
Story
LACNIC's FORT Can Validate ASPA. Its Router Feed Defaults to Version 0
LACNIC announced a validator that can carry ASPA data towards routers. The release also keeps that route behind a configuration value whose default is zero. That is not a contradiction or a defect. It is the difference between shipping a capability and establishing that the…
Story
LACNIC and the economics of IANA recognition and franchise risk
IANA recognition is not a commercial franchise, yet it creates a similarly scarce institutional position: one regional registry becomes the globally accepted gateway between an upstream numbering system and a defined community.
Story
LACNIC and the economics of NRO coordination incentives
A regional Internet registry is not a shop that customers can abandon when service disappoints them. Internet number resources must remain unique, and each registry serves a defined region. That makes coordination indispensable. It also removes the most familiar market…
Story
LACNIC and the economics of ICP-2 reform
The rule for recognising an Internet registry is also a rule about who must bear the cost of proving that institutional change is safe. LACNIC makes that trade-off unusually visible: regional legitimacy is built through members and an open policy process, while recognition…