Netduma R2 — PS5 Call of Duty feels delayed despite Open NAT, 45–50 ms ping and 0% packet loss

[Oguzhan]

 

Hi,

I’m experiencing inconsistent gameplay and a significant feeling of delay in Call of Duty on PS5. I would appreciate help diagnosing the cause rather than changing settings without knowing what is responsible.

My setup:

• Fiber-to-the-home (FTTH) connection in Istanbul, Turkey: 1000 Mbps download / 50 Mbps upload.
• ZTE H3600 router → Netduma R2 WAN port → PS5 connected to an R2 LAN port by Ethernet.
• DumaOS version: 4.0.258.
• Only the PS5 is connected to the R2, with no other household internet activity during testing.
• The R2’s WAN IP is configured as the DMZ host on the ZTE.
• UPnP is enabled on the R2. The old manual UDP 3074 forwarding rule targeting the PS5’s former Wi-Fi address has been disabled.
• In-game NAT now shows Open.
• Geo-Filter filtering and Steady Ping are both disabled for the latest tests.

The problem:

Offline gameplay feels completely smooth and responsive. Online, some matches feel reasonably good, while others feel noticeably heavy and delayed. I often die before I can aim when encountering an opponent, or lose despite firing first. It feels as though I am behind what the opponent is seeing, although I have no measurement of that delay.

The game typically reports 45–60 ms ping and 0% packet loss. In the latest comparison, one match felt acceptable at 45–46 ms, while the next felt much worse at approximately 50 ms.

Tests so far:

• Fixing NAT from Moderate to Open did not noticeably improve the gameplay.
• The issue persists with filtering and Steady Ping disabled.
• Restarting the upstream router did not resolve it.
• I previously experienced similar symptoms when playing directly through the ZTE without the R2.
• Two matches through a mobile hotspot felt more responsive despite higher ping of 85–100 ms. However, that connection was less stable, and I cannot confirm whether those matches used the same servers as the fiber connection.

What measurements or logs can I collect to distinguish between ISP routing, jitter, game-server behavior, and any contribution from the R2?

Can the R2 capture useful latency variation or game-traffic diagnostics during an affected match? Please let me know the specific data and screenshots you need.

Thank you.

[Oguzhan]

How can I obtain the actual game server IP for an active PS5 match on R2 firmware 4.0.258? The Geo-Filter only shows the host location and Server ID. I want to compare traceroute and latency measurements to the same endpoint over my FTTH connection and mobile hotspot.

[Netduma Fraser]

There isn't really any data you can get from the router including the IP directly to help with what you're asking and traceroutes can be quite unreliable. ALL devices should be connected to the R2 for QoS to be most effective, even if you think other devices aren't being used background updates could affect you - how have you set Congestion Control? If you're experiencing it without the R2 in play then I suspect it's more of a location issue in relation to the closest servers. What you found with phone data does make sense, you likely had a ping where lag compensation started working in your favour or the servers you were on had less load. Force servers slightly further away with the Geo-Filter even if they have a higher ping and see if they play better for you.