Internet Routing Registry (IRR) Explorer
Lookup IP Routes, ASNs & Routing Registry Data
Look up IP blocks, ASNs, and routing records across IRR databases to compare registered route objects with live BGP announcements. Quickly identify mismatches, review RIR and RADB data, and access the correct contacts to request cleanup of outdated or incorrect routing records.
The prefix table displays all network prefixes associated with your query. In certain cases, two separate tables may appear: the first contains prefixes directly overlapping the queried resource, while the second expands the view to include all overlaps associated with the least-specific prefix identified in the initial results.
The table is organized into several columns:
Prefix: Displays the network prefix identified within BGP, RPKI, or IRR data sources.
RIR: Indicates the Regional Internet Registry responsible for allocating or assigning the prefix.
BGP: Lists the originating Autonomous System Number(s) currently observed announcing the prefix within the global Default-Free Zone (DFZ).
RPKI: Shows the ASNs authorized through RPKI Route Origin Authorizations (ROAs), including the maximum permitted prefix length defined within each ROA.
IRR Database Columns: Presents originating ASNs extracted from route or route6 objects across various Internet Routing Registry (IRR) databases. For each origin entry:
- A valid indicator signifies the object successfully passes RPKI origin validation.
- An invalid indicator signifies the object fails RPKI validation.
- No indicator means no relevant ROA was identified for validation comparison.
Advice
Provides contextual insights, alerts, and warnings regarding the prefix’s BGP, IRR, and RPKI state. The IRR Explorer attempts to identify potential routing inconsistencies or configuration issues, though certain complex or non-standard network deployments may occasionally trigger false positives.
It is important to note that an origin may still receive an RPKI validation state even when no ROA exists for the exact prefix itself. For example, assume a ROA authorizes 192.0.2.0/22 for AS65540 with a maximum prefix length of /24, while an IRR route object exists for 192.0.2.0/24 originated by the same ASN. In this scenario, two entries would appear: one for the /22 and another for the /24. Although no ROA exists specifically for the /24, the more specific prefix is still covered by the parent /22 ROA. As a result, the IRR origin for the /24 would still be treated as RPKI valid through inherited coverage from the encompassing authorization.