Routinator’s HTTP service offers a web based user interface on the
path. In addition to displaying detailed statistics from the last validation
run Routinator has performed, as well as HTTP and RTR connection metrics, the
most prominent functionality is the Prefix Check.
By default, you only need to provide an IP address or prefix. When clicking Validate, Routinator will look up from which Autonomous System the closest matching prefix is announced in BGP and perform RPKI validation. Alternatively, you can manually provide an ASN.
The returned RPKI validity state will be Valid, Invalid or NotFound and is based on the current set of Validated ROA Payloads (VRPs) in the cache. Routinator will provide an overview of all VRPs that led to the result, along with the reason for the outcome.
Routinator doesn’t just retrieve the ASN for a specific prefix, but it also fetches related information. In addition to validating the longest matching prefix (or exact match if this is what you selected), details can be provided on less specific and more specific announcements seen in BGP, as well as other resources allocated to the same organisation.
Routinator does not perform the BGP and allocation lookups itself, but relies on the open-source roto-api service, developed and hosted by NLnet Labs at bgp-api.net. The service uses these data sources:
BGP information based on RISWhois data, which is part of the RIPE NCC’s Routing Information Service (RIS). This data set is currently updated every 8 hours.
Resource allocations retrieved from statistics hosted by the five Regional Internet Registries. These are updated daily.
New in version 0.8.3.
Changed in version 0.10.0: The Prefix Check