vSphere Replications are showing that they are exceeding the RPO but still replicating.
vSphere Live Recovery (All Versions)
vSphere Replication when it faces various networking problems, such as, firewall issues, networking issues, DNS, or IP issues, can lead to performance degradation on replicating virtual machines. Such as the following messages, repeating in the vmkwarning.log on a source ESXi host:
2024-08-02T09:53:47.758Z Wa(180) vmkwarning: cpu66:4651443)WARNING: Hbr: 5362: Failed to establish connection to [127.0.0.1]:32032 (groupID=GID-####-####-####-####-############): Broken pipe
Other networking messages may be found, like this, inside the HBR log on the vSphere Live Recovery appliance.
Powering off and then powering on the vSphere Live Recovery appliance can clear these issues and should be a first step and may resolve the issue.
For further troubleshooting, if this solution does not work, please refer to: vSphere Replication Troubleshooting