[Oman] Getting higher ping than usual on MES1

Recently I have been getting much higher ping on mes1, the closest server to me. before I would get ~30ms while now it is ~140ms (exactly the same as cdg1, the 2nd closest). I tried asking other players that play on mes1 and they all said they experienced no such issue, and it might be a problem with how my ISP (Awasr) routes my connection.

Traceroute:

Tracing route to ec2-15-184-17-132.me-south-1.compute.amazonaws (dot) com [15.184.17.132]
over a maximum of 30 hops:

1 <1 ms 3 ms 1 ms 192.168.100.1
2 3 ms 4 ms 4 ms static-host-141-105-175-253.awasr.om [141.105.175.253]
3 4 ms 3 ms 3 ms 10.31.100.3
4 5 ms 3 ms 3 ms 134.0.218.77
5 124 ms 127 ms 124 ms 62.75.3.229
6 126 ms 127 ms 126 ms 62.75.6.185
7 127 ms 126 ms 127 ms 62.75.3.22
8 * * * Request timed out.
9 * * * Request timed out.
10 142 ms 140 ms 139 ms 52.93.38.187
11 139 ms 145 ms 138 ms 52.93.38.115
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 137 ms 137 ms 137 ms 150.222.243.59
18 137 ms 137 ms 138 ms 150.222.246.170
19 * * * Request timed out.
20 134 ms 134 ms 134 ms 54.239.46.152
21 137 ms 139 ms 136 ms 52.93.68.153
22 * * 134 ms 52.93.130.190
23 * * * Request timed out.
24 136 ms 135 ms 141 ms 52.93.224.248
25 135 ms 135 ms 143 ms 52.93.225.7
26 136 ms 136 ms 136 ms 52.93.225.6
27 133 ms 138 ms 134 ms 52.93.224.251
28 139 ms 135 ms 137 ms 52.93.227.46
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Pathping:

Tracing route to ec2-15-184-17-132.me-south-1.compute.amazonaws (dot) com [15.184.17.132]
over a maximum of 30 hops:
0 DESKTOP-31LKJFR [192.168.100.8]
1 192.168.100.1
2 static-host-141-105-175-253.awasr.om [141.105.175.253]
3 10.31.100.3
4 134.0.218.77
5 62.75.3.229
6 62.75.6.185
7 62.75.3.22
8 * * *
Computing statistics for 175 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-31LKJFR [192.168.100.8]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.100.1
0/ 100 = 0% |
2 2ms 0/ 100 = 0% 0/ 100 = 0% static-host-141-105-175-253.awasr.om [141.105.175.253]
0/ 100 = 0% |
3 2ms 0/ 100 = 0% 0/ 100 = 0% 10.31.100.3
0/ 100 = 0% |
4 4ms 0/ 100 = 0% 0/ 100 = 0% 134.0.218.77
0/ 100 = 0% |
5 122ms 0/ 100 = 0% 0/ 100 = 0% 62.75.3.229
100/ 100 =100% |
6 — 100/ 100 =100% 0/ 100 = 0% 62.75.6.185
0/ 100 = 0% |
7 — 100/ 100 =100% 0/ 100 = 0% 62.75.3.22

Trace complete.

MTR:

Start: Fri Aug 7 06:48:27 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 37.244.24.130 0.0% 10 0.5 1.1 0.5 4.3 1.1
3.|-- Blizzard 0.0% 10 1.1 2.0 1.0 9.3 2.5
4.|-- 137.221.66.40 0.0% 10 0.6 0.8 0.6 1.5 0.0
5.|-- 137.221.78.74 0.0% 10 1.0 2.6 1.0 15.9 4.6
6.|-- 137.221.78.32 0.0% 10 32.6 4.6 1.2 32.6 9.9
7.|-- 80.249.208.30 0.0% 10 1.0 2.7 0.9 11.4 3.7
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 134.0.217.233 0.0% 10 131.1 130.4 130.1 131.2 0.0
12.|-- 134.0.218.78 0.0% 10 127.6 128.0 127.4 131.0 0.9
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- static-host-161-8-102-204.awasr.om 0.0% 10 131.6 131.9 131.6 132.1 0.0

07/08/2020 06:48:27 UTC

MTR:
Start: Fri Aug 7 06:48:27 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.6 0.4 0.2 0.6 0.0
2.|-- 37.244.25.130 0.0% 10 0.8 0.8 0.6 1.3 0.0
3.|-- Blizzard 0.0% 10 0.9 1.0 0.8 1.3 0.0
4.|-- 137.221.66.32 0.0% 10 1.5 1.1 0.8 1.5 0.0
5.|-- 137.221.77.70 0.0% 10 9.9 74.2 9.8 414.0 137.7
6.|-- 137.221.65.93 70.0% 10 12670 12730 12670 12764 52.3
7.|-- 137.221.78.34 0.0% 10 10.4 10.1 9.9 10.4 0.0
8.|-- 80.249.208.30 0.0% 10 9.8 11.3 9.8 23.1 4.1
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 134.0.217.233 0.0% 10 136.8 136.9 136.7 137.3 0.0
13.|-- 134.0.218.78 0.0% 10 144.9 145.2 144.8 147.6 0.7
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- static-host-161-8-102-204.awasr.om 0.0% 10 138.5 138.6 138.0 138.8 0.0

