You can kick the tires here: https://rootbeer.testing.ns.internet2.edu/roa-planner/ The implementation remains fragile and will be unavailable intermittently, but we hope to improve it over the next couple of weeks. Please send me (ssw@internet2.edu) any suggestions, concerns, etc. From the help page: The RPKI-ROA Planner is a tool designed to help network operators efficiently plan their Route Origin Authorizations (ROAs), which are vital for securing BGP routing. To generate a comprehensive set of ROA recommendations for a user-supplied IP prefix, the Planner aggregates routing and registration information from four key sources: - Internet Routing Registry (IRR): Route Objects are gathered from services like https://stat.ripe.net/data/whois/. - Regional Internet Registries (RIRs): IP registration data is fetched from sources such as https://rdap.arin.net/registry/ip/. - Routing History: Historical routing data is analyzed using services like RIPEstat (https://stat.ripe.net/data/routing-history). - Global Route Views: The Planner includes routes observed in the global research and education community (via Routeviews). Crucially, these routes may be longer (more specific) than those typically seen in the Default-Free Zone (DFZ). Assumption: If a route was observed in the past, is currently visible, or is documented in an IRR object, it is a candidate for a new ROA. It excludes any candidate routes that are already covered by an existing, valid ROA, ensuring you only focus on what's missing. All candidate routes are presented to you in the table. You have full control to deselect individual routes or use age filters to exclude older, potentially stale data before the final ROA set is calculated. The Planner prioritizes generating multi-prefix ROAs (covering multiple routes with one authorization) over single-prefix ROAs. Using multi-prefix ROAs is the recommended best practice for maintaining cleaner, more efficient RPKI records. thanks! Steven Wallace Director - Routing Integrity Internet2 ssw@internet2.edu