Skip to main content

Routing Information: M7IRR & M7RPKI (Action 4)

Two separate scores measure whether your announced routes are documented.

IRR score (M7IRR)​

Percentage of your announced routes covered by a matching IRR route object. Routes are compared against objects from the major IRR databases (RIR IRRs plus RADB and others).

  • A route announced in BGP with no covering route object counts as missing.
  • A prefix announced even briefly during the month is counted for the whole month; withdrawing it later doesn't remove it from that month's comparison.

RPKI score (M7RPKI)​

Percentage of announced routes covered by a valid ROA, with a heavy penalty for invalids:

score = (fraction valid) − 10 × (fraction invalid)

A single RPKI-invalid announcement hurts far more than an unknown one. Fix invalids first (wrong origin ASN or maxLength on the ROA), then add coverage for unknowns.

"I created ROAs but my score didn't change"​

  • ROA data syncs from the RIRs roughly every 12 hours, and the current month's report regenerates daily, so new coverage typically reflects within about a day.
  • Verify your ROAs independently: rpki-validator.ripe.net or your RIR's portal.
  • Counts may differ slightly from other tools (Cloudflare, FORT monitor) because the Observatory only evaluates prefixes actually announced in BGP, not every ROA you've created.