07/08/2020 06:48:27 UTC

The ping from Blizzard looks good in your tests, but once it reaches your ISP’s network, it climbs to 138-147ms. Ideally, you need to use a WinMTR to confirm this, since the looking glass only pings the login server for the game.

thanks for the quick response, here are the WinMTR results:

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

| WinMTR statistics |

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

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

| 192.168.100.1 - 0 | 551 | 551 | 0 | 1 | 14 | 2 |

| static-host-141-105-175-253.awasr.om - 0 | 551 | 551 | 1 | 2 | 28 | 3 |

| 10.31.100.3 - 0 | 551 | 551 | 2 | 3 | 18 | 3 |

| 134.0.218.77 - 0 | 551 | 551 | 1 | 3 | 13 | 3 |

| 62.75.3.229 - 0 | 551 | 551 | 122 | 123 | 131 | 123 |

| 62.75.6.185 - 0 | 551 | 551 | 124 | 125 | 134 | 127 |

| 62.75.3.22 - 0 | 551 | 551 | 124 | 126 | 155 | 124 |

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

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

| 52.93.38.187 - 1 | 547 | 546 | 137 | 139 | 155 | 141 |

| 52.93.38.115 - 0 | 551 | 551 | 137 | 139 | 158 | 141 |

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

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

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

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

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

| 150.222.243.59 - 0 | 551 | 551 | 135 | 137 | 155 | 136 |

| 150.222.246.170 - 0 | 551 | 551 | 135 | 137 | 152 | 137 |

| 150.222.246.195 - 91 | 120 | 11 | 0 | 135 | 147 | 133 |

| 54.239.46.152 - 0 | 551 | 551 | 131 | 133 | 206 | 133 |

| 52.93.68.153 - 0 | 551 | 551 | 134 | 136 | 154 | 137 |

| 52.93.130.190 - 13 | 368 | 322 | 131 | 133 | 147 | 137 |

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

| 52.93.224.248 - 0 | 551 | 551 | 133 | 136 | 153 | 139 |

| 52.93.225.7 - 0 | 551 | 551 | 133 | 136 | 161 | 136 |

| 52.93.225.6 - 0 | 551 | 551 | 134 | 137 | 152 | 140 |

| 52.93.224.251 - 0 | 551 | 551 | 131 | 133 | 170 | 133 |

| 52.93.227.46 - 0 | 551 | 551 | 133 | 135 | 157 | 139 |

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

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

|____________|||||||

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

This test is much longer than expected. This could be an issue with your ISP’s peering partner, but it’s hard to tell. Can you run the WinMTR to 15.185.37.198?

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

| WinMTR statistics |

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

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

| 192.168.100.1 - 0 | 253 | 253 | 0 | 1 | 8 | 1 |

| static-host-141-105-175-253.awasr.om - 0 | 253 | 253 | 1 | 2 | 12 | 1 |

| 10.31.100.3 - 0 | 253 | 253 | 2 | 3 | 10 | 3 |

| 134.0.218.77 - 0 | 253 | 253 | 1 | 3 | 11 | 6 |

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

| 134.0.220.73 - 0 | 253 | 253 | 13 | 15 | 47 | 13 |

| 213.202.5.211 - 0 | 253 | 253 | 14 | 17 | 51 | 15 |

| 150.222.210.69 - 0 | 253 | 253 | 15 | 18 | 30 | 18 |

| 52.93.68.129 - 0 | 253 | 253 | 14 | 15 | 25 | 15 |

| 52.93.130.192 - 5 | 213 | 203 | 21 | 24 | 39 | 23 |

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

| 52.93.224.142 - 0 | 253 | 253 | 23 | 25 | 39 | 35 |

| 52.93.224.155 - 0 | 253 | 253 | 22 | 24 | 44 | 22 |

| 52.93.225.0 - 0 | 253 | 253 | 21 | 23 | 36 | 22 |

| 52.93.224.247 - 0 | 253 | 253 | 21 | 26 | 41 | 23 |

| 52.93.227.201 - 0 | 253 | 253 | 22 | 25 | 42 | 25 |

| 52.93.226.152 - 19 | 145 | 118 | 21 | 22 | 37 | 22 |

| 52.93.226.159 - 19 | 145 | 118 | 23 | 24 | 34 | 24 |

| 52.93.227.74 - 19 | 145 | 118 | 21 | 23 | 34 | 24 |

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

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

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

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

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

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

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

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

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

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

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

|____________|||||||

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

I’m on US-E and getting significantly more ping than usual, plus lots of dropped packets

I got placed in a US-W game earlier and ping was normal and no packet loss.

Heya PepegaAim,

We’ve actually seen an increase of latency from Oman, where you’re located. Thanks for the report and sending in that winMTR. I’m changing the title of this thread to try to centralize reports here. If we see anybody else from Oman having this problem, can you please direct them here to create tests for us?

For anybody else in Oman who has suddenly higher latency, here’s how to create that test. If you’re still having this problem, please create a WinMTR test which catches a disconnection. You want to restart the test every 10-15 minutes until you catch one of these problems. Once you’ve caught one red handed, run the test for about 5 more minutes. This will let us look for problems between your house and our servers which may cause this.

If you have problems with posting it due to a link error, go ahead and copy paste this into your next post, and replace “WinMTR goes here” with your test.

~~~~
WinMTR goes here
~~~~