RIRRd UK 01 · United Kingdom · HYEHOST LLCChange location or node
Connecting to this instance…
Registry overview
Routing registry
A lightweight Internet Routing Registry.
Start with a query
All queriesSource freshness
View sourcesReading source status…
Current counts are loading.
Node activity
HTTP queries per second
Loading measured data…
Response time · p95
Loading measured data…
Request handling
Counters cover requests forwarded to the Rust service since it started. Requests rejected by the reverse proxy are excluded. Successful handler latency excludes rejections, TLS and network delivery. No query-result cache is used.
Objects by source
Current committed countsLoading measured data…
Explore registered routing policy and generate IRR filters. Availability here does not establish full IRRd parity or production qualification.
Find routing data
Registry explorer
Choose what you need. Run a query, then copy its result or command.
Choose a starting point
Equivalent HTTP request
Choose a query to see its command.
Results
Choose an example above, or enter your own query.
No query submitted.
Large responses show a preview of at most 1,000 items or 64 KiB. Downloads retain the complete original response. Expansion has service limits; an error or timeout is not an empty routing policy.
Mirror coverage
Sources & objects
Current counts, update mode and per-source publication details.
| Source | Current objects | IPv4 routes | IPv6 routes | AS-sets | Update mode | Last check |
|---|
Source details
Browse object keys
30 keys per pageFor developers
API & commands
Working examples for IPv4, IPv6, AS-set membership and automation.
GraphQL workbench
Running schema
Use “Inspect schema” to load the current schema.
For network operators
Connect BIRD or FRR
Generate IRR prefix filters, review them and validate your router configuration.
bgpq4 generates configuration text; it does not change a router. Review source choice and compare the candidate with your current policy before applying it.
Read the router integration guideService health
Resource usage
Memory, CPU and database usage for this RIRRd process.
Waiting for a live resource observation.
Resource history
Application RAM · RSS
Loading measured data…
CPU · one core = 100%
Loading measured data…
Understanding these numbers
Application RAM is the process’s current resident memory (RSS). Filesystem cache is counted separately and can include reclaimable pages. A service limit is a ceiling, not RAM in use. Maintenance can raise historical peaks without representing normal query usage.
View service totals, peaks and limits
Current-run charts exclude older runs by default. Choose all recorded runs to inspect the original observations, including maintenance. No measurements are removed or replaced to flatten the graphs.