Updating your BGP configuration isn’t enough when deploying or leasing IPv4 resources.
If your Route Origin Authorization (ROA) still authorizes a different ASN than the one announcing the prefix, networks performing RPKI Route Origin Validation (ROV) may classify your route as Invalid.
This can lead to:
Route rejection by RPKI enabled networks
Reduced reachability across the Internet
Unexpected connectivity issues for your users
Hours of unnecessary troubleshooting
Before announcing a new or leased IPv4 prefix, always verify that:
The correct origin ASN is authorized
The ROA reflects your intended routing policy
Outdated ROAs have been updated or removed
A ROA review takes only a few minutes, but it can prevent major routing issues.