APNIC members can publish ASPAs in MyAPNIC, with monitoring in DASH

What changed

APNIC deployed support for Autonomous System Provider Authorization (ASPA) objects in MyAPNIC and the APNIC Registry API in July 2026, so APNIC members can publish their upstream provider relationships directly. On 23 September APNIC announced an APNIC Academy webinar for 30 September covering ASPA basics, the difference between origin validation and path validation, available tools, and how APNIC's DASH service can monitor ASPA status.

APNIC notes that the RIPE NCC, ARIN and APNIC have supported ASPA since late 2025 or during 2026, and that all RIRs are expected to support it by the end of 2026.

Why it matters for BYOIP teams

An ASPA is published by the holder of an AS number and lists that AS's authorised upstream providers. Whether you need one depends on your setup:

• If a cloud originates your prefix from its own AS number, your ROA authorises that AS, and path relationships are the provider's concern.
• If you bring your own AS number to a cloud or CDN, your ASN's ASPA should list the providers that carry your announcements.

What to check

• Whether any of your BYOIP prefixes are originated from your own ASN.
• The provider list you would publish, and how you will keep it current when you add or drop a cloud or transit provider.
• DASH or your RIR's dashboard for ASPA status after publishing.