BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

LACNIC · RIR Watchdog

LACNIC

Start with Policy for a plain-language record of what changed, who argued for what, how the decision evolved, and where the evidence has gaps. Story adds BTW reporting and context.

Freshness: Stale · Last refresh:
267Stories
95Policies
50People with verified identities
85Source accounts awaiting identity resolution
49Participated in 2+ policies
22Participated in 5+ policies
47.3%Top-five discussion share
1Median effective participants
6People covering 50%

Participation concentration

Who actually shaped this RIR?

Discussion statistics are still being updated. Figures shown reflect the records processed so far.

Open a linked profile to follow that person or organisation across policies, messages and changing positions. Every figure remains tied to the stated source coverage.

Recurring people and organisations
  1. Jordi Palet Martinez38 Policies participated · 76 Discussion messages
  2. RICARDO PATARA26 Policies participated · 67 Discussion messages
  3. Gianina Pensky24 Policies participated · 101 Discussion messages
  4. Juan Alejo Peirano24 Policies participated · 83 Discussion messages
  5. Nicolas Antoniello24 Policies participated · 53 Discussion messages
  6. Unknown20 Policies participated · 44 Discussion messages
  7. Paola Perez18 Policies participated · 40 Discussion messages
  8. Carlos Plasencia18 Policies participated · 35 Discussion messages
  9. Alex Ojeda12 Policies participated · 20 Discussion messages
  10. Sergio Rojas. . .12 Policies participated · 18 Discussion messages

Policy records

Start with Policy
  1. LAC-2026-5

    Recuperación de Recursos Legados no Justificados

    Under discussion · Official status: Under discussion
    Introduced: Sep 16, 2026 · Latest activity: Sep 16, 2026

    Source coverage is incomplete.

  2. LAC-2026-4

    Justification of Need for Inter-RIR Transfers

    Under discussion · Official status: Under discussion
    Introduced: Sep 15, 2026 · Latest activity: Sep 15, 2026

    Source coverage is incomplete.

  3. LAC-2023-4

    Legacy Resources Management

    Rejected · Official status: Did not reach consensus
    Introduced: Jun 30, 2026 · Latest activity: Aug 29, 2026
    8Policy versions
    1Total participants
  4. LAC-2026-3

    Require Valid ROA Coverage for Requesting Additional Resources

    Under discussion · Official status: Under discussion
    Introduced: Aug 12, 2026 · Latest activity: Aug 12, 2026
    2Policy versions
    1Discussion messages
    2Total participants
    1Effective participants
    100%Top-five discussion share
  5. LAC-2025-2

    Definition of ‘Organization’

    Rejected · Official status: Did not reach consensus
    Introduced: Apr 30, 2026 · Latest activity: Jul 4, 2026
    2Policy versions

Latest stories

Open Story
Seven blue data capsules enter a validator while one amber relay capsule connects the intake to two anonymous organizations.

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.

Sep 24, 2026
Five address-resource tiles connect through an unlabeled ASN ring beside a frosted pane showing only part of a route path.

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…

Sep 24, 2026
Four distinct evidence channels—a dossier, an intermittent route signal, a reverse-DNS tree and a contact ledger—converge on one copper decision mechanism.

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.

Sep 20, 2026
A glass projection plane shows two origin nodes above four underlying authorization paths, while one observed route reaches only one node.

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…

Sep 19, 2026