:-) Thank you for using my service. I think this problem is caused by the standard deviation of RTT value because the RTT score is a sum of RTT average and standard deviation. For example, please refer the following table:

* SG Asia (Singapore - Amazon EC2)
19.0451
122.7559
* SG Asia (Singapore - DigitalOcean)
52.0711
169.6145
* SG Asia (Singapore - SecureAX)
17.1928
122.8581
* SG Asia (Singapore - SecureAX)
32.6292
172.3846

This table show that e.g. SG Asia (Singapore - Amazon EC2), the average of RTT is 19.04 ms but standard deviation is 122 ms pointing that the connection or network is very unstable at this moment.

In that case, you should select other Mudfish node to connect but if all of them are high in a view of RTT score, it seems it'd be better to select a node whose stddev. value is more lower.

Thanks for the update. Unfortunately the high RTT scores I'm seeing have been affecting my ping in CSGO as well though. Even when I choose the best server with the Wizard, lately I can only get my ping as low as 130 or so. For the past couple months, I had stable pings in the 80s. Any idea why I can't get a good connection in CSGO anymore? =/ I started using a free service called Wtfast which lets me get a ping around 100..but that's nothing like the 80 I used to get with Mudfish..

Yes the high RTT scores should affect your the ping value too. Depending on the status of international network line, this RTT could be vary sometimes and according to the data stored in the server side, all KR based mudfish nodes have a high RTT value to the game server.

Did you try to use ADN mode of mudfish? Though I couldn't guarantee the result, it would be one of which you can try. http://en.loxch.com/docs/faq/html/#what-s-adn-mode