LACNIC repository has 160 ASPAs; 100 list multiple providers

LACNIC Has 160 Published ASPAs. A Hundred Give Operators More Than One Provider to Keep Straight.

Why it matters

LACNIC opened the ASPA publishing controls in MiLACNIC. Its own repository now shows what that button has to carry: 160 customer-AS declarations, most with more than one authorized provider.

Theo March3 November 2026Reading Time 2 minLast update: 3 November 2026

A LACNIC RRDP snapshot contains 160 published ASPA entities; 100 list multiple authorized provider ASNs.

Summary

LACNIC's 3 November RRDP snapshot contains 160 published ASPA files for 160 distinct customer ASNs. The snapshot's SHA-256 matches the value in LACNIC's notification, session 66b09eea-03c7-435f-bb29-5bee810bd657, serial 504814.
Reading the provider lists inside those files yields 60 with one authorized provider ASN and 100 with at least two. The largest list has twelve. These are declared authorizations in LACNIC's hosted repository, not a count of current transit circuits.

The interesting number is 100. A registry can add a publishing button once; a network must keep every provider entry current after that. A replacement transit contract, an added backup or a retired upstream is a fresh occasion to check the signed list.

LACNIC's 22 October announcement said members holding an ASN could create and publish ASPA objects in MiLACNIC, including bulk editing. It also said FORT could validate them. The notice supplied no object count. The repository now supplies a dated one. At serial 504814, it holds 160 ASPA publication entries. Each filename's customer ASN matched the customer ASN parsed from its signed content in this review. All 160 CMS signatures checked successfully; the repository snapshot itself matched the hash advertised by LACNIC.

The distribution is more useful than a ceremonial total. Thirty-eight declarations name two providers, 28 name three, 20 name four and fourteen name five or more. One names twelve. No object has an empty provider list. A twelve-entry declaration is not a finding that twelve connections are live. It is twelve published relationships for the holder to reconcile with its own network and contracts.

This is a snapshot of LACNIC's hosted RRDP repository, not a regional adoption percentage. A region-wide denominator would need the delegated repositories and a defined eligible-ASN set. The snapshot also gives no router-policy deployment count. The concrete finding is narrower and stronger: publishing has produced 160 inspectable declarations, and most of them are already lists that will require maintenance.

The member portal made creation easy. The long-running work starts when one of those provider relationships changes and the authorization must follow it.