LACNIC: What Is It and What Does It Do?

First published on 16 April 2025, with a recorded update on 28 July 2026. The historical wording is retained below. Dated clarifications and the closing discussion were added on 5 October 2026 to distinguish registry services, policy approval, historical figures and present IPv4 request pathways.

LACNIC (the Latin America and Caribbean Network Information Centre) is the Regional Internet Registry responsible for allocating and managing IP addresses and Autonomous System Numbers across Latin America and the Caribbean. Headquartered in Montevideo, Uruguay, it serves 33 territories and operates as a membership-based non-profit.

LACNIC is one of five Regional Internet Registries (RIRs) worldwide. Each RIR receives blocks of Internet number resources from IANA and distributes them within its own service region:

• • AFRINIC — Africa and parts of the Indian Ocean
  • APNIC — Asia-Pacific
  • ARIN — North America and parts of the Caribbean
  • LACNIC — Latin America and most of the Caribbean
  • RIPE NCC — Europe, the Middle East, and Central Asia

This article explains where LACNIC came from, what it actually does day to day, who its members are, and how its policies get made.

NRS clarification · 5 October 2026. LACNIC’s official English name is Latin American and Caribbean Internet Addresses Registry. The current official introduction identifies 33 territories in its service region. Some Caribbean territories are served by ARIN; check the applicable coverage rather than treating the Caribbean as one registry region.

What Does LACNIC Actually Do?

LACNIC's core function is the stewardship of Internet number resources, but its work extends well beyond handing out addresses.

Resource allocation. LACNIC allocates IPv4 and IPv6 address blocks and Autonomous System Numbers (ASNs) to ISPs, businesses, universities, and governments in its region. Every allocation follows needs-based policies developed by the community.

The WHOIS registry. LACNIC maintains a public WHOIS database recording which organisation holds which IP block. Network operators, security teams, and law enforcement rely on it daily to trace traffic and resolve abuse complaints.

Routing security. LACNIC operates RPKI (Resource Public Key Infrastructure) services that let networks cryptographically verify route announcements, reducing the risk of route hijacking.

DNS infrastructure. Through its +Raíces programme, LACNIC deploys copies of DNS root servers across the region, making the Internet in Latin America and the Caribbean more resilient to outages elsewhere in the world.

Training and community development. LACNIC runs technical workshops, IPv6 deployment training, and policy forums, and supports regional research through initiatives like the FRIDA programme.

NRS clarification · 5 October 2026. WHOIS identifies registered holders and contacts; it does not by itself establish unrestricted ownership or identify the actual user of traffic. RPKI origin validation checks authorisation of a prefix’s originating AS, not the whole AS path. See RFC 6811.

How Are LACNIC's Policies Made?

LACNIC operates on a bottom-up, self-regulation model. The rules governing resource management are not written by LACNIC staff or its board — they are proposed, debated, and approved by the community through the Policy Development Process (PDP).

The PDP is open to anyone, member or not. Proposals are discussed on public mailing lists and at LACNIC's twice-yearly public policy forums, and are adopted by consensus. Objections must be backed by technical reasoning; simple disagreement is not enough to block a change. All adopted policies are published in the LACNIC Policy Manual, the authoritative document governing resource management in the region.

This open model is common to all five RIRs and is a defining feature of how Internet number resources are governed globally.

NRS clarification · 5 October 2026. The Policy Development Process v8, checked on 5 October 2026, includes Board ratification after consensus and last call. The Board can reject ratification and request further analysis. Open policy participation, membership voting and Board elections are different mechanisms with different eligibility rules.

When Was LACNIC Founded?

LACNIC's founding happened in three stages, which is why you'll see different dates cited:

• • August 22, 1999 — The founding agreement was signed in Santiago, Chile, during the second ICANN meeting, by organisations affiliated with ECOM-LAC. Their case was simple: Latin American IP addresses should be managed by a Latin American entity, not by ARIN in North America, which handled the region's allocations at the time.
  • 2001 — LACNIC was formally constituted, with administrative headquarters in Montevideo, Uruguay, and technical infrastructure hosted at the NIC.br facilities in São Paulo, Brazil.
  • October 2002 — ICANN officially recognised LACNIC as a Regional Internet Registry at its Shanghai meeting, and LACNIC began independent operations.

