RPKI what-if
Model publishing one ROA before you do it. See today’s origin-validation verdict, the ROAs behind it, and what changes for every origin observed announcing the prefix.
Enter a prefix and origin. The page reads the live RPKI store and the latest daily routing snapshot, then re-runs origin validation with your proposed ROA added. Nothing is published and no router or validator is touched.
current state
reading live data
today
loading
Reading the RPKI store and the latest routing snapshot…
covering ROAs
| prefix | maxLength | origin | TA | state |
|---|---|---|---|---|
| Loading covering ROAs… | ||||
after publishing
hypothetical ROA
proposed
The verdict change will appear here.
observed origins
| origin | observations | today | after | delta |
|---|---|---|---|---|
| Loading observed origins… | ||||
Observed origins come from the latest daily routing snapshot.
what this does and does not model
- Models the ROA objects present in the RPKI store on the store date, not router or validator policy. Local ROV policy, ASPA, and RPKI-to-router transport are out of scope.
- Models only the exact prefix entered. Sub-prefixes and other announcements inside the same address space are not modelled.
- Observed origins are the origins seen announcing this exact prefix in one daily routing snapshot. An origin missing from that snapshot may still announce the prefix.
- A covering ROA constrains this announcement only when its maxLength is at least the announced prefix length.
Provenance will appear here.