Last saturday i checked my ping to my nordvpn IP address that i connect to los angeles. I use for /l %i in (1,1,254) do @ping 185.202.221.%i -w 10 -n 1 | find “Reply” to see a range of ping values. Lowest used to be 163ms, but now it has increased to at least 174ms.
Then i would try to use mudfish as it could be better, but the US west los angeles google 2 which used to be around 162-163ms, is now also 171ms.
I there something wrong with my connection to US west los angeles. It seems like it is only Los angeles, because connection to seattle and San francisco still seems OK on mudfish and NordVPN.
Hello. I use full VPN mode and from there I check the lowest RTT on the us west los Angeles nodes to connect to. Then i connect my computer to my Xbox and play from there.
I am saying that the nodes to us west for me have been higher recently. I am not sure if you are able to know why.
Umm… then are you meaning that you’re playing a game at Xbox and connecting it via your computer (which Mudfish is running)? Then it looks like you’re following Internet Connection Sharing with Mudfish, right?
Which “RTT Checking Method” found at “Setup → Program” menu do you use? As you can see, if you test from Command Prompt, it tests using ICMP protocol. However if “RTT Checking Method” for example is UDP, Mudfish uses UDP protocol to measure RTT.
Thank you for answering. I checked and seem to be using TCP. What should I be using to check? And will it allow my RTT to be accurate when I do my ping test?
If you want to match your ping between the result of Command Prompt and Mudfish, I think you can change the option to ICMP based. With ICMP based, I think it’ll become more similar with your result from Command Prompt.
However if the results between TCP and ICMP are different, it means your ISP or the upstream ISP has QoS (Quality of Service) rule on their network router. So I guess that it’s why TCP shows more less ping.
