# Prefix Routing Consistency
This data call compares the given routes (prefix originating from an ASN) between Routing Registries and actual routing behaviour as seen by the RIPE NCC route collectors (RIS (opens new window)).
GET /data/prefix-routing-consistency/data.json?resource=193.0.20.0/24
# Parameters
| Key | Value | Info | Required |
|---|---|---|---|
| resource | prefix | The prefix to query | yes |
# Data Output
| Key | Info |
|---|---|
| in_bgp | "True" if the route has been seen by RIS, "False" otherwise |
| in_whois | "True" if the route exists in whois, "False" otherwise |
| origin | AS number (integer) of the route |
| asn_name | The name of this AS's holder |
| prefix | Prefix (CIDR string) of the route (more or less specific to the input resource) |
| irr_sources | IRR source this route was found in e.g. "RADB", "RIPE", "LEVEL3"... |
| query_starttime/query_endtime | For registration data: query_starttime defines the query time For routing data: holds the start and end time the query covers From version 0.6 on the result is based on a snapshot instead of a time period. For compatibility reasons "query_starttime" and "query_endtime" will be kept in version 0.x but will hold the same value. |
| resource | Defines the resource used for the query |
# Code Examples
# Available versions for this data call:
deprecated - 0.7
Difference to 1.0 and up: the result is based on a time period, which is stated in "query_starttime" and "query_endtime". However, these fields hold exactly the same value.
current - 1.1
Difference to 0.x: "query_starttime" and "query_endtime" is replaced by "query_time"