Region
Latin America Caribbean
Latin America Caribbean regional intelligence explains how companies, people, policy moves, network operations, investment signals, data centre demand, telecom execution, and market constraints shape infrastructure delivery in the same geographic market or governance area. The page connects published coverage with evidence, regional actors, operating dependencies, market context, and customer or regulatory exposure that may otherwise sit across separate topic or company pages. Readers can compare who is active, which signals are backed by public evidence, how local execution risk connects to broader internet infrastructure strategy, and what changes may affect customers, partners, regulators, or capital planning. Readers can understand the geography, the relevant infrastructure sectors, the public evidence base, and the practical questions that make the regional page more useful than a short listing of articles.
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
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 12,609-Organisation Electoral Roll Has No Revision Clock
LACNIC has opened a month-long period for members to challenge its 2026 Board electoral roll. The roll is searchable and its totals reconcile, but the number on the page has no visible timestamp or version to tell a member which state they are challenging.
Story
LACNIC’s AI Client Resolves a Model, Then Chats Without a Resolution ID
LACNIC has published a cleaner way for Java applications to reach its PAI AI gateway. The new client says which model answered. What it cannot say, in its public typed contract, is whether that answer came from the exact model-resolution state the application inspected a moment…
Story
LACNIC Signs 150 Reverse-DNS Files. The Batch Has No Manifest.
LACNIC’s public directory gives every reverse-DNS data file its own signature and checksum. What it does not give a whole-directory consumer is one signed statement saying which 150 filenames belong to the same completed publication.
Story
LACNIC’s BGP Case Counts 368 Route Peers. The Vendor Could Not Produce a Definitive Installation List.
LACNIC’s latest routing-security case is unusually rich in network evidence and unusually poor in application evidence. The route, certificate and attack window can be reconstructed in detail; the vendor still cannot say which installations accepted the malicious update. That gap…
Story
LACNIC Budgets a $390,000 Operating Gap. Financial Results Close All but $87,000 on Paper
A budget can show a small loss while concealing three different movements: the recurring cost of running the registry, the accounting result of a portfolio and the cash that actually entered or left the institution. LACNIC’s 2025 accounts show why its 2026 plan needs those…
Story
LACNIC’s Autonomous-Network Ladder Needs a Scenario Ledger, Not a Company Badge
Two operators can both call themselves level three while describing entirely different machines. One may automate fault diagnosis in a radio network; the other may automate service fulfilment but leave every consequential configuration change to a person. The number sounds…
Latin America and Caribbean Institutional
Odebrecht made off-book payments and compliance monitorship a corporate-accountability test
Odebrecht's admitted bribery scheme was not simply a sequence of employees evading an otherwise functioning payment system. The United States resolution described a dedicated organisational capability—the Division of Structured Operations—that helped request, authorise, fund and…