Since starting operations, LACNIC has distributed more than 180 million IPv4 addresses across the region.

NRS clarification · 5 October 2026. The detailed founding chronology and the figure of more than 180 million IPv4 addresses above are retained as the original article’s historical account, not newly verified milestones or a current 2026 resource total. The current official introduction dates LACNIC’s establishment to 2002. Organising, constitution and recognition are distinct milestones.

LACNIC and IPv4 Exhaustion

On June 10, 2014, LACNIC reached its final /10 block of IPv4 addresses and entered its exhaustion phase, triggering much stricter allocation rules such as the slow-start policy for new ISPs. On August 19, 2020, LACNIC announced complete exhaustion of its available IPv4 pool.

Since then, organisations needing IPv4 space have two main options: acquire addresses through policy-compliant transfers (intra-regional since 2016, inter-RIR since 2020), or deploy IPv6. LACNIC has invested heavily in the second path — its training programmes and deployment support have helped make Brazil, Mexico, Peru, and Ecuador some of the strongest IPv6 adopters in the world.

NRS clarification · 5 October 2026. The current exhaustion guidance still provides for recovered or returned space, a waiting list and a separate critical-infrastructure pool. Eligible first-time IPv4 recipients must meet the applicable conditions, including IPv6 requirements. Waiting-list entry guarantees neither an allocation nor a date. IPv6 deployment does not automatically replace every IPv4 connectivity requirement. The country examples above are historical observations, not a verified current ranking.

Related Post:

https://nrs.help/how-to-get-a-lacnic-ip-address/

https://nrs.help/the-impact-of-lacnic-policies-on-ip-address-allocation/

https://nrs.help/how-to-check-ownership-with-the-lacnic-whois-database/

https://nrs.help/the-process-of-requesting-ip-resources-from-lacnic/

Frequent Asked Questions

What does LACNIC stand for?

Latin America and Caribbean Network Information Centre (in Spanish: Registro de Direcciones de Internet para América Latina y Caribe).

Where is LACNIC headquartered?

Montevideo, Uruguay, with technical infrastructure also hosted in São Paulo, Brazil.

How many countries does LACNIC serve?

33 territories across Latin America and the Caribbean. Some Caribbean territories fall under ARIN instead.

How is LACNIC different from ICANN?

ICANN coordinates the global Internet naming and numbering systems at the top level; LACNIC is one of five regional registries that manage number resources within a specific geographic region. IANA (operated under ICANN) allocates large blocks to the RIRs, which distribute them locally.

Has LACNIC run out of IPv4 addresses?

Yes. LACNIC entered its exhaustion phase in June 2014 and announced complete IPv4 exhaustion in August 2020. New IPv4 space is now available only through transfers or waiting lists.

NRS clarification · 5 October 2026. For the current official English name, use Latin American and Caribbean Internet Addresses Registry. For a new resource request, distinguish regional coverage, transfer eligibility and waiting-list conditions; none can be inferred solely from the fact that the general IPv4 pool is exhausted.

Institutional accountability

NRS asks who bears the consequences when an institution fails. Operators must keep serving customers, meet contracts and protect their businesses through a registry crisis. Agreement among institutions does not itself give those operators an adequate voice or an effective way to challenge decisions.

We advocate clear duties, decisions whose reasons can be examined, continuity of service and meaningful holder participation. Reform should let the people who depend on these resources influence the rules and defend their rights. Moving authority between institutions is not enough.

Sources and next steps

Current procedures checked on 5 October 2026: LACNIC introduction, Policy Development Process, IPv4 exhaustion phases, IPv4 waiting list and RFC 6811 on origin validation. The detailed founding chronology and old statistics retain their attribution to the historical article; NRS’s accountability argument is a reform position.

Read about structural risk in the registry model and NRS Shield. If you want NRS to represent you in policy or election matters, consider POA and representation separately, including scope, duration and revocation. Reading, membership or supporting reform does not grant a mandate. A POA does not transfer ownership of IP resources.