Protect the connectivity your customers rely on
Plan renewal alongside your network operations so the addresses and routing support behind your services stay ready. Check your service dates, the prefixes in use and your originating ASN before the renewal comes due.
How RPKI supports your network
RPKI lets networks check whether an ASN is authorized to originate an IP prefix. A Route Origin Authorization, or ROA, records the prefix, authorized ASN and permitted prefix length. Keeping those details aligned with your BGP announcement helps other networks validate your routes.
If a renewal has lapsed
- Contact LARUS support or your account manager with the affected prefixes and service reference.
- Complete the renewal and ask the team to check the ROAs and routing support for those resources.
- Share your originating ASN and observed routing status so the team can investigate the actual announcement and follow the recovery through.
The original service notice explains that an expired, unrenewed service can lose its associated RPKI records. The effect depends on the remaining authorizations and the receiving network. NotFound means no authorization covers the prefix; Invalid means a covering authorization exists but does not match. They are different states.
Make the next renewal straightforward
Keep your service dates and operational contact details up to date. If a route needs attention, bring the observed prefix and ASN to support early. Restoration follows the actual routing and validation updates; your support team can track progress for your case.