Cisco RV260 stuck freezes stops responding

[emwu90]

For some time now, I've been experiencing issues with RV260 routers. The problem is that, for unknown reasons, the router freezes/stuck and stops responding to ping and others protocol requests on both the WAN and LAN.

The LED's continue to light up (screen in attachment)

I have the latest firmware installed, which is Firmware Version 1.0.01.10.

Issues related to the ISP and local network do not seem to be the cause, as they are functioning correctly.

The only solution is to restart the device, after which it resumes normal operation.

I have attached the latest router logs (debug mode), which have been sent to the syslog server:

Has anyone else encountered a similar problem with this device? I also have RV340 devices, and they work correctly without any freezing issues.

The issue becomes particularly problematic as I only have remote access to the device through VPN and site-to-site connections. In the event of a freeze / stuck, I lose access to the device and local network.

[pieterh]

this router has basically the same error as before the WAN link is lost, no backup link is configured
and is restored again when " WAN: COPPER Link is Up"

what does the "intermediate" switch show in the logging ?
can you find here information about  the port to the ISP or the port to the router ?
if this shows the ISP link as flapping, you know were the fault lies
if this shows the router link flaps, then  a fault in the router  (power supply faulty or temperature too high) is most likely cause

[emwu90]

Update on the situation:

We have started the process of resetting RV260 routers to factory settings. In several locations, the situation has improved, and the issue no longer occurs last months (by the way, this is the first time I've come across devices that freak out after a while and have to be rebooted to factory settings)

However, sporadic occurrences persist in some locations, clearly indicating a problem with the device/software...

@pieterh No, there are neither ISP issues nor high temperature problems there. The logs are incorrect, because the router is going crazy...