SevenDeviations

It's still an issue even with the cloud update, and upgrading to early access does not help.

I installed the beta, hoping it would solve the issue. It did not, the issue is still persisting, and it seems to happen only when not gaming. Also after installing the beta sometimes I can't load into Call Of Duty, I get the "Server disconnected" error at launch. Not sure if it's a GeoFence bug but I use no smart boost, no adblocker etc. When I turn the GeoFence off and completely delete the divice from the geofence menu it seems to help. I might just go back to the regular R2 OS at this point and see if it's fixed. R2_2025-04-29T19_19_08.340Z_logs.txt

I'm having the same issue as some others have said. I have an R2 with the latest firmware, plugged into my ISPs router already in bridge mode, and I get these random disconnects about once per hour. I attached my log. I've had the R2 since it came out and never had these issues until recently. I use QOS at 70% down 90% up and do not use HybridVPN. log-1745853470738.txt

I was wondering how big of a deal Double NAT is when it comes to games like COD. Right now I have my R2 connected to my other router, not in DMZ , so I have double NAT. I don't have access to the first router's settings, as they are managed by the house owner. My bufferbloat is consistently in the A to A+ range when I have the double NAT R2 plugged in, as opposed to when I plug directly into my ISP router my bufferbloat is a D score. My question is does double NAT really introduce any hidden network latency that would effect things like hit detection etc.? On my R2 I have my QOS capped at 10mbps and 10mbps down and generally have the best results with that.

It's definitely super weird, I feel like I get deleted super fast even if I shoot first.

I'm having a similar issue to what one guy said earlier, where the game will only put me in the Tokyo server. I'm in the US east coast. I tried the usual steps on the R2 to reset it, Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter with the manual option Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client But for some reason my matchmaking starts at 170ish ping and it always puts me on the Tokyo server, even though I have the New Jersey server simple geo-fenced. When I switch over to MW3, and even MW2 everything is normal and it works as intended putting me on the NJ server every time. With ping assist on it seems to half work, it will connect me to US servers again but ones that are above my 30 ping assist settings. Interested to see if testing reveals anything.

I fixed it, thanks

Same thing happened to me as well. I went through the same steps as usual to fix it but to no avail.