High ping (400+ ms) to instance server (Japan realm)

Japan realm has instances servers with high ping:



Creating new location instances usually fixes that problem, but it's impossible to create new instance of map (without losing it) and The Labyrinth room.

Client log
"
2019/03/09 22:22:26 18857993 da [INFO Client 5144] Connecting to instance server at 165.192.78.132:6112
2019/03/09 22:22:26 18858087 163 [DEBUG Client 5144] Connect time to instance server was 94ms
2019/03/09 22:22:28 18860146 a50 [INFO Client 5144] : You have entered Battle-scarred Hideout.
2019/03/09 22:22:40 18872174 da [INFO Client 5144] Connecting to instance server at 34.85.63.38:6112
2019/03/09 22:22:41 18872595 163 [DEBUG Client 5144] Connect time to instance server was 405ms
2019/03/09 22:22:47 18878538 a50 [INFO Client 5144] : You have entered Alleyways.

WinMTR log
"
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Pekarna - 0 | 106 | 106 | 0 | 2 | 28 | 1 |
| 10.26.100.1 - 3 | 99 | 97 | 1 | 2 | 12 | 2 |
| 10.2.100.33 - 1 | 103 | 102 | 6 | 9 | 100 | 10 |
| 10.2.100.125 - 3 | 99 | 97 | 6 | 8 | 77 | 8 |
| 10.8.2.17 - 0 | 106 | 106 | 5 | 7 | 24 | 5 |
| 10.2.200.18 - 0 | 106 | 106 | 5 | 8 | 76 | 6 |
| 10.8.102.137 - 0 | 106 | 106 | 6 | 183 | 1061 | 445 |
| 10.2.200.5 - 0 | 106 | 106 | 6 | 9 | 80 | 7 |
| vvk06.transtelecom.net - 1 | 103 | 102 | 7 | 15 | 107 | 7 |
| mskn17ra-lo1.transtelecom.net - 1 | 105 | 104 | 113 | 118 | 167 | 114 |
| Google-gw.transtelecom.net - 13 | 71 | 62 | 132 | 140 | 161 | 136 |
| 108.170.250.47 - 12 | 75 | 66 | 0 | 145 | 181 | 140 |
| 209.85.240.102 - 9 | 79 | 72 | 151 | 159 | 180 | 157 |
| 209.85.142.51 - 5 | 91 | 87 | 164 | 174 | 205 | 164 |
| 216.239.47.100 - 8 | 84 | 78 | 171 | 180 | 202 | 174 |
| 209.85.143.252 - 9 | 83 | 76 | 182 | 197 | 233 | 191 |
| 108.170.237.243 - 6 | 87 | 82 | 181 | 190 | 234 | 182 |
| 172.253.51.158 - 6 | 87 | 82 | 249 | 256 | 328 | 249 |
| 216.239.57.196 - 5 | 93 | 89 | 265 | 295 | 313 | 301 |
| 72.14.239.209 - 12 | 75 | 66 | 304 | 315 | 341 | 304 |
| 72.14.238.85 - 5 | 91 | 87 | 305 | 311 | 334 | 312 |
| 209.85.246.232 - 6 | 87 | 82 | 394 | 418 | 509 | 394 |
| 209.85.143.247 - 9 | 79 | 72 | 397 | 404 | 433 | 404 |
| 209.85.244.63 - 5 | 91 | 87 | 397 | 403 | 415 | 401 |
| 108.170.242.193 - 15 | 67 | 57 | 400 | 406 | 420 | 401 |
| 209.85.253.60 - 3 | 99 | 97 | 396 | 402 | 490 | 396 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Last edited by YobaYoba on Mar 9, 2019, 7:54:44 AM
Last bumped on Mar 11, 2019, 11:29:01 PM
Looking at the test it appears like there are too many hops, looking a bit deeper, the ip addresses of the hops show that you are getting routed to the US before getting back to japan, that would generaly indicate a problem big enough that the connection has to be re routed around it, and by the looks the chosen path is being over used as you start getting packet loss over 10% not to mention the increased latency due to the disatence.
Ancestral Bond. It's a thing that does stuff. -Vipermagi

He who controls the pants controls the galaxy. - Rick & Morty S3E1
"
YobaYoba wrote:
Japan realm has instances servers with high ping:



Creating new location instances usually fixes that problem, but it's impossible to create new instance of map (without losing it) and The Labyrinth room.

Client log
"
2019/03/09 22:22:26 18857993 da [INFO Client 5144] Connecting to instance server at 165.192.78.132:6112
2019/03/09 22:22:26 18858087 163 [DEBUG Client 5144] Connect time to instance server was 94ms
2019/03/09 22:22:28 18860146 a50 [INFO Client 5144] : You have entered Battle-scarred Hideout.
2019/03/09 22:22:40 18872174 da [INFO Client 5144] Connecting to instance server at 34.85.63.38:6112
2019/03/09 22:22:41 18872595 163 [DEBUG Client 5144] Connect time to instance server was 405ms
2019/03/09 22:22:47 18878538 a50 [INFO Client 5144] : You have entered Alleyways.

