RPKI Auto Objects - Launching July 8, 2026
On July 8, 2026, we’ll be launching a new enhancement to RADb’s data feed: RPKI Auto Objects. As a feature of the IRRd platform that underlies RADb, we’ll be presenting pre-existing RPKI pseudo-source objects, providing you with rapid insights into the validity of network routes.
Including RPKI Auto Objects in RPSL route object queries provides a more complete and security-aware view of routing data by combining traditional IRR information with cryptographically-validated RPKI data. This allows you to see both operator-declared routes and those backed by valid ROAs in a single query, making it easier to identify inconsistencies such as stale IRR entries, missing ROAs, or potentially invalid route origins.
We expect that this will improve routing policy decisions and automation by enabling hybrid filtering approaches, such as preferring RPKI-valid routes while still leveraging IRR data where needed. It also reduces integration complexity by exposing RPKI data in a familiar RPSL format, allowing existing tools and workflows to incorporate validation insights without requiring separate RPKI processing pipelines. |
|
Sample RADb data output with RPKI Auto Objects: |
$ whois -h whoisdemo.radb.net -- 35.25.0.0/16
route: 35.25.0.0/16
descr: Merit Network, Inc.
origin: AS237
mnt-by: MAINT-AS237
changed: ljb@merit.edu 20231009
source: RADB
last-modified: 2025-01-24T15:14:08Z
rpki-ov-state: valid
route: 35.25.0.0/16
descr: RPKI ROA for 35.25.0.0/16 / AS237
remarks: This AS237 route object represents routing data retrieved from the RPKI. This route object is the result of an automated RPKI-to-IRR conversion process performed by IRRd.
max-length: 16
origin: AS237
source: RPKI # Trust Anchor: arin
|
We look forward to your feedback. Please share your experiences and your RADb ideas. |
Coming Soon!
New RADb API authentication:
New RADb Portal login interface:
Be on the lookout for announcements on these upcoming features. |