I use Mudfish to reduce my ping in Valorant on the Frankfurt servers. I’ve been trying to use the TR Europe (Bursa - OneProvider) node, as it’s geographically closest to me and shows a good realtime RTT in the dashboard (around 40 ms). However, in-game I get unstable 80 ms, which is almost double the expected value and higher than my original ping.
I’ve tried:
Full VPN mode (no improvement, same 78-81 ms ping)
FastConnect (actually made my ping worse)
TR → DE routing (higher ping overall, ~110ms)
MTU tweaks and different protocol modes
Could this be a routing or tunneling issue between the TR node and Riot’s servers? Is there anything I can do, or is there a chance this might improve soon?
Interestingly, I also tried routing through the DE servers, and I got a lower ping (~65 ms, same as my default ping), even though Germany is much farther from me than Turkey.
I need some game packets to analyze for this case. If I know the game protocol properly, it’s based on Anycast - Wikipedia network so it’s a little bit unpredictable in my experience.
Hey! Thanks for the reply. I recorded the game packets as you requested and uploaded them. I would be very grateful if you could help me resolve this issue.
Let me know if you need any other information from me.
Thank you for your packet dump. I’d checked your packet dump but yes it looks the game server is still based on Anycast network.
However I found a workaround(?) to measure the ping but it requires a patch at Mudfish nodes. Currently I’m working on that part to support the new measurement way… So you might need to wait a little bit more until the new server version of Mudfish will be deployed…
Thanks for the update! That sounds promising. Just to clarify, will this patch actually help reduce my ping, or is it mainly for more accurate measurements?
Thank you for your interest. My patch is to provide more accurate measurements for this game item. So frankly it’s not related to your ping. However I expect that it’s more helpful to pick a proper mudfish node.