Overview of RPKI services and features offered by each RIR

This page presents the implementation status for each RIR regarding various RPKI services and features. These services and features fall into three categories:

  • Services/features related to service modes
  • Support for object types
  • Other services/features

Last updated: Dec 2025

Services/features related to service modes

Service/feature AFRINIC APNIC ARIN LACNIC RIPE NCC
Hosted service Yes Yes Yes Yes Yes
Delegated service No Yes Yes Yes Yes
Transition between Hosted and Delegated – Supported as action in RIR portal N/A No No No Yes
Transition between Hosted and Delegated – Supported as manual action by RIR staff (Request needs to be sent to Registration Services team) N/A Yes Yes Yes No
Hosted and Delegated can be run simultaneously, i.e. Is make-before-break supported? N/A Yes No No No
Hybrid service (Publication service for Delegated RPKI) No Yes Yes No Yes

Support for object types

Service/feature AFRINIC APNIC ARIN LACNIC RIPE NCC
Route Origin Authorizations (ROAs)* Yes Yes Yes Yes Yes
RPKI Signed Checklists (RSCs) No Yes No No No
Autonomous System Provider Authorizations (ASPAs) in RIR portal No No No No Yes
Autonomous System Provider Authorizations (ASPAs) in API No No No No Yes
BGPsec No No No No No
Signed Prefix Lists No No No No No
Ghostbuster records No No No No No

* Support both in RIR portal AND in API, when an API is available.

Other services/features

Service/feature AFRINIC APNIC ARIN LACNIC RIPE NCC
API for ROA management No Yes Yes Yes Yes
Support for user AS0 (User can create ROAs with AS0 as origin AS) Yes Yes Yes Yes Yes
RIR issues AS0 ROAs for unallocated space No Yes
(Issued on a separate TA)
No Yes
(Issued on a separate TA)
No
Test environment / Sandbox available (for Members) No Yes
(Best-effort service)
Yes No Yes
Multi-user support Yes Yes Yes Yes Yes
Multi-factor authentication (RIR portal) Yes, mandatory

  • TOTP
  • BPKI certificate
Yes, mandatory

  • TOTP
Yes, mandatory

  • TOTP
  • SMS
  • Security key (FIDO2)
Yes, mandatory for Members in Medium or higher tiers. Optional for the rest.

  • TOTP
  • SMS
  • OTP (Yubi key)
Yes, mandatory

  • TOTP
  • Passkey
BGP route collector suggestions No Yes No Yes Yes
Interface supports alignment between RPKI and IRR data sources No Yes Yes Yes No
(Warning in IRR about validity status compared to ROAs)
Supports creation of ROAs for prefixes sub-allocated by provider No No No Yes No
Warning when creating non-minimal ROAs (As recommended in Section 7 of RFC 9319: The Use of maxLength in the Resource Public Key Infrastructure (RPKI) ) No No No No No
Transactions history No Yes Yes Yes Yes

Last modified on 01/12/2025