RPKI validity of an ASN's registry route objects
The ASN's RIPE Database registry route / route6 objects (inverse origin), each annotated with its RPKI Route Origin Validation verdict (valid / invalid / unknown), plus a summary. NOTE: the RIPE Database 'roa-check' search parameter is a no-op over the JSON REST API (verified live - it adds no annotation to the returned objects), so the verdict is computed per route from RPKI validation (prefix + origin). Complements the single-prefix /prefix/{cidr}/rpki with the AS-wide registry view. Upstream registry: 'global' (all RIRs via GRS, default) | ripe | ripe-nonauth | <rir>-grs.
Path parameters
Origin ASN.
Origin ASN.
Query parameters
Upstream registry: 'global' (all RIRs via GRS, default) | ripe | ripe-nonauth | <rir>-grs.
Upstream registry: 'global' (all RIRs via GRS, default) | ripe | ripe-nonauth | <rir>-grs.
Max distinct route prefixes validated.
Max distinct route prefixes validated.
Response
Successful Response
Example response
{
"_meta": {
"product": "Sugra NetAtlas",
"atlas_built_at": "2026-08-21T04:00:00Z",
"privacy_signal_version": "2026.06",
"confidence": "high",
"accuracy": "public",
"response_time": "2026-08-22T10:00:00Z"
}
}