Skip to main content


Quick summary

Table view of active RPKI ROAS, related to the AS filters you have configured in Setup | AS Filters.

Each table row represents an RPKI ROA, which includes the Prefix, Max Length, and AS. Click on a row to reveal the Data Service and URI for each ROA. Click on any column to sort the data.

Use the table filters to filter RPKI ROAS based on all available fields.

Click on Show Columns to hide unwanted data columns or reveal additional ones (IP Version and Mask Length).

Click on Download CSV to export the data in CSV format.

Click on Share to copy a URL of the current RPKI ROAs view.


We form the real-time view of the RPKI ROAs we collect from the RPKI data service. Note that these are filtered resources according to either the AS filters (originating prefixes) or the Prefix filters. If either the AS of an RPKI ROA is an AS filter or the prefix of the ROA is a Prefix filter we show the corresponding ROA.

RPKI ROAs have the following fields:

  • Prefix in CIDR format, e.g.,
  • Max Length as the maximum prefix length that can be advertised in BGP.
  • AS as the valid origin AS being able to announce the prefix (and its sub-prefixes up to max length).

Hidden fields include:

  • IP Version (4 for IPv4, 6 for IPv6)
  • Mask Length as the CIDR length of the prefix. E.g., has a mask length of 24.

RPKI ROA information can be filtered based on all these fields (incl. the hidden ones). The filtered table can be exported to CSV. It can also be shared in a URL form with other Code BGP Platform users.

Finally, each RPKI ROA row is expandable and exhibits an inner table with all data sources that see the ROA. The inner data source table can be filtered (and CSV-exported) based on the following fields:

  • Data Service (RPKI)
  • URI as the URI of the RPKI ROA e.g., rsync://
  • Endpoint as the endpoint from which we downloaded the URI resource, e.g., http://routinator:9556/jsonext


Main tab



Data Sources