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
The LACNIC Board ballot is set for November. Its English call says October.
LACNIC’s election index and dated timelines put the 2026 Board vote on 3–10 November. One English field in the detailed call instead says voting opens a month earlier; the Spanish call gives the November date.
Latin America and Caribbean National Telecom Trends
Mexico’s rural broadband order needs two delivery tests
The Comisión Reguladora de Telecomunicaciones has set out two routes for extending rural access through Telmex and Telnor. A connection point for a local provider and a household fibre offer sit at different places in the network; the public record should measure them separately.
Story
Why the IXP Ranking Counts São Paulo, Rio and Fortaleza Separately
Gael Hernandez’s PeeringDB-based ranking is a useful view of recorded capacity at individual exchange entries. Its three IX.br city rows should not be read as three independent operator systems: the same study counts a much broader, multi-country NL-IX footprint as one entry.
Story
CEDIA’s FIRST Talk Leaves Critical CSIRT Decisions With People
At the LACNIC 46 co-located symposium, a 21 October session will describe DALIA’s AI-assisted triage and correlation while reserving critical decisions and containment for people. The abstract does not say how that boundary is enforced.
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
ARIN grant turns Dominica campus Wi-Fi gaps into a student evidence project
A US$20,000 award backs planned mapping, routing-security, IPv6 and accessibility work at Dominica State College; the project’s findings have not yet been published.
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
Jamaica’s Internet Exchange Turns on the Terms of Participation
A 2026 relaunch brings JAIXP back into view, but its durable value will depend on why independent operators choose to connect, exchange traffic and remain.
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 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.