How to use this tool
IRR Route Object Lookup: interpretation and next steps
IRR Route Object Lookup checks whether the exact route or route6 object exists in the RIPE Database and compares it with the currently observed BGP origin. Use it before asking an upstream to accept a new announcement.
What this check answers
RPKI and IRR solve different problems. RPKI authorizes origin cryptographically; a route object documents routing intent for networks that still build filters from IRR data.
Workflow
- Enter the ASN and exact IPv4 or IPv6 prefix.
- Confirm the exact object, mnt-by, source, and last-modified fields.
- Compare its origin with BGP and then run the consistency audit for wider coverage.
Example and limits
An exact `route6` object binding your IPv6 /48 to your ASN is commonly needed before an upstream enables filtering for the new announcement.
- An object for a less-specific prefix may not satisfy an upstream expecting an exact match.
- Finding an old object does not make its origin or maintainer appropriate for a new route.
Frequently asked questions
Does an IRR object replace a ROA?
No. Configure both when your routing policy and resource model require them.
Why can an object exist but BGP be absent?
IRR records intent; the route may be withdrawn, filtered, or not yet announced.
Does this tool edit RIPE Database?
No. It is read-only.