API
All read endpoints are anonymous. /api/submit requires an API key. Everything else is also reachable over classic whois at irr.irrd3.net:43 — see /cli.
irr.irrd3.net:43 — bgpq4 (-S IRRD3), irrpt, jwhois, whois -h irr.irrd3.net. For mirroring use NRTM -g IRRD3: or the NRTMv4 UNFs; RPKI consumers use the public RTR on rtr.irrd3.net:3323. The authoritative source is IRRD3 — submit objects via /submit, this API, or whois !a/!d/!m.
Queries
/v1/whois?q=<whois-query>text/plain RPSL/result text; 204 when empty/not-found; 400 on bad query. Auth attribute hashes are stripped. Alias: /api/whois.curl 'https://irrd3.net/v1/whois?q=AS2914' # aut-num + related curl 'https://irrd3.net/v1/whois?q=!iAS-AMS-IX,1' # recursive set expansion curl 'https://irrd3.net/v1/whois?q=-M%201.1.1.0/24' # RIPE-style more-specifics
/api/bulk{"queries": ["AS2914", "-M 1.1.1.0/24"]} → {"results": [{"q","type","result"}, …]} where type is success|notfound|error.curl -X POST https://irrd3.net/api/bulk -H 'Content-Type: application/json' \
-d '{"queries":["AS2914","!iAS-AMS-IX"]}'/api/suggest?q=<prefix>{suggestions:[{pk,class,source}]}. Min 2 chars. Used by the web search box.curl 'https://irrd3.net/api/suggest?q=AS-AMS'
Status & metrics
/v1/status/api/status, /api/sources.curl 'https://irrd3.net/v1/status' | jq '.[] | {name, objectCount, serialNewestMirror}'/metricsirrd3_mirror_lag_ops), slow queries./api/events?since_id=N returns rows with id > N in ASC order (incremental polling — the front-page ticker uses this); ?before_id=N pages backwards. Filters: src, op (A|M|D), class, pk (prefix). Response includes latest_id watermark to anchor future polls. Rate-limited 120/min.curl 'https://irrd3.net/api/events?limit=10' | jq '.events[] | {ts,source,op,pk}'
curl 'https://irrd3.net/api/events?since_id=1809000' # new rows only/api/events/<id>before/after object text (previous journal version vs this op — DELs carry the deleted text), kind (create|update|delete), changed_attrs ({added,removed,modified}) and a line-level diff.curl 'https://irrd3.net/api/events/1809001' | jq '.changed_attrs'
Validation & lookup
/api/rov?prefix=<cidr>&asn=<n>{state: valid|invalid|notfound, vrps: [covering ROAs]}. Built from the hourly VRP refresh (~1M VRPs, NTT gin export).curl 'https://irrd3.net/api/rov?prefix=1.1.1.0/24&asn=13335'
/api/roas?asn=<n>[&afi=4|6]{asn, count, truncated, roas: [{afi, prefix, max_len}]}. Reverse of /api/rov: prefix+ASN → state; ASN → its VRPs.curl 'https://irrd3.net/api/roas?asn=13335'
/api/route?prefix=<cidr>{routes: [{class, pk, source, prefix, origin_asn, serial_last}], truncated} (max 1000; truncated:true means the covering set was cut). Answers "who claims this prefix" across all mirrored sources.curl 'https://irrd3.net/api/route?prefix=1.1.1.0/24'
/changes.rssGraphQL
/graphqlsources, source(name), object(class, primaryKey, source), objects(class, source, limit, offset), asn(asn), prefix(prefix), search(q), rov(prefix, asn), setMembers(name, recursive), asSetExpansion(name). Interactive explorer when opened in a browser.curl -X POST https://irrd3.net/graphql -H 'Content-Type: application/json' \
-d '{"query":"{ asn(asn: 2914) { routes4Count memberOf objects { source primaryKey } } }"}'Submissions
/api/submitX-API-Key: <key> (create with irrd:user <email> <pass> --key). Body {"source","password","objects":[{"op":"add|mod|del","text":"route: …"}]} — add creates-or-replaces, mod replaces but requires the object to exist, del deletes (partial text OK). Identical rewrites return "unchanged":true — no journal op, no notify mail. Each object must carry a mnt-by: whose auth verifies password, or (IRRD3 only) qualify via the PDB+ROA path: PeeringDB-affiliated origin ASN + valid ROA for routes, affiliation for aut-nums/AS<n>: sets — affiliations are an OAuth-time snapshot trusted for 30 days (irrd3.pdb_affiliation_ttl_days); past that the PDB path disables and the response gains "affiliations_stale":true until the account signs in with PeeringDB again. All adds/modifies are shape-validated server-side (required attrs per class, prefix/ASN/email formats, pk-name charsets, member-token syntax, count caps on mnt-by:/auth:/notify:) — failures return per-object errors and store nothing. Host-bit-set prefixes (203.0.113.1/24) are rejected — use the network address. A submitted source: line is restamped to the target registry, and changed: is server-stamped with the authorizing maintainer + date on every write. Changes journal immediately (NRTM-servable). Successful route:/route6: writes may carry an advisory "warning" field with the RPKI/ROV state — informational only, never blocks the write. Max 20 objects per request — larger batches get HTTP 413; split them client-side.curl -X POST https://irrd3.net/api/submit \
-H 'X-API-Key: ir3_…' -H 'Content-Type: application/json' \
-d '{"source":"IRRD3","password":"mntpw","objects":[{"op":"add","text":"route: 192.0.2.0/24\norigin: AS64497\ndescr: test\nmnt-by: MNT-EX"}]}'Whois updates — TCP :43 only
Classic IRR mutation channel on irr.irrd3.net:43 — HTTP whois is read-only. Send a bare !a, !d or !m on its own line, then the object text, then a blank line to submit. Queries like !a AS-FOO still read — only the bare command mutates.
The object's source: attribute picks the target registry — it must be authoritative here (IRRD3). Authentication is IRRd-style: include auth: lines carrying the cleartext password for a credential stored on the object's mnt-by: maintainer (BCRYPT-PW / CRYPT-PW / MD5-PW — the server verifies it against the stored hash; submitting the hash itself does not work). Auth lines are stripped before storage; mntner objects store only hashes. Deletes authenticate against the stored object's mnt-by, not submitted text.
Verification policy: IRRD3 accepts objects proven either by maintainer chains or by PeeringDB + RPKI. Chains: covering inetnum/as-block/aut-num objects in the RIR/NIR mirrors (RIPE, APNIC, ARIN, AFRINIC, LACNIC, JPIRR, TC) — open mirrors like RADB/ALTDB never count, so you must already maintain your space in your RIR's IRR. Routes need a covering inetnum and an existing origin aut-num; as-sets must be hierarchical AS<n>:NAME. inetnum/inet6num/as-block objects are rejected — those belong to the RIRs. PDB+ROA (API only): via /api/submit, a route:/route6: is also accepted when your API-key account is PeeringDB-affiliated with the origin ASN and a valid ROA covers prefix+origin; aut-num: and AS<n>:-hierarchical sets need only the affiliation. No passwords required on that path.
All adds/modifies are shape-validated before auth: required attributes per class (descr: on routes/sets/domains, as-name: on aut-nums, address:/e-mail:/nic-hdl: on person/role, a supported auth: scheme on mntners), plus prefix/ASN/email format checks, pk-name charsets, member-token syntax on sets, and count caps (mnt-by: ≤8, mntner auth: ≤8, notify: ≤8 addresses). Host-bit-set prefixes are rejected — submit the network address. Deletes may be partial. The registry restamps source: and owns changed: (authorizing maintainer + date) on every write — don't bother maintaining them yourself. Responses: C = applied + journaled (NRTM-servable immediately), F <reason> = rejected, nothing is written on failure. Successful route writes whose announcement isn't ROV-valid return the advisory as A<n> text before C (e.g. ROV not-found: no ROA covers 203.0.113.0/24 for AS64512…) — same warning the API returns as "warning".
Multi-origin (MOAS): the same prefix announced by different ASNs is normal — each origin is a separate route:/route6: object (prefix+ASN is the key), authorized independently: its own ROA on the PDB path, or covering mntner chains on the password path. Submit them as separate objects in one batch.
Bootstrap: create your maintainer first. Easiest: sign in with PeeringDB and use /mntners — it mints an IRRD3-local mntner: object bound to one of your affiliated ASNs (password bcrypt-hashed, shown to you once as cleartext to keep). Or via whois: !a a mntner: object with a self-chosen password in the auth: line (cleartext — we hash it before storage, e.g. auth: BCRYPT-PW mysecretpassword). Either way the mntner's name then goes in mnt-by: on your objects — it satisfies the attribute requirement even when the PDB+ROA path does the actual authorization. Hierarchy rules apply to the password path — covering as-block/aut-num/inetnum objects must authorize the write. And on /api/submit you can skip passwords entirely: affiliation + a valid ROA is sufficient for routes, aut-nums and AS<n>: sets.
$ nc irr.irrd3.net 43 !a mntner: MNT-EXAMPLE descr: Example maintainer auth: BCRYPT-PW mysecretpassword # cleartext — hashed on storage mnt-by: MNT-EXAMPLE source: IRRD3 changed: you@example.com 20261107 C
Object watches — change webhooks
Signed-in users can register watches on /watches: an ASN (any IRRD3 op referencing it — route origins, aut-num/as-block, AS<n>: set names, members), a prefix (route overlap, either direction), or one exact object (class:pk, e.g. route:203.0.113.0/24AS64512). When a journal op on the authoritative source matches, matching ops are batched and POSTed to your endpoint as JSON:
{"watch":{"kind":"asn","value":"AS64512","label":"…"},
"events":[{"source":"IRRD3","serial":42,"op":"M","class":"route",
"pk":"203.0.113.0/24AS64512","matched":"AS64512",
"object_text":"route: …\norigin: AS64512\n…","text_truncated":false}],
"event_count":1,"truncated":false}
Each event also carries object_text — the object's RPSL text after the op (capped at 32KB; text_truncated flags larger objects) — so receivers can diff or alert without a whois fetch. Deliveries carry X-Irrd3-Timestamp + X-Irrd3-Signature: sha256=<hmac> — HMAC-SHA256 of "<ts>.<raw body>" keyed with your per-watch secret (shown on /watches, click to copy). Ops are A/M/D. Failed deliveries retry with backoff up to ~24h; respond 2xx to acknowledge. The test button queues a test.ping delivery. Up to 50 watches per account; watches only see ops created after the watch itself.
Managed AS-SETs (PeeringDB sign-in)
/api/v1/setsAS<asn>:AS-NAME) — a managed definition stored here, NOT published to any IRR source. Responses include the generated RPSL text to submit to your own registry. POST body: {"name","members":[...],"descr","remarks","webhook_url","policy":{…}}. A members entry starting with # is an annotation — rendered as a remarks: attr at that position, ignored by expansion. policy.member_style = nested|flat|both controls whether the generated object lists authored tokens, the expanded ASNs, or both; policy.member_layout = grouped|lines; policy.member_names adds a remarks: line with the registry name (descr/as-name) above each expanded member — flat styles re-expand on every call, so the output always reflects current registry data. Sign in with PeeringDB, mint a key on /mysets.curl -H 'X-API-Key: ir3_…' https://irrd3.net/api/v1/sets
curl -X POST -H 'X-API-Key: ir3_…' -H 'Content-Type: application/json' \
-d '{"name":"AS13335:AS-CUST","members":["AS-TELIA"],"policy":{"transit":true}}' \
https://irrd3.net/api/v1/sets/api/v1/set/<name>/flat{asns[], count, depth, truncated, skipped{…}, unresolved[], cycles[]}. Public — applies the owner's saved policy when the set is managed here.curl https://irrd3.net/api/v1/set/AS13335:AS-CUST/flat | jq .count
/api/v1/set/<name>/filters?format=&afi=txt (one CIDR/line), json, junos, bird, frr, cisco. &afi=4|6 restricts to one family — bird emits only PF_*_V4/PF_*_V6, json returns {afi,prefixes[]}. Aggregated (sibling-merge) and cached until the underlying registry data changes. Managed sets may set policy.filter_name to control the rendered identifier. Public.curl 'https://irrd3.net/api/v1/set/AS13335:AS-CUST/filters?format=frr'
/api/v1/set/<name>/rpslsource:/changed: is emitted — the registry stamps those on submission. Owner-keyed (X-API-Key).curl -H 'X-API-Key: ir3_…' 'https://irrd3.net/api/v1/set/AS13335:AS-CUST/rpsl'
/api/v1/flatten{"members":["AS13335","AS-FOO"],"policy":{…}}, get the flattened ASN list back. Nothing is stored. For a saved set, pass "expand":true in the POST /api/v1/sets body to get the flat result in the same response.curl -X POST -H 'X-API-Key: ir3_…' -H 'Content-Type: application/json' \
-d '{"members":["AS13335","AS-TELIA"],"policy":{"transit":true}}' \
https://irrd3.net/api/v1/flattenPeeringDB mirror — pdb.irrd3.net
/api/<type>https://pdb.irrd3.net/api instead of https://www.peeringdb.com/api. Types: org fac net ix campus carrier carrierfac ixfac ixlan ixpfx netfac netixlan poc. Same params as upstream: field filters (id, asn, name, net_id, fac_id, ix_id, …), depth, since, fields. No rate limits, no API key needed.curl 'https://pdb.irrd3.net/api/net?asn=13335' curl 'https://pdb.irrd3.net/api/netixlan?ixlan_id=26&depth=0'
/healthz /readyz /metrics /sync/readyz reports last_sync/sync_running/last_error; GET|POST /sync forces an incremental sync; /metrics is Prometheus-format (peeringdb_cache_entries, peeringdb_last_sync, sync duration/failure counters).curl -s https://pdb.irrd3.net/readyz | jq
/api/v1/set/<name>/members{"add":["AS-TELIA"],"remove":["AS1299"],"expand":true?} — returns the updated member list + regenerated RPSL (+ flat result if expand). GET returns just the member list.curl -X POST -H 'X-API-Key: ir3_…' -H 'Content-Type: application/json' \
-d '{"add":["AS6939"],"expand":true}' https://irrd3.net/api/v1/set/AS13335:AS-CUST/membersManaged sets support a webhook_url — https://… gets a JSON POST ({set, count, added[], removed[]}) when the flattened membership changes anywhere in the subtree; mailto:ops@… mails the same diff.
NRTM mirroring
TCP :43 — NRTMv3-g SOURCE:3:FIRST-LAST streams journal entries; -g SOURCE:3:FIRST-LAST + keepalive (!!) live-tails. !j reports journal ranges, !J JSON source status.printf -- '-g RIPE:3:1-LAST\n' | nc irrd3.net 43
/nrtm4/<SOURCE>/update-notification-file.json.jose variant is JWS RS256; verify with verification-key.pem. Streams are listed on the /nrtm4 index.curl 'https://irrd3.net/nrtm4/RIPE/update-notification-file.json'