Latency problems on Japan realm

Oh gods, help GGG to repair shitty server!
Russian Heisenberg
"
Win32Trojaan wrote:
Oh gods, help GGG to repair shitty server!


The only way it will be fixed for us is for GGG to put the servers back in Vladivostok. let the rest of Asia use Tokyo.
"
Kellog wrote:
"
Win32Trojaan wrote:
Oh gods, help GGG to repair shitty server!


The only way it will be fixed for us is for GGG to put the servers back in Vladivostok. let the rest of Asia use Tokyo.


Please! Return as it was a week ago/ I want my ping 45 back.
Edit: Whatever, we will not have a server in Vladivostok.
Russian Heisenberg
Last edited by Win32Trojaan on Jul 16, 2019, 9:28:34 AM
"
Win32Trojaan wrote:
"
Kellog wrote:
"
Win32Trojaan wrote:
Oh gods, help GGG to repair shitty server!


The only way it will be fixed for us is for GGG to put the servers back in Vladivostok. let the rest of Asia use Tokyo.


Please! Return as it was a week ago/ I want my ping 45 back.
Edit: Whatever, we will not have a server in Vladivostok.


And next league, at least for the first half, connections will be made to google 50%+ of the time at 400ms+. Why? because half of Asia plays on the Tokyo server and they need to offload capacity.

The problem now is something different and god knows what's going on.
The game was fine until about a week or two ago. Now it is like this...

https://youtu.be/IxdvhhzKg3A

Still hoping for a solution :(
Looks like the peering at Psych Networks (the network provider for GGG) has changed. Using the Psych Networks looking glass and running an mtr from them to the Rostelecom BGP cluster in Vladivostok:

"
HOST: Looking.Glass.Tokyo Loss% Snt Last Avg Best Wrst StDev
1. 103.78.120.1 0.0% 10 1.1 1.1 1.0 1.2 0.1
2. 10.11.0.1 0.0% 10 0.4 1.9 0.3 9.7 3.2
3. 10ge1-17.core1.tyo1.he.net 0.0% 10 0.3 0.3 0.3 0.4 0.0
4. 100ge10-2.core1.hkg1.he.net 0.0% 10 53.3 53.4 53.2 54.0 0.2
5. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6. uak10-sr2.dv.ip.rostelecom.ru 0.0% 10 120.5 121.4 120.5 128.1 2.4


For some reason they're dumping traffic on to the he network and through Hong Kong instead of directly.
Looking back through the traces I saved, we are back to the point just before Psych Networks established peering with Russian Far East. Hence the elevated latency.

Perhaps GGG could tell us if this is just something temporary or whether the peering has been removed?

This is before peering was established:
"
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

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

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

| 192.168.255.254 - 0 | 500 | 500 | 0 | 0 | 1 | 0 |

| 10.251.14.123 - 0 | 500 | 500 | 3 | 7 | 11 | 8 |

| 10.251.14.120 - 0 | 501 | 501 | 2 | 3 | 13 | 2 |

| 188.254.26.51 - 0 | 500 | 500 | 127 | 127 | 167 | 128 |

| 194.68.123.187 - 0 | 500 | 500 | 131 | 131 | 171 | 131 |

| 184.105.64.105 - 1 | 493 | 491 | 148 | 148 | 184 | 148 |

| 184.105.65.29 - 0 | 500 | 500 | 150 | 154 | 384 | 150 |

| 184.105.65.34 - 0 | 501 | 501 | 157 | 158 | 194 | 158 |

| 184.105.80.14 - 0 | 500 | 500 | 165 | 166 | 204 | 165 |

| 184.105.65.13 - 0 | 500 | 500 | 208 | 210 | 254 | 209 |

| 184.105.64.254 - 0 | 501 | 501 | 201 | 201 | 239 | 201 |

| 216.218.221.14 - 0 | 501 | 501 | 201 | 201 | 238 | 201 |

| 10.22.0.2 - 0 | 500 | 500 | 201 | 201 | 235 | 202 |

| 172.107.201.54 - 0 | 500 | 500 | 201 | 201 | 241 | 201 |

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

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


This is today:

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

| WinMTR statistics |

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

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

| 192.168.255.254 - 0 | 10 | 10 | 0 | 0 | 1 | 0 |

| 10.251.14.127 - 0 | 10 | 10 | 2 | 3 | 4 | 3 |

| 10.251.14.124 - 0 | 10 | 10 | 1 | 2 | 3 | 2 |

| 217.107.67.31 - 0 | 10 | 10 | 125 | 125 | 126 | 126 |

| 194.68.123.187 - 0 | 10 | 10 | 133 | 133 | 133 | 133 |

| 184.105.64.105 - 0 | 10 | 10 | 142 | 142 | 143 | 142 |

| 184.105.65.29 - 0 | 10 | 10 | 149 | 149 | 150 | 149 |

| 184.105.65.34 - 0 | 10 | 10 | 153 | 153 | 154 | 153 |

| 184.105.80.14 - 0 | 10 | 10 | 159 | 166 | 192 | 160 |

| 184.105.65.13 - 0 | 10 | 10 | 205 | 205 | 206 | 205 |

| 184.105.64.254 - 0 | 10 | 10 | 248 | 248 | 250 | 248 |

| 216.218.221.14 - 0 | 10 | 10 | 250 | 250 | 252 | 250 |

| 10.22.0.2 - 0 | 10 | 10 | 246 | 246 | 247 | 246 |

| 172.107.201.54 - 0 | 10 | 10 | 247 | 247 | 248 | 247 |

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

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



Last edited by Kellog on Jul 17, 2019, 5:19:39 AM
Game is unplayable.
Russian Heisenberg
I'm having the provider look into this again.
What news from provider?
Russian Heisenberg

Report Forum Post

Report Account:

Report Type

Additional Info