Region
Latin America and the Caribbean
Latin America and the 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
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.
Story
FORT’s Snapshot Patch Changes the Rebuild, Not the Meaning of a Good Hash
The published 1.6.8 fix constrains snapshot references and moves a download ahead of workspace deletion. Its cache still remembers an attempt result—a distinction that matters when signed routing evidence vanishes from a local view.
Story
Two Minutes Can Become Many in LACNIC’s Permission Cache
A public PAI client can restart the age of a cached permission entry after a malformed authorization reply without obtaining a new permission decision. Its small resilience mechanism exposes a larger question: which clock should govern an application when the authority it…
Story
LACNIC 46 Says Blocking Is Now Reactive. Its Public Agenda Does Not Show the Coding Rule
A regional result is already visible: a forthcoming LACNIC 46 session says reactive blocking now dominates where active blocking had previously been observed. The public agenda does not yet show how 18 jurisdictions, an unknown number of cases and four unlike kinds of target were…
Story
LACNIC's Election Recovery Defaults to ALL. One Email Search Reaches Vote, Nomination and Support Links
Convenience has a constitutional edge when the thing being recovered is not an account but a power. LACNIC’s newly published election code can use one email address to find three kinds of tokenised link. The missing record is not another log of clicks. It is a receipt showing why…
Story
LACNIC Asked for a Technical-Committee Charter. Its First Committee Ran the Registry.
LACNIC’s Board has found a sensible reason to create a technical committee and an equally sensible reason to fear one. Directors need a place to understand technologies that may reshape the registry. They do not need a second operations room. The distinction sounds obvious until…
Story
LACNIC Counts 2.223 Billion BGP Messages. Its Family Table Totals 853 Million Updates
Two sums on LACNIC’s noisy-BGP study close perfectly. A third opens a 1.37-billion-count question. That does not make the research wrong; “messages” and “updates” may describe different stages. It does make the missing bridge between raw RIS files and the published tables the…
Story
LACNIC's Open-Source Election Lookup Puts the Email Address in the Request Path
LACNIC's open-source election system authenticates a participation lookup before returning its answer. Yet the documented interface has already placed the entity identifier in the part of the request most likely to be copied by infrastructure. The distinction is not a disclosed…
Story
LACNIC’s IPv6 Clock Subtracts 210 `/32`s Without Showing Which Fragments Count
IANA’s allocation clock for LACNIC reaches a reassuringly precise answer: 978,428 units of `/32` space remain available. The public rows beneath it supply exactly the 210-unit subtraction that produces that number. Yet most of those fragments are not labelled `available` in…
Story
LACNIC’s Highest Risks Have Two Clocks and No Public Start Point
LACNIC has put unusually sharp time limits around its most serious residual risks. Its public Board record says what must happen immediately, within 90 days and in less than 120 days. What it does not publish is the event from which either clock is counted—a small omission that…
Story
Rapport Tests Cache Survival. Its Missing-Manifest Warning Is Still Commented Out
LACNIC’s young RPKI test suite preserves the right routes when a manifest disappears; the quieter question is whether the person responsible for those routes is demonstrably told why they are now coming from cache.
Story
LACNIC Listed 32 Resources for December Revocation. That Is Not 32 Cases.
A new LACNIC cohort places 32 number-resource records on one 90-day clock. The table is useful precisely because it is public. Its limit is just as important: a row identifies a resource, not the recovery case behind it.
Story
LACNIC’s ASPA Explainer Cites a Moving Percentage Without a Snapshot
LACNIC’s ASPA Explainer Cites a Moving Percentage Without a Snapshot 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.…
Story
LACNIC 46's Attendee List Has Consent. It Still Needs a Retention Clock
LACNIC tells registrants that their names will appear on the event website. That clarity settles the easy argument; the harder one is how a public list shows the scope, duration and outcome of the permission it already has.
Story
LACNIC’s Abuse-Contact Lockout Sits Outside the Policy Manual
LACNIC’s policy manual says when an abuse contact becomes noncompliant. A separate help page says the consequence is blocked access to MiLACNIC. The missing entity is not another reminder email. It is the public record that joins a rule to the administrative control it activates.
Latin America and Caribbean Institutional Trends
RRC24 Timed Out at Startup. Recovery Needs Its Own Load Test
RIPE NCC has traced a routing-data publication interruption to unusually heavy starting work. The useful management question is now what load a recovered service has actually proved it can finish.
Story
A LACNIC Telecom Essay Moves Voice to IP. It Leaves Backup Power Unassigned.
A new LACNIC Blog essay catches the most consequential detail in the retirement of traditional telephony: the call may look unchanged, but its power supply has moved. That observation deserves a more exact public answer about who keeps an IP call alive when the lights go out.
Story
LACNIC's RDAP delegationSigned Records Parent DS Presence, Not DNSSEC Validation
A boolean in a registry response can look like a verdict on the security of a DNS chain. LACNIC's RDAP `delegationSigned` field answers a narrower question: whether the registration view reports DS records in the parent. It does not run a resolver, test the child keys or prove…
Story
LACNIC Deferred Its $2,100 IPv6-Only Fee to 2029. The 2020 Notice Still Ends the Waiver in 2026
The lower 2026 price is not an accounting mistake. It is the result of a unanimous Board decision that shifted the final step of LACNIC’s IPv6-only discount from 2026 to 2029. The documentary problem is quieter: the original notice remains public with the old endpoint, while the…
Story
LACNIC Says to Email the Bulk WHOIS Form. The Same Page Says Email Is Not Accepted
LACNIC’s public instructions give a Bulk WHOIS applicant two doors and no label for the threshold between them. The signed form is to be emailed first, the original is to be posted after approval, yet the same page ends by saying emailed forms are not accepted. The problem is not…