LACNIC withdraws proposal that would have required 80% ROA coverage for more space

What changed

LACNIC policy proposal LAC-2026-3, “Require Valid ROA Coverage for Requesting Additional Resources,” did not reach consensus on 4 November 2026 and was withdrawn on 6 November. The official policy system lists the status as Withdrawn.

The proposal would have required any organisation seeking additional IPv4 or IPv6 resources from LACNIC to show that at least 80% of the IPv4 and IPv6 resources LACNIC had already allocated or assigned to it were covered by valid Route Origin Authorizations (ROAs). The requirement would have sat on top of existing utilisation criteria. It would not have applied to new members, to members who were not requesting more space, or to legacy resources not obtained from LACNIC.

Why it matters for BYOIP teams

Had the proposal been adopted, incomplete ROA coverage could have blocked a subsequent allocation even when utilisation criteria were met. That gate is not entering force. ROA coverage remains good operational practice for anyone announcing their own prefixes; it is not, under this withdrawn proposal, a LACNIC eligibility test for more space.

What to check

• Your current ROA coverage in MiLACNIC if you plan further LACNIC requests, even though this proposal is withdrawn.
• Other open LACNIC proposals on the same policy system if you follow the region's PDP.