How to use this tool
RPKI & BGP Status Lookup: interpretation and next steps
RPKI & BGP Status Lookup validates an ASN-prefix pair against current ROAs and RIPE RIS observations. Use it after creating a ROA, changing maxLength, or troubleshooting a route that is unexpectedly rejected.
What this check answers
A Valid result means the observed origin and prefix length are authorized by at least one matching ROA. Invalid ASN and Invalid Length are operational problems: they can cause filtering even when a BGP session is Established.
Workflow
- Enter the origin ASN and the exact announced prefix.
- Read RPKI status, matching ROAs, maxLength, and RIS visibility.
- Open a Looking Glass sample to compare an observed AS path with your intended propagation.
Example and limits
If 193.0.0.0/21 is originated by AS3333 and the matching ROA is /21 with maxLength /21, the exact route is Valid. A /22 would require a maxLength of at least /22.
- A valid ROA does not prove every network accepts your route.
- More-specific announcements can become Invalid when maxLength is too short.
Frequently asked questions
Does Valid mean my route is reachable everywhere?
No. It confirms origin authorization; propagation, filters, and policy still determine reachability.
What does maxLength do?
It sets the longest, more-specific prefix the ROA authorizes.
Why show BGP and RPKI together?
RPKI answers authorization while BGP shows public route observation; both are needed for diagnosis.