Network & Infrastructure / BGP Policy & Internet Edge
RPKI cache failure and the router's retained validation state
A validator connection fails, yet routing decisions do not change immediately. Another router changes behavior much sooner, producing inconsistent reachability at the same Internet edge.
Environment and inputs: BGP speakers and route reflectors; policy syntax, RPKI integration and address-family behavior depend on the implementation. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Record cache session state, last successful synchronization, retained dataset age, expiration settings and router import policy. Distinguish validator reachability from route validity in the incident timeline.
Explain the result
Implementations can retain validated data for configured intervals. A transport failure does not automatically mean all routes become invalid, and treating every failure as invalid can cause a broad outage.
Plan the fix
Design redundant validators and explicit stale-data behavior using the deployed router documentation. Keep monitoring of cache age separate from counts of valid, invalid and not-found prefixes.
Check the result and rollback
Exercise cache loss without changing advertisements in a lab. Confirm expected expiration transitions and restore the original policy if the fallback unexpectedly suppresses legitimate routes.