How to use this tool
BGP & IRR Consistency Audit: interpretation and next steps
BGP & IRR Consistency Audit finds prefixes and peer relationships that appear in one public system but not the other. It turns a manual comparison into a prioritized reconciliation list.
What this check answers
BGP-only entries can indicate missing IRR registration; IRR-only entries can be stale policy or intentionally inactive. Neither state is automatically wrong, so review each mismatch against your intended routing policy.
Workflow
- Enter an ASN to audit its prefixes and policy relationships, or a prefix to audit origin records.
- Start with entries where BGP and IRR disagree.
- Verify individual routes with the IRR and RPKI tools before making changes.
Example and limits
A prefix visible in RIS but absent from IRR is a useful prompt to check whether the correct route object was created and published in the required source.
- RIS applies visibility thresholds, so local or low-visibility routes may be absent.
- IRR policy data can describe planned rather than live relationships.
Frequently asked questions
Is every mismatch an error?
No. It is a review queue, not an automatic remediation command.
Which source is authoritative?
Use the relevant RIR database for registration, your router for intent, and BGP observation for propagation.
Can this create objects?
No. It only compares public data.