ASPA Is Now Available in MiLACNIC, and FORT Incorporates Its Validation
October 22, 2026
During the LACNIC 46 – LACNOG 2026 event, the regional registry announced support for creating and publishing ASPA objects in MiLACNIC and its validation through FORT validator. These implementations constitute substantial improvements to strengthen Internet routing security across the region.
Routing security played a central role with the presentation of ASPA (Autonomous System Provider Authorization), a new RPKI mechanism. The news was shared by Gerardo Rada, who explained ASPA’s addition to the MiLACNIC portal, and Jorge Cano, who presented the incorporation of the new version of FORT with support for ASPA.
What Does ASPA Bring to the RPKI ecosystem?
Until now, origin validation allowed verifying through ROA objects if an autonomous system number (ASN) was authorized to originate an IP prefix. ASPA goes one step further. It allows advancing toward path validation of the routes, as Cano, Senior Software Architect in LACNIC, explained in his presentation.
Through ASPA, ASN holders can formally declare who their authorized transit providers are. Other operators can use this information to check if routing relationships are consistent and detect anomalies such as route leaks or route hijacks.
(Free access, no subscription required)
ASPA does not replace ROA but rather complements it to gradually enable path validation.
FORT Adds Support for ASPA
Publishing the information is just one part of the process. The other one includes validating it and providing it to the operators so that they can use it in their routing policies.
FORT, the open-source RPKI validator developed by LACNIC, has added support for ASPA validation for that purpose.