Forum Index Technical Support Latency problems on Japan realm

History

"
I have 40ms latency now, but it still jumps to 200 and 400 in different locations.
Yes :\

Dehale
Jun 17, 2019 12:33:41 PM

Reporting from Japan.

Seems like the changes they made made a difference! I played for about 3 hours tonight and I had no problems with lag or not being able to join instances. Even the annoying Delve problem was gone!

Thanks for taking the time and fixing this, I understand that new season launches are a lot of work and especially if the player base increases with it!

CalleTheBunny
Jun 17, 2019 18:16:32 PM

The datacenter reports that the new routing should be in place now. Is there an improvement?

Fitzy_GGG
Jun 18, 2019 06:52:10 AM

"
Fitzy_GGG wrote:
The datacenter reports that the new routing should be in place now. Is there an improvement?


i'll be back home in 4 hours, gonna check it out and post WinMTR traces

fataleast
Jun 18, 2019 06:54:50 AM

"
Fitzy_GGG wrote:
The datacenter reports that the new routing should be in place now. Is there an improvement?


I haven't played very much yet but so far, for me, It's actually very good. Surprisingly, it seems I can use lockstep again, which I wasn't able to with the IBM/Softlayer servers.

Only remaining issue for me is the random connections to Google cloud, which jumps the latency from ~45ms to ~400ms. Hopefully that will tail off as the league ages.

Thanks for the help Fitzy.

Edit: mtrs:

Spoiler
"
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| bashful.home.arpa - 0 | 200 | 200 | 0 | 0 | 1 | 0 |

| 10.251.14.125 - 0 | 200 | 200 | 3 | 10 | 12 | 8 |

| 10.251.14.124 - 0 | 200 | 200 | 2 | 2 | 25 | 2 |

| 87.226.133.15 - 0 | 200 | 200 | 34 | 35 | 56 | 34 |

| 218.100.7.69 - 0 | 200 | 200 | 35 | 35 | 44 | 35 |

| 10.0.0.6 - 0 | 200 | 200 | 35 | 36 | 38 | 36 |

| 103.102.160.162 - 0 | 200 | 200 | 35 | 35 | 38 | 35 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider



"
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| bashful.home.arpa - 0 | 31 | 31 | 0 | 0 | 1 | 0 |

| 10.251.14.127 - 0 | 31 | 31 | 3 | 5 | 7 | 6 |

| 10.251.14.124 - 0 | 31 | 31 | 2 | 3 | 30 | 3 |

| 87.226.181.89 - 0 | 31 | 31 | 105 | 105 | 111 | 105 |

| 5.143.253.105 - 0 | 31 | 31 | 105 | 106 | 115 | 105 |

| 108.170.250.130 - 0 | 31 | 31 | 106 | 106 | 108 | 107 |

| 209.85.250.110 - 0 | 31 | 31 | 124 | 124 | 125 | 124 |

| 172.253.50.211 - 0 | 31 | 31 | 145 | 150 | 158 | 146 |

| 172.253.51.198 - 0 | 31 | 31 | 146 | 163 | 180 | 173 |

| 172.253.66.14 - 0 | 31 | 31 | 149 | 150 | 159 | 150 |

| 108.170.234.119 - 0 | 31 | 31 | 156 | 157 | 161 | 156 |

| 172.253.65.174 - 0 | 31 | 31 | 225 | 236 | 255 | 240 |

| 216.239.57.136 - 0 | 31 | 31 | 239 | 240 | 257 | 256 |

| 209.85.143.103 - 0 | 31 | 31 | 248 | 251 | 294 | 248 |

| 72.14.233.237 - 0 | 31 | 31 | 289 | 291 | 339 | 289 |

| 108.170.235.217 - 0 | 31 | 31 | 370 | 370 | 371 | 371 |

| 64.233.175.105 - 0 | 31 | 31 | 376 | 377 | 378 | 377 |

| 209.85.244.34 - 0 | 31 | 31 | 377 | 377 | 379 | 377 |

| 108.170.242.97 - 0 | 31 | 31 | 372 | 372 | 374 | 372 |

| 108.170.228.118 - 0 | 31 | 31 | 376 | 376 | 378 | 376 |

| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |

| 59.77.85.34.bc.googleusercontent.com - 0 | 31 | 31 | 373 | 373 | 375 | 373 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Kellog
Jun 18, 2019 07:30:41 AM

"
Fitzy_GGG wrote:
The datacenter reports that the new routing should be in place now. Is there an improvement?
Ok Fitzy

Spoiler
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.10.1 - 0 | 887 | 887 | 0 | 0 | 1 | 0 |
| 100.66.0.1 - 0 | 887 | 887 | 0 | 0 | 1 | 1 |
| du-205-41.sv-en.ru - 0 | 888 | 888 | 0 | 0 | 1 | 1 |
| 188.128.29.53 - 0 | 888 | 888 | 17 | 17 | 31 | 18 |
| 95.167.95.101 - 0 | 887 | 887 | 74 | 75 | 98 | 75 |
| 218.100.7.69 - 0 | 887 | 887 | 74 | 75 | 98 | 75 |
| 10.0.0.6 - 0 | 887 | 887 | 75 | 75 | 79 | 75 |
| 103.102.160.138 - 0 | 887 | 887 | 74 | 75 | 77 | 75 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

https://youtu.be/52lnuyD1gjg

Dehale
Jun 18, 2019 07:57:36 AM


The menu shows ping 30. And in fact ping 300: D
Cheating: D

Kreyd
Jun 18, 2019 09:06:54 AM

Yeah, unfortunately google are not as accommodating. Last time I raised this with them, they said:

"
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.

Fitzy_GGG
Jun 18, 2019 09:38:31 AM

"
Fitzy_GGG wrote:
Yeah, unfortunately google are not as accommodating. Last time I raised this with them, they said:

"
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.


I appreciate they don't host in Russia, at least not directly, what I don't understand is why they don't just offload the traffic in one of their European locations. They're obviously routing through Europe to get to back to JP and they appear to jump through hoops once they get there.

Kellog
Jun 18, 2019 10:07:05 AM

"
Dehale wrote:
"
Fitzy_GGG wrote:
The datacenter reports that the new routing should be in place now. Is there an improvement?
Ok Fitzy

Spoiler
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.10.1 - 0 | 887 | 887 | 0 | 0 | 1 | 0 |
| 100.66.0.1 - 0 | 887 | 887 | 0 | 0 | 1 | 1 |
| du-205-41.sv-en.ru - 0 | 888 | 888 | 0 | 0 | 1 | 1 |
| 188.128.29.53 - 0 | 888 | 888 | 17 | 17 | 31 | 18 |
| 95.167.95.101 - 0 | 887 | 887 | 74 | 75 | 98 | 75 |
| 218.100.7.69 - 0 | 887 | 887 | 74 | 75 | 98 | 75 |
| 10.0.0.6 - 0 | 887 | 887 | 75 | 75 | 79 | 75 |
| 103.102.160.138 - 0 | 887 | 887 | 74 | 75 | 77 | 75 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

https://youtu.be/52lnuyD1gjg


What you're probably seeing is what I mentioned in my earlier post. GGG now use Google Cloud for additional server capacity at the beginning of a league. Unfortunately for us, Google don't host in Russia and their peering with Russian Telecoms only goes West, so they route the traffic, through Europe back to Japan, hence the latency jump. Check the IP of the instance with the high latency.

Kellog
Jun 18, 2019 10:12:35 AM
  • Prev
  • 1
  • 2
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 18
  • 19
  • Next