R3 connection freezing temporarily

[eggsmell]

About a few weeks ago, I started experiencing random connection freezes for 10-20 seconds a time, out of nowhere. While browsing the internet, streaming video, just gaming, combinations of both, etc.

The problem seems to be completely random, sometimes I go half a day without it happening, sometimes it happens 3-4 times within 30 minutes. It happens network-wide, and isn't an actual disconnection but just a hard freeze.

I have DHCP leases set to 10000 minutes on the devices I use the most, and SmartBOOST disabled. I'm also on the newest early access firmware, but this had also started occurring on the newest non-early access firmware as well. I have also factory reset since the problem began to no avail.

The logs are as follows when it occurs, I've been checking them periodically when it happens and these are the same regularly occurring messages that happen everytime. The freeze was inbetween 6:33:30 and 6:34:00, but I think the errors in that time frame might just be coincidental as they also show up outside of disconnect times.

Sat Jul 25 2026 06:34:05
daemon.err cli.lua[4275]: [WARNING]: ct 175db1: time went backwards!
daemon.err cli.lua[4275]: [WARNING]: ct 175db1: time went backwards!
daemon.err cli.lua[4275]: [WARNING]: ct 175db1: time went backwards!
Sat Jul 25 2026 06:33:52
user.notice hotplug: Device:eth0, Interface:wan6, Action:ifupdate user.notice hotplug: enter 25-routermac script for runner runtime config
Sat Jul 25 2026 06:33:50
user.warn overwatch: [WARNING]: Unable to load ov config file: json_load_document: (//www/json/ov_inf_extra_params.json) could not open file
Sat Jul 25 2026 06:33:46
user.notice hotplug: Device:eth0, Interface:wan6, Action:ifupdate user.notice hotplug: enter 25-routermac script for runner runtime config
Sat Jul 25 2026 06:33:15
daemon.err cli.lua[4275]: [WARNING]: ct 175db1: time went backwards!
daemon.err cli.lua[4275]: [WARNING]: ct 175db1: time went backwards!

[Netduma Fraser]

Are you able to connect to your ISP modem/router for a few days directly to see if you get the same issue without the R3? Did it start happening after changing any specific settings/anything with your hardware setup?