I had steady 120ms latency last week but currently its over 300 ms
|
I attach the WinMTR
i am living in south korea and was okay to play in singapore server last week. After the sudden d/c on friday, the latency went up by 300 at this moment. I thought it was just a sudden problem, but it still last till now. I do not know how to interpret this so please help me out with this. ps. I had 200ms latency in Amercia server before and i still have almost same latency. in case this info would help you to figure out.
Spoiler
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.0.1 - 16 | 94 | 79 | 1 | 1 | 8 | 1 | | 123.212.66.1 - 0 | 158 | 158 | 3 | 10 | 39 | 8 | | 211.244.169.161 - 0 | 158 | 158 | 1 | 3 | 9 | 4 | | 58.229.67.249 - 0 | 158 | 158 | 1 | 6 | 201 | 2 | | 1.255.23.29 - 0 | 154 | 154 | 3 | 36 | 4155 | 6 | | 118.221.7.50 - 0 | 155 | 155 | 3 | 31 | 4150 | 4 | | 58.229.14.238 - 0 | 155 | 155 | 2 | 31 | 4144 | 6 | | 58.229.92.170 - 2 | 150 | 148 | 254 | 264 | 396 | 261 | | ae-3.r25.tokyjp01.jp.bb.gin.ntt.net - 5 | 131 | 125 | 254 | 305 | 4393 | 334 | | xe-1-0-0.r20.tokyjp03.jp.bb.gin.ntt.net - 4 | 134 | 129 | 253 | 296 | 4381 | 259 | | xe-2-0-0.r20.tokyjp03.jp.ce.gin.ntt.net - 4 | 132 | 127 | 257 | 300 | 4381 | 264 | | ae1.bbr01.eq01.sng02.networklayer.com - 3 | 142 | 139 | 327 | 368 | 4393 | 329 | | ae5.dar01.sr03.sng01.networklayer.com - 3 | 139 | 135 | 338 | 375 | 4365 | 345 | | po1.fcr01.sr03.sng01.networklayer.com - 2 | 150 | 148 | 325 | 334 | 459 | 333 | |216.12.203.90-static.reverse.softlayer.com - 4 | 135 | 130 | 325 | 363 | 4365 | 336 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider | |
|
58.229.92.170 is the Korean edge router, and seems to be the bottleneck. See if you can't get your ISP to fix this problem.
|
