IRRd3

Our private IRR registry — IRRD-protocol compatible, open for public use.

HOSTED SERVICE Routing & BGP · 10 features · PHP 8.4 / CI4.7 · MariaDB · prefork PHP workers · Docker

overview

IRRd3 (irrd3.net) is a registry service we operate — not software we distribute. It serves the IRR whois protocol on port 43 (bgpq4 / Pathvector / irrtoolset compatible), mirrors the public registries over NRTM, publishes over NRTMv3 + NRTMv4, and accepts authenticated authoritative submissions over HTTPS.

It's private infrastructure, open for anyone to use: queries, looking glass, NRTM feeds and the RPKI RTR endpoint are public; writes need a mntner password or a PeeringDB account.

features

  • ▸Whois on :43 — full IRRD ! + RIPE - query semantics, shared TCP + HTTP engine
  • ▸NRTM v3 client & server, NRTM v4 (UNF/JWS) — mirrors RADB, RIPE, AFRINIC and friends with journalled history back to 2016 via snapshot diffs
  • ▸RPKI RTR daemon (RFC 8210 v0+v1) on :3323 — ROAs + VRP deltas for relying parties
  • ▸HTTP API — whois, authenticated submit, incremental events feed, managed sets
  • ▸Web UI — query, browser submit, managed AS-SET designer, prefix-list filters, object/ASN/prefix watches
  • ▸PeeringDB OAuth — affiliated ASNs can submit routes/sets; ROA validity acts as covering proof
  • ▸Verified registry — the IRRD3 source certifies objects via trusted + local mntners
  • ▸Set tools — managed-set definitions stay private until you publish the generated RPSL yourself
  • ▸Webhooks — HMAC-signed, SSRF-guarded delivery for set watches and object watches
  • ▸Lean by design — prefork PHP workers, prefix-range index, ~5k objects/sec bulk import

stack

PHP 8.4 / CI4.7 MariaDB prefork PHP workers Docker systemd