IRRd3
developers·cli clients

Command-line clients

This server speaks classic IRR whois on TCP port 43 — both IRRd-style ! commands and RIPE-style - flags, in any mix. Anything that works against IRRd works here: bgpq4, pathvector, irrd-client, the stock whois tool, or plain netcat.

whois / netcat

Simple lookup
An aut-num lookup returns the object plus reverse-related route/route6 objects.
whois -h irr.irrd3.net AS2914
Prefix searches
RIPE-style flags: -x exact, -l first-level less specific, -L all less specific, -m first-level more specific, -M all more specific.
whois -h irr.irrd3.net -- '-M 1.1.1.0/24'
whois -h irr.irrd3.net -- '-x 193.0.0.0/21'
Inverse + key-only searches
-i finds objects by any attribute value; -K returns primary keys only; -T restricts object classes; -s limits sources.
whois -h irr.irrd3.net -- '-i mnt-by AS-FOO-MNT'
whois -h irr.irrd3.net -- '-T route -i origin AS13335'
whois -h irr.irrd3.net -- '-K -s RADB 192.58.128.0/24'
Persistent session
Send !! first to keep the connection open between queries — RIPE-style lookups otherwise close after each response.
printf '!!\nAS2914\n-M 1.1.1.0/24\n' | nc irr.irrd3.net 43

bgpq4

Prefix list from an as-set
The bread-and-butter filter-generator query: -A aggregate, -b BIRD/JunOS format, -4/-6 address family, -S source selection.
bgpq4 -h irr.irrd3.net -S RIPE,RADB,ARIN -Ab4 AS13335:AS-CLOUDFLARE
bgpq4 -h irr.irrd3.net -S RIPE -6Ab AS-AMS-IX-PEERS
JSON output
-tj runs a !j query — per-source serial ranges, handy for checking freshness.
bgpq4 -h irr.irrd3.net -tj

pathvector

Point pathvector's IRR queries at this host — it speaks the IRRd wire protocol natively.
irr-server: irr.irrd3.net

IRRD ! command reference

!iAS-SET[,1]members of an as-set (,1 = recursive expansion)
!a4AS-SET / !a6expand as-set to prefix list (v4/v6)
!gAS13335 / !6routes originated by an ASN (v4/v6)
!mclass,pkexact object lookup — !maut-num,AS2914
!r<prefix>[,o|l|L|M]route objects covering prefix (o=origins, l/L=less, M=more specific)
!oMNT-NAMEobjects with mnt-by = MNT-NAME
!sSRC,SRCselect sources for this connection
!j / !Jjournal serial ranges / full JSON source status
!vserver version
!n<name> / !t<sec>client identification / query timeout
!!keepalive — hold the session open
!qquit

NRTM (near real-time mirroring)

Stream journal entries
-g replays serials 3 through N, then live-tails new changes until disconnect. Versions: always 3 (NRTMv3).
whois -h irr.irrd3.net -- '-g RIPE:3:1-LAST'
Check serial ranges
-q sources reports first/last journal serial per source — what a mirror client needs before opening an NRTM stream.
whois -h irr.irrd3.net -- '-q sources'

Exports

Full-registry snapshots for bootstrap/mirror imports — gzipped RPSL dumps, regenerated daily. NRTM covers deltas; these cover the initial load (and disaster recovery).

Download a source snapshot
One gzipped file per enabled source — plain RPSL text, source:-stamped, gzipped.
curl -O https://irrd3.net/export/RIPE.db.gz
curl -O https://irrd3.net/export/IRRD3.db.gz
Manifest
Machine-readable index: per-source file name, URL, size, and generation timestamp.
curl https://irrd3.net/export/index.json

RPKI RTR (routers)

Validated ROA payloads + ASPAs over RTR (RFC 8210 v0/v1/v2) on TCP 3323 — serials bump on every 10-minute VRP refresh; connected clients get Serial Notify pushes.

Point a validator at it
rtrclient / Routinator / stayrtr / rpki-rtr — standard RTR client config.
rtrclient tcp rtr.irrd3.net 3323
# routinator: rtr-listen → add rtr.irrd3.net:3323 as an RTR source
Router RTR config
Point your routers at the cache for live ROV/ASPA on BGP announcements.
# bird2
roa4 table r4 { };
roa6 table r6 { };
protocol rpki {
  roa4 { table r4; };
  roa6 { table r6; };
  remote "rtr.irrd3.net" port 3323;
}

# junos
set routing-options validation group RPKI session rtr.irrd3.net
set routing-options validation group RPKI session rtr.irrd3.net port 3323

PeeringDB cache

A drop-in PeeringDB API mirror lives at https://pdb.irrd3.net — swap your tool's base URL from https://www.peeringdb.com/api and everything works the same, minus their rate limits. Covers org fac net ix campus carrier carrierfac ixfac ixlan ixpfx netfac netixlan poc; resyncs on a schedule plus change probes, and GET/POST /sync forces one.

Lookups
Same query params as the real API — filters, depth, since.
curl 'https://pdb.irrd3.net/api/net?asn=13335'
curl 'https://pdb.irrd3.net/api/netixlan?asn=2914&depth=0'
curl 'https://pdb.irrd3.net/api/fac?name=Equinix%20AM3'
Ops endpoints
Health/readiness for monitoring, metrics for Prometheus.
curl https://pdb.irrd3.net/healthz
curl https://pdb.irrd3.net/readyz
curl https://pdb.irrd3.net/metrics

Notes: auth: hashes are always stripped from output. HTTP equivalents of every query live under /api; the /query page runs them through the same engine.