I play from India and I play usually on EU servers in all games, because of the time window I play in, I get very long queue times on Singapore & ME servers and the matchmaking isn’t great either.
Recently, when I play on ams1 server my ping gets shot upto 500 ms mid game, when the normal ping is and should be around 160 ms.
At the start of the match it is fine at 160-170ms but all of a sudden it shoots upto 350ms-500ms and stays there. Following is the WinMTR output for when the issue exists.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 278 | 278 | 0 | 0 | 0 | 0 |
| 103.212.157.27 - 0 | 278 | 278 | 1 | 1 | 2 | 1 |
| 103.212.157.1 - 2 | 267 | 264 | 2 | 12 | 166 | 4 |
|115.113.240.105.static-delhi.vsnl.net.in - 0 | 278 | 278 | 2 | 3 | 37 | 2 |
| 172.23.183.134 - 0 | 278 | 278 | 24 | 25 | 59 | 24 |
|ix-ae-0-100.tcore1.mlv-mumbai.as6453.net - 22 | 152 | 119 | 0 | 26 | 61 | 25 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| if-ae-12-2.tcore1.l78-london.as6453.net - 58 | 85 | 36 | 0 | 154 | 156 | 154 |
| if-ae-17-2.tcore1.ldn-london.as6453.net - 27 | 138 | 102 | 0 | 148 | 150 | 149 |
| BLIZZARD-EN.edge7.Amsterdam1.Level3.net - 0 | 278 | 278 | 157 | 161 | 231 | 209 |
| 137.221.78.27 - 14 | 179 | 155 | 259 | 424 | 3958 | 444 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| 137.221.78.55 - 3 | 251 | 244 | 258 | 371 | 398 | 375 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Up until tcore hops the ping is normal (~150ms). It gets bad after the blizzard hop.
Most games and even most overwatch matches are fine but this happens randomly. And once this issue starts game connects me to Finland servers which has 220-240 ms ping for some reason (pretty much the same ping as US servers), and these Finland games will be running just fine.
Sometimes it gets so bad that it disconnects me to the login screen. While the rest of my internet is working perfectly fine, I have a ping test running in the background just to make sure there is no packet loss from my ISP’s end.
This is the WinMTR output for when there is no issue and everything is running fine on the same server IP address - 64.224.26.50.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 101 | 101 | 0 | 0 | 0 | 0 |
| 103.212.157.27 - 0 | 101 | 101 | 1 | 1 | 2 | 1 |
| 103.212.157.1 - 0 | 101 | 101 | 2 | 14 | 153 | 3 |
|115.113.240.105.static-delhi.vsnl.net.in - 0 | 101 | 101 | 2 | 3 | 22 | 2 |
| 172.23.183.134 - 0 | 101 | 101 | 24 | 24 | 43 | 24 |
|ix-ae-0-100.tcore1.mlv-mumbai.as6453.net - 7 | 82 | 77 | 24 | 25 | 47 | 24 |
| if-ae-2-2.tcore2.mlv-mumbai.as6453.net - 49 | 35 | 18 | 0 | 146 | 149 | 146 |
| if-ae-12-2.tcore1.l78-london.as6453.net - 48 | 36 | 19 | 0 | 153 | 156 | 153 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.edge7.Amsterdam1.Level3.net - 0 | 101 | 101 | 159 | 162 | 220 | 159 |
| 137.221.78.27 - 70 | 26 | 8 | 0 | 946 | 4463 | 364 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| 137.221.78.51 - 0 | 101 | 101 | 159 | 160 | 187 | 160 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
The route used through London is slightly inefficient, but based on how the submarine network cables are laid out it shouldn’t have that much of an impact (if I have to guess I would say ~5 ms of difference).
But the bigger issue is the random high ping of like 350-500 ms, which just so happens to affect after the blizzard hop.