IRR Registry Data, Streamed via RTR.
irr2rtr resolves prefix, ASN, and policy objects from your chosen IRR sources and normalizes them into production-ready RTR streams. Built for network engineers running BIRD 2, FRRouting, and GoRTR.
Live Simulator
LiveNormalized RTR Records (VRPs)
RFC 6811 Structure| Prefix | Max Length | ASN | IP Family |
|---|---|---|---|
| No active RTR session. Click Resolve to parse records. | |||
protocol rpki irr2rtr_rpki {
rtr "irr2rtr_agent" {
remote "rtr.akae.re" port 3232;
refresh 60;
retry 30;
expire 120;
}
import table;
}Automated RTR Staging
Configure your routing policies once. As registries publish upstream database updates, irr2rtr staging layers automatically calculate diffs and push updates down to edge listeners instantly.
Standard RTR Protocols
No custom parsing scripts required on routers. We supply clean, authenticated RTR protocols over TCP, natively supported by hardware platforms and virtual route daemons.
Operator Security
Decouple client admin environments from actual RTR data feeds. Staging caches isolate route servers from credential exposure.
Sync Monitoring
Track target snapshot history, pending sync status, and latest query diagnostics. Keep operations visible and predictable.
Multi-Registry support
Query multiple databases concurrently. Supported IRR sources include RIPE, APNIC, RADB, ARIN, LACNIC, and AFRINIC.