All Activity

There is likely still 1 or more Ireland servers you need to allow, allow one, restart the game, if needed allow again and repeat until you've got them all then try again.

i have allowed the dublin one, now i can see the us one. still cant connect

That dublin one is the one you need to allow, it's an authentication server, it's why you're getting the issue. You may need to redo the process a few times but once you've got them it will be fine. If you could provide the IDs also that'd be really helpful

Hi, everything is as you mentioned. If i put my geofilter on now on the east coast, i get the waiting for networking and then quits when starting the game. Nothing has been changed. If i geofilter in eu is fine. Version 4.0.645. I also set the pc as a console but had no issues until around 2 weeks ago. no servers are blocked. Now i cant even see servers in the us. Only dublin one keeps popping up yellow triangle. I also went back 2 firmware and same happened also jus tried anything outside uk and same error happens

The log needs to be prior to rebooting otherwise it won't have any useful information about the issue. In LAN Settings set a static/reserved IP for each device, reboot from the interface and see if it happens again.

It happened a couple hours ago, it disconnect everyday/night. It started happening for a month now. Here's the logs log-1770579631728.txt

Could you provide more information, what do you mean by crashing exactly? How often are you disconnecting? Is it on all devices? Do you need to reboot for it to come back on or do they restore themselves? Can you provide the log from the System Information page when it next happens please?

Does anyone know why my router keeps crashing/disconnecting? 3 PC 1 Console 12 wifi devices

Good to hear - have you fine tuned QoS to ensure it's not caused by local congestion?

Haha thanks! That's the Early Access firmware so you're on the latest currently. You can check if they've been run by going to Speed Test > History & Ping Optimizer > History, if they haven't been run then it's likely the router detected the servers were not available and cycling through trying to find an available one ready for when you do run it - their servers are not always available so that's not unlikely. The DHCP lease is once a week but it could be all spread out depending on when that device connected initially. It's also just a good precaution, by setting as static/reserved they'll never change so it'll completely remove it as being a potential cause.

yep works now i had to disable and re enable , also ping is very inconsistent in val despite only london servers as i can load in get 6-8ms and then sometimes it gets 200ms plus for some reason.

To force servers you need to do the following: It's essential the Geo-Filter is enabled before the game client (e.g. Steam etc) if on PC or platform (e.g. Xbox, PlayStation) or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working. For settings ensure Ping Assist and Geo-Latency are disabled in the Geo-Filter menu that can be found by clicking ⋮ in the top right hand corner of the page and go to Settings. Strict Mode should also be enabled, it is enabled by default so if you haven't disabled it you can ignore it. If you have disabled it or want to check it can be found in the same Settings menu as above or in Settings > Troubleshooting > Advanced > Developer Options depending on your firmware version. Fast Search should also be disabled which it is by default so can be ignored if you haven't changed it, otherwise this can be found in the same place. If you're getting the disconnect after doing this then ensure you zoom out fully to see if there is a server being blocked, if so then add it to your allow list - you may need to do it a few times but then when done it should work fine when enabled.

I'd generally recommend using the Geo-Filter yes but I just want you to disable it for the moment to see if the issue still occurs.

After this selecting east coast US i get exit desktop or reconnect. Basically the 1st screenshot i posted after the fw upgrade.

Quindi consigli di lasciarlo acceso?

So flushed the new firmware. Now i get this. Geo latency is turned off.

God I love how knowledgeable you are. Okay so RGB confirmed issue thats fine I have it turned off anyway. As for the version I am not running early access if there is a new one can you send me a link happy to try it out. But im currently on v4.0.645 As for the speed tests/ optimiser I haven't run those in a very long time. So idk why it's running them in the background. I set them up shortly after 4.0.645. Haven't touched since. I have a 1000/100 connection so QOS isn't a huge issue for my daily use. I can do the DHCP I guess see if that helps not sure why it's releasing them early though? but sure ill give it a go.

The RGB we've seen happen on other routers so that's not a hardware issue - a replacement would not fix it, the time going backwards is log spam but is harmless, we'll be sorting that. Are you on the Early Access version currently? Are you running the speed test/ping optimizer tests and then concerned that you're getting disconnects/dropouts? As those tests by design disconnect all devices so it's a pure test from the router to the internet. You don't need to be running these tests often. Do a speedtest.net test to figure out your full/expected speeds, enter those into the router then you don't need to run the speedtest. Ping Optimizer changes the Congestion Control percentages which you can do manually, find the best percentages for you and then you don't need to touch this again either. Other than that the only other indicators for potential disconnects etc can be resolved: In Settings > DHCP > Add Rules > Select Device > Save. Do that each device you're noticing the disconnects/issues with. Then in DHCP > Advanced change the lease time to 10000, save, reboot the router from the interface and see if it happens again please.

Disable Geo-Latency in Geo-Filter settings if you haven't already and try again. I've also given you access to the Early Access firmware: https://forum.netduma.com/forum/151-netduma-r3-early-access/

Does it occur if the Geo-Filter is disabled before launching the game?

Just factory reset it. Still happens. It ignores the geofilter

Hey Fraser, Sorry for the delay in getting back to you. I only returned about a week ago and haven’t been home much, but I’ve been around more this week and can confirm the issue is still very persistent. Normally when these problems occur, I’m unable to log into the router at all to download logs, as the UI becomes unreachable. This time, however, I was able to log in during one of the instability periods and successfully capture the logs, which I’ve attached here. In day-to-day use, the main symptoms are intermittent loss of connectivity (primarily affecting Wi-Fi clients), long buffering or stalls on streaming services (e.g. YouTube), and periods where the router becomes unresponsive until it eventually recovers on its own — or more often requires a hard power cycle at the wall. Ethernet usually continues to function while Wi-Fi does not, although this isn’t guaranteed. From a quick review of the logs, there appear to be repeating loops of errors, including multiple warnings around system time going backwards (cli.lua: time went backwards), frequent Smart QoS / benchmark test failures and retries, and regular WAN hotplug or interface updates occurring around the same time as the instability. These events seem to line up closely with when the router becomes unresponsive or client connections stall. I’ve done several clean installs using the latest firmware, so I don’t believe this is related to a bad install. We’ve also been on this firmware version for quite some time now (close to a year), so it should be considered relatively stable at this point. Hopefully these logs help identify the underlying cause. Please let me know if there’s anything specific you’d like me to test or capture next. That said, taking all of these issues together — along with the RGB on my unit, which I’m now fairly certain has failed — it does feel like this may be pointing toward a hardware-related issue. I’m open to your thoughts on this or any additional steps you’d like me to try, but I may need to start considering a replacement unit if appropriate. Kind regards, Zac R3_2026-02-08T09_22_13.020Z_logs.txt