WinMTR log
"
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Pekarna - 0 | 106 | 106 | 0 | 2 | 28 | 1 |
| 10.26.100.1 - 3 | 99 | 97 | 1 | 2 | 12 | 2 |
| 10.2.100.33 - 1 | 103 | 102 | 6 | 9 | 100 | 10 |
| 10.2.100.125 - 3 | 99 | 97 | 6 | 8 | 77 | 8 |
| 10.8.2.17 - 0 | 106 | 106 | 5 | 7 | 24 | 5 |
| 10.2.200.18 - 0 | 106 | 106 | 5 | 8 | 76 | 6 |
| 10.8.102.137 - 0 | 106 | 106 | 6 | 183 | 1061 | 445 |
| 10.2.200.5 - 0 | 106 | 106 | 6 | 9 | 80 | 7 |
| vvk06.transtelecom.net - 1 | 103 | 102 | 7 | 15 | 107 | 7 |
| mskn17ra-lo1.transtelecom.net - 1 | 105 | 104 | 113 | 118 | 167 | 114 |
| Google-gw.transtelecom.net - 13 | 71 | 62 | 132 | 140 | 161 | 136 |
| 108.170.250.47 - 12 | 75 | 66 | 0 | 145 | 181 | 140 |
| 209.85.240.102 - 9 | 79 | 72 | 151 | 159 | 180 | 157 |
| 209.85.142.51 - 5 | 91 | 87 | 164 | 174 | 205 | 164 |
| 216.239.47.100 - 8 | 84 | 78 | 171 | 180 | 202 | 174 |
| 209.85.143.252 - 9 | 83 | 76 | 182 | 197 | 233 | 191 |
| 108.170.237.243 - 6 | 87 | 82 | 181 | 190 | 234 | 182 |
| 172.253.51.158 - 6 | 87 | 82 | 249 | 256 | 328 | 249 |
| 216.239.57.196 - 5 | 93 | 89 | 265 | 295 | 313 | 301 |
| 72.14.239.209 - 12 | 75 | 66 | 304 | 315 | 341 | 304 |
| 72.14.238.85 - 5 | 91 | 87 | 305 | 311 | 334 | 312 |
| 209.85.246.232 - 6 | 87 | 82 | 394 | 418 | 509 | 394 |
| 209.85.143.247 - 9 | 79 | 72 | 397 | 404 | 433 | 404 |
| 209.85.244.63 - 5 | 91 | 87 | 397 | 403 | 415 | 401 |
| 108.170.242.193 - 15 | 67 | 57 | 400 | 406 | 420 | 401 |
| 209.85.253.60 - 3 | 99 | 97 | 396 | 402 | 490 | 396 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider



You're seeing the same as me - The most bizarre Tokyo route ever! - Google new host!.

For some reason, random instances are connecting to Google in California, hence the massive latency increase.
I have opened a case with Google to see if they can assist us in fixing this.
"
Fitzy_GGG wrote:
I have opened a case with Google to see if they can assist us in fixing this.


Thanks for the reply. Out of curiosity, why are we connecting to Google at all?
We're using Google Cloud Platform for some of our extra capacity at launch.
"
Fitzy_GGG wrote:
We're using Google Cloud Platform for some of our extra capacity at launch.


I hope you find a solution for this soon, the game is pretty much unplayable as it is.
yeah same problem. as i already wrote here
https://www.pathofexile.com/forum/post-reply/2452578

Hope it will be fixed..
Google came back with the reason why this is happening:
"
The latency that your clients are experiencing is normal as the Russian Internet Service Provider (ISP) Rostelecom route their traffic from Vladivostok to Moscow since they have a peering with Google there. The traffic then moves back towards Japan from Moscow through Google network which takes a significant time as google does not have connections through Russia.
In this case, as Rostelecom peers with google in Europe, the best solution for serving Rostelecom customers from GCP is to serve them from instances located in Europe.


It's likely something you'd need to take up with your ISP. Though, you may connect to less of these instances now as time goes on, which may make this less of a problem.
"
Fitzy_GGG wrote:
Google came back with the reason why this is happening:
"
The latency that your clients are experiencing is normal as the Russian Internet Service Provider (ISP) Rostelecom route their traffic from Vladivostok to Moscow since they have a peering with Google there. The traffic then moves back towards Japan from Moscow through Google network which takes a significant time as google does not have connections through Russia.
In this case, as Rostelecom peers with google in Europe, the best solution for serving Rostelecom customers from GCP is to serve them from instances located in Europe.


It's likely something you'd need to take up with your ISP. Though, you may connect to less of these instances now as time goes on, which may make this less of a problem.


Thanks for the feedback Fitzy.

As it's highly unlikely Rostelecom will change their peering in this situation, we're basically screwed. Basically boils down to not playing PoE, for at least the first month or so, every time the league changes. How about bringing back the Vladivostock server from the Garena days...

Report Forum Post

Report Account:

Report Type

Additional Info