Hawaii to Hong Kong, is this the lowest ping it can go?

It’s been a while since I’ve played World of Tanks again. Last time, I used Mudfish to great success, as it was able to reduce my ping from 250 down to a manageable 130-150 ms. However, after I stopped playing, it looks like WoT Asia has moved their servers from SG to HK. Now, my ping without Mudfish is 220-230 whereas with Mudfish, it now only goes down to 200ms, still too high for a competitive game like this. Despite any attempts to use different nodes and whatnot, I can’t seem to improve my ping. Is this really the limit for me?

Umm… Did you try to use the advanced node mode too? I’m not sure that there’s a good route for you. At least with the basic mode, it seems you’ll have a limited result to improve your ping.

Looks like there was an update earlier that changed routes to China, as I noticed that my connection got worse. After installing the new updates, I did see that there are new nodes to connect to, but sadly it still is just as worse as last time, only reaching 200ms.

I was looking for FAQs about the advanced node mode, and I think the information about China server is relatively new, so that’s a surprise. Not sure if that’s a response to this question or it was just a coincidence.

So yeah, tried advanced node mode and see if there’s any “recommendations”, and it just shows the same information as the basic mode, choosing one connection favorably, albeit still 200ms ping. When I click that in the advanced mode, the window closes and on the main window, it just chooses that same connection as basic mode. Will I have to experiment what two nodes to use myself, or is the recommendation really the best one that it can do?

https://pop.he.net/?city=honolulu

core1.hkg1.he.net> traceroute 64.62.205.38 source 27.50.33.1 numeric|Target|64.62.205.38|
| — | — |
|Hop Start|1|
|Hop End|30|

Hop Packet 1 Packet 2 Packet 3 Hostname
1 53 ms 53 ms 53 ms 100ge10-1.core1.tyo1.he.net (184.105.64.130)
2 131 ms 131 ms 140 ms 10ge11-11.core1.hnl1.he.net (184.105.213.85)
3 135 ms 131 ms 131 ms university-of-hawaii.10gigabitethernet11-17.core1.hnl1.he.net (64.62.205.38)

The lowest ping between Hong Kong and Hawaii is 131ms. (honolulu - japan - hong kong)
If routing goes to the United States(east), it will be more than 200ms.
You need to find the route that uses AAG(hawaii-guam-ph-hk) or JUS(hawaii-jp) or SEA-US(hawaii-guam) submarine cables.

Thanks for the help. I tried to go to Advanced Mode and select a JP node that has 160ms, then to a HK server. Same thing happens though, traceroute immediately jumps to 215ms as soon as it hits the node. Does it mean it’s not utilizing the correct cables?

  1. 1 <1 ms <1 ms <1 ms 10.254.45.1
  2. 2 213 ms 213 ms 214 ms 10.233.160.1
  3. 3 214 ms 213 ms 227 ms 10.255.255.102

Strangely enough, I use the same IP (27.50.33.1) that you used to test and got sub 200ms ping. It didn’t use any of the nodes that I setup though, immediately going through a JP server then hopping to HK with far less ping…

The IP of WoT according to MudFish is 92.223.52.5. Without Mudfish, my connection does go through east which causes the high ping…

Tracing route to 92.223.52.5 over a maximum of 30 hops

  1. 1 <1 ms <1 ms <1 ms 192.168.1.1
  2. 2 9 ms 12 ms 9 ms 142.254.190.145
  3. 3 25 ms 30 ms 26 ms agg63.hnllhiqe02h.hawaii.rr.com [24.25.232.153]
  4. 4 12 ms 12 ms 10 ms agg33.hnllhiik01r.hawaii.rr.com [72.129.46.88]
  5. 5 10 ms 12 ms 11 ms agg21.milnhixd01r.hawaii.rr.com [72.129.45.42]
  6. 6 69 ms 63 ms 63 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0]
  7. 7 64 ms 62 ms 62 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.102]
  8. 8 67 ms 63 ms 70 ms bu-ether45.chctilwc00w-bcr00.tbone.rr.com [107.14.19.36]
  9. 9 61 ms 62 ms 69 ms 0.ae2.pr1.lax10.tbone.rr.com [107.14.19.54]
  10. 10 61 ms 61 ms 60 ms 63-218-51-169.static.pccwglobal.net [63.218.51.169]
  11. 11 219 ms 218 ms 218 ms tenge0-1-0-17.br02.hkg12.pccwbtn.net [63.218.174.61]
  12. 12 * * * Request timed out.
  13. 13 * * * Request timed out.
  14. 14 217 ms 217 ms 218 ms 92.223.52.5

But yeah, still doing the same one node jump but with 200ms+ after that… Anything else I should do?