Reference

My RPO status shows late - is my data at risk?

RPO status is an operational measurement of sync freshness, not a verdict on existing recovery data.

ReadyCurrentrporeplicationsync

The Short Answer

A late RPO status means the target's last successful sync is older than the pattern's sync interval. Your existing recovery points and replica state are unaffected - what is at risk is only how recent the recovery point would be if you failed over right now.

RPO status is a measurement based on the last successful sync, the target's current state, and whether work is queued or blocked. It is not a guarantee, and a late reading is a prompt to investigate, not a data-loss event.

Where To Look

Check the target's last sync result and error state - a failed sync usually explains the gap.
Check whether syncs are queued behind pattern concurrency limits.
Check controller health: syncs are blocked while a controller is unreachable.
If a sync was interrupted, checkpoint recovery may be required before normal syncs resume.