IRR objects still exist, unfortunately and usefully

IRR objects are route records in Internet Routing Registries that still tell many networks which ASN may originate a prefix. They remain useful because some providers still build filters from IRR data, even when RPKI is in place. You should publish both so you are not dropped by a network that still checks the older path.

What an IRR object is

An IRR holds route or route6 objects that list a prefix and an origin ASN. Registries such as RADB and the RIR IRRs store these records for operators who still filter on them. The object should name the ASN that actually announces the space. Keep the origin ASN aligned with your ROA so RPKI and IRR do not disagree.

Sub-assignments need objects that match what you announce, not a covering block you do not originate. If we announce the prefix, the object names our ASN. If you announce it, the object names yours. That split matches how you handle ROAs, and getting it backwards causes hard-to-spot drops.

Why RPKI alone is not enough

RPKI is the cryptographic check. IRR is still the source some desks use when they build prefix lists. A valid ROA with an empty IRR can look like “not in our list” on those networks. The reverse also happens: IRR looks fine, RPKI is invalid, and the cryptographic drop wins. You do not choose which filter you hit first, so create both and keep them in sync.

WHOIS is not the route object

IP WHOIS or RDAP shows who holds the address space. IRR shows who may route it. An LOA is a separate letter for human review. Updating WHOIS on a lease does not create the route object. Ending a lease should include removing or updating the IRR entry as well. A leftover object after a cancel can leave a stale origin in someone’s filter until someone cleans it up.

When a peer still does not see you

If the session is up and one peer still misses your routes, ask whether they filter on IRR. Show them the published object rather than billing details. Note which registry you used, because RADB and an RIR IRR are different queries. Whenever the ROA or the announcement changes, update orig-as so both stay matched. That habit prevents most Friday filter surprises.