LACNIC sets 16 December legacy IPv4 deadline and outlines 2027 RPKI tier
Only 29% of LACNIC legacy IPv4 space has responded ahead of the 16 December 2026 deadline. LACNIC also outlined a 2027 paid tier keeping legacy status while unlocking RPKI and IRR.
On 16 November 2026, LACNIC reported that holders representing only 29% of legacy IPv4 space (and 13% of legacy entities) in the region have contacted the registry ahead of its 16 December 2026 call-to-action deadline.
What changed
Under LACNIC's legacy resource outreach, holders of pre-RIR IPv4 blocks must complete ownership and contact verification by 16 December 2026, after which LACNIC notes it may cease providing registration services for unverified records.
To clarify options for verified holders, LACNIC outlined three service tiers:
- Free contact-only maintenance: Holders can keep basic WHOIS/RDAP contact information updated at no charge while retaining legacy status, without RPKI or advanced registry tooling.
- 2027 paid resource-management tier (retains legacy status): Starting in 2027, legacy holders can sign an annual service agreement granting access to MiLACNIC, RPKI ROA creation, IRR route objects, reverse DNS, sub-assignments, and geofeeds, without converting their blocks to non-legacy member allocations.
- Full LACNIC membership: Standard member relationship with all member services and governance participation.
Separately, policy proposal LAC-2026-5 (Recovery of Unjustified Legacy Resources), which proposed reclaiming legacy blocks that failed to justify use, did not reach consensus on 11 November 2026.
Why it matters for BYOIP teams
BYOIP deployments rely on authoritative registry records: cloud providers verify prefix ownership through WHOIS/RDAP and check RPKI ROAs and IRR objects before announcing customer space. If a LACNIC legacy IPv4 block loses registration services after 16 December 2026 or lacks RPKI and IRR access, onboarding or re-homing that prefix onto cloud networks becomes blocked.
At the same time, the planned 2027 resource-management contract gives legacy holders a clear path to publish RPKI ROAs, IRR objects, reverse DNS, and geofeeds in MiLACNIC without surrendering legacy status.
What to check
- Audit any pre-RIR legacy IPv4 blocks in your inventory whose WHOIS/RDAP records fall under LACNIC administration, and verify whether contact justification has already been filed before 16 December 2026.
- If you lease legacy LACNIC space, confirm with the address holder which service tier they intend to maintain so RPKI ROA and IRR updates remain available into 2027.
- Monitor LACNIC announcements for the exact 2027 fee schedule and launch date of the legacy resource-management contract.
Sources
- Legacy Resources: The Role of the Community in LACNIC's Call to Action
LACNIC · published 16 Nov 2026 · checked 17 Nov 2026
- LAC-2026-5: Recovery of Unjustified Legacy Resources
LACNIC · published 11 Nov 2026 · checked 17 Nov 2026