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
LACNIC’s 80% ROA gate failed consensus. Two days later, the gate was gone.
A proposal would have made route-origin paperwork a condition for getting more addresses. The public record now shows two decisions, two days apart.

Story
LACNIC Took Conciliation Out of Its Directors' Dispute Route
The registry changed a small clause with a large institutional meaning. A director who quarrels with LACNIC under the new commitment meets a three-arbitrator process in the contract text. The previous agreement first sent the parties to conciliation. The Board also wrote down…

Story
A University’s IPv4 Block Went Eight Ways. LACNIC Kept the Receipts.
The 2026 transfer file shows eight specified pieces of a Mexican university’s `148.224.0.0/16` address space going to seven named recipients. One /18 accounts for three quarters of the visible addresses. The record is precise about the blocks and much less helpful about the…

Story
LACNIC Filed Two /22 Transfers. Their Routes Rose in Lockstep.
VIP Network handed two separate IPv4 /22s to LINQ on LACNIC's 27 October transfer ledger. Both exact RDAP cards changed at 11:24:12 UTC. RIPE's routing monitors then saw the same sequence for each block: zero full-table peers at 16:00, 39 at midnight, and all 322 sampled peers a…

Story
LACNIC Logged One /22 Transfer. The Routes Changed Hands in Two Acts.
The registry recorded a single 1,024-address transfer to Fiber Box. RIPE's routing snapshots show the upper half moving to the new origin first, while the lower half briefly slipped from most of its observed peers.

Story
A /15 Went to ARIN. Its Halves Ended at LACNIC and APNIC.
V.TAL sent 131,072 IPv4 addresses to Globenet in one piece. Two later receipts and two exact live registrations show where every address went.

Story
LACNIC Has 160 Published ASPAs. A Hundred Give Operators More Than One Provider to Keep Straight.
LACNIC opened the ASPA publishing controls in MiLACNIC. Its own repository now shows what that button has to carry: 160 customer-AS declarations, most with more than one authorized provider.

Story
LACNIC Logged Eleven IPv4 Ranges Twice. Two Names Don’t Join.
The same eleven ranges returned to LACNIC’s transfer ledger after 438 to 2,402 days. Two party chains break on names; one old /22 now answers as four /24s.

Story
EVEO Collected 32,256 IPv4 Addresses. LACNIC Filed Eleven Separate Receipts.
Eleven transfers from ten Brazilian sources put 32,256 addresses under EVEO S.A. The current RDAP records still match all eleven ranges, but the log makes readers assemble the total.

Story
LACNIC Moved 17,408 IPs to One Holder. RIS Sees the Small Block, Not the Big One.
Two October transfers have the same source and recipient. The larger /18 last appeared in RIPE’s routing view in August; the /22 is visible to 320 of 322 peers.

Story
LACNIC Logged a Transfer with No Address. The Blank Is 297 Days Old.
A university-to-DIGY transfer has names, date and no IPv4 range in LACNIC’s public file. The only such row in 1,922 has survived since January.

Story
A /20 Left LACNIC for ARIN. It Came Back 438 Days Later to Someone Else.
The same 4,096 addresses crossed the registry border twice. A current registration names the final holder; two transfer rows explain the round trip.

Story
LACNIC’s Security Demo Stops at Brazil’s Platform Border
At LACNIC 46, ASPA, delegated RPKI and incident reports shared one teaching deck. The member portals did not share one route.

Story
SERRA Got Half a /22 in Two Slips. ANDRA Kept the Other Half.
LACNIC’s 26 October transfer file has two /24 receipts, not one /23. Current RDAP leaves the adjoining /23 with the source and makes the split exact.

Story
LACNIC Charges $200 to Apply for an IPv4 List It Keeps Behind a Door
The registry offers a place for sellers, buyers and intermediaries to find one another. Entry has a fee, visibility is restricted, and LACNIC expressly declines to audit the intermediaries it lists.

Story
LACNIC Sent Two Equal TIM Address Batches Through Different RIR Doors
Four June rows say ARIN; five September rows say RIPE NCC. Each batch contains exactly 327,680 IPv4 addresses, and today the June lookups also end at RIPE.

Story
LACNIC’s 2017 /19 Has Nine Pieces on Today’s Registry Map
A single 8,192-address transfer has become a nine-piece register. Six 2026 transfers did most of the cutting.

Story
LACNIC Approved IPv4 Sub-Assignments. Every New Deal Resets a Three-Year Clock.
LACNIC Approved IPv4 Sub-Assignments. Every New Deal Resets a Three-Year Clock. 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
Pronto Net's 24-Row Trail: Two Neighbouring /24s Went to Different Holders in Two Days
LACNIC records 11,008 IPv4 addresses moving out under four capitalisations of one source name since 2023. The most revealing split happened across a single /23 in October.

Story
LACNIC's Row Says /21. The Transfer Was One /24.
Three Brazilian recipients took three small pieces of a 2,048-address block in four days. The registry's two columns tell very different stories if you read only one.
