NRTM
RADb Availability via NRTM (Near Real Time Mirroring)
The Routing Assets Database (RADb) is accessible through the IRR Near Real Time Mirroring (NRTM) service. This service enables developers and network operators to obtain near-real-time updates from the RADb, ensuring their local IRR mirrors are kept in sync with the global database.
Why Use NRTM?
The RADb contains a vast amount of routing information crucial for network management and operations. Many applications and processes that interact with routing data require the IRR/RPSL query language and rely on system-generated responses from the IRRd (Internet Routing Registry daemon). To facilitate efficient and consistent data access, it is recommended that developers set up a private WHOIS service that mirrors the RADb using NRTM.
By utilizing a private WHOIS service, developers can:
Reduce the load on public IRR servers.
Maintain consistent, up-to-date local copies of routing data.
Integrate seamlessly with custom applications requiring IRR data.
Note: Syncing between databases can take sometime. Please use RADb’s WHOIS service for up to date RADb information.
Service Characteristics:
Public Availability: The NRTM service is publicly accessible, allowing users to synchronize routing data without restrictions.
Timely Updates: Under normal conditions, committed edits are made available within ten minutes, and often even sooner, ensuring that mirrored data is almost always current.
Reliability: The service is designed to be robust and responsive, minimizing latency between changes made to the RADb and their availability via NRTM.
Recommended Configuration:
To ensure reliable and consistent access, developers are encouraged to:
Configure their systems to use the
nrtm.radb.nethostname.Implement automated processes to regularly synchronize their local mirrors using this NRTM endpoint.
Monitor their NRTM connections to detect and resolve any connectivity or synchronization issues promptly.
Partial mirrors
For most of the mirrored databases we just mirror everything but there are cases where we only mirror a subset of objects from a given database.
If an IRR is not listed below, then we mirror all their objects.
For the IRRs listed below, these are the objects we mirror for them.
AFRINIC
as-set
aut-num
filter-set
inet-rtr
mntner
peering-set
route6
route
route-set
rtr-set
RIPE
as-set
aut-num
inet-rtr
mntner
peering-set
route6
route
route-set
rtr-set
RIPE-NONAUTH
as-set
aut-num
inet-rtr
mntner
peering-set
route6
route
route-set
rtr-set
JPIRR
as-set
aut-num
filter-set
inet-rtr
mntner
peering-set
route6
route
route-set
rtr-set
CANARIE
as-set
aut-num
filter-set
inet-rtr
mntner
peering-set
route6
route
route-set
rtr-set
TC
as-set
aut-num
filter-set
inet-rtr
mntner
peering-set
route6
route
route-set
rtr-set
APNIC
as-set
aut-num
filter-set
inet-rtr
mntner
peering-set
route6
route
route-set
rtr-set