When I am on Mal’ganis, I have variable server and home latency (anywhere from 200ms - 500 ms). However when I am on a server like Hyjal, it is fine (40ms).
Any clue as to why this is happening? I have Cox Internet in Los Angeles, CA.
When I am on Mal’ganis, I have variable server and home latency (anywhere from 200ms - 500 ms). However when I am on a server like Hyjal, it is fine (40ms).
Any clue as to why this is happening? I have Cox Internet in Los Angeles, CA.
Hey Ademuro,
Sounds like there might be some routing issues between your ISP and the Mal’ganis server. Mal’ganis server is US Central (Chicago) while Hyjal is US West (Las Vegas), so the internet path to those servers is going to be different.
Can you run a WinMTR to the Central data center so we can see if the problem shows up?
- Download WinMTR
- Right-click on the downloaded .zip folder and select “Extract All”, to extract the files to a new folder.
- Open the new folder that was created, then open the WinMTR_x64 folder.
- Right-click on the WinMTR application and select “Run as administrator”.
- Type the IP address 24.105.62.129 in the “Host” field.
- Click on “Start” and then launch the game. Allow the test to run for at least 10 -30 minutes. Click on “Stop” when you’re done playing after you have experienced the latency or connection issue.
- Click on “Copy Text to Clipboard”, paste the results here, then highlight everything and hit the </> button in the posting section so it will allow links.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 8879 | 8879 | 0 | 0 | 133 | 0 |
| 10.76.224.1 - 1 | 8616 | 8546 | 3 | 32 | 425 | 68 |
| 100.120.104.74 - 1 | 8584 | 8506 | 4 | 33 | 354 | 86 |
| 100.120.104.22 - 1 | 8607 | 8535 | 6 | 37 | 365 | 87 |
| langbprj01-ae1.rd.la.cox.net - 2 | 8485 | 8381 | 8 | 38 | 369 | 72 |
| 68.105.30.130 - 1 | 8582 | 8504 | 8 | 41 | 359 | 89 |
| ae1-br01-eqla1.as57976.net - 2 | 8507 | 8414 | 57 | 242 | 3351 | 343 |
| No response from host - 100 | 1790 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1790 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe01-eqch2.as57976.net - 1 | 8598 | 8524 | 50 | 82 | 405 | 131 |
| 24.105.62.129 - 1 | 8597 | 8522 | 51 | 80 | 400 | 116 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I’m also having spontaneous high world ms on Proudmoore-US. Relogging helps for a moment, but it comes right back. This is highly irregular for me so I suspect it’s a server side issue?
In raid instance is going south because of latency, Blizzard looking Glass included. US Sen’jin
TRACEROUTE:
traceroute to 108.24.154.83 (108.24.154.83), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.873 ms 0.847 ms 0.845 ms
2 24.105.18.2 (24.105.18.2) 3.582 ms 3.593 ms 3.594 ms
3 137.221.105.10 (137.221.105.10) 3.590 ms 3.588 ms 3.588 ms
4 137.221.66.16 (137.221.66.16) 3.497 ms 3.515 ms 3.516 ms
5 137.221.83.80 (137.221.83.80) 1307.505 ms 1307.636 ms 1528.472 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.878 ms 7.284 ms 7.334 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 6.462 ms 5.704 ms 5.686 ms
9 ae-2-3601.edge7.LosAngeles1.Level3.net (4.69.219.45) 18.382 ms 15.458 ms 15.403 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 7.109 ms 7.068 ms 7.068 ms
11 ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net (130.81.221.139) 66.185 ms 66.217 ms 66.228 ms
12 * * *
13 * * *
14 * * *
15 * * *
TRACEROUTE:
traceroute to 108.24.154.83 (108.24.154.83), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.291 ms 1.302 ms 1.316 ms
2 24.105.18.2 (24.105.18.2) 1.465 ms 3.908 ms 3.975 ms
3 137.221.105.10 (137.221.105.10) 4.112 ms 4.123 ms 4.136 ms
4 137.221.66.16 (137.221.66.16) 1.302 ms 1.340 ms 1.373 ms
5 137.221.83.80 (137.221.83.80) 1365.119 ms 1365.153 ms 1583.324 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.040 ms 6.503 ms 6.529 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.596 ms 5.885 ms 5.874 ms
9 ae-2-3601.edge7.LosAngeles1.Level3.net (4.69.219.45) 6.280 ms 6.560 ms 6.919 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 6.171 ms 5.862 ms 5.728 ms
11 ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net (130.81.221.139) 64.949 ms 65.035 ms 65.303 ms
12 * * *
13 * * *
14 * * *
15 * * *
PING:
PING 108.24.154.83 (108.24.154.83) 56(84) bytes of data.
— 108.24.154.83 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
PING:
PING 108.24.154.83 (108.24.154.83) 56(84) bytes of data.
— 108.24.154.83 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
TRACEROUTE:
traceroute to 108.24.154.83 (108.24.154.83), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.531 ms 0.543 ms 0.570 ms
2 24.105.18.2 (24.105.18.2) 1.810 ms 1.874 ms 1.888 ms
3 137.221.105.10 (137.221.105.10) 1.904 ms 1.916 ms 1.933 ms
4 137.221.66.16 (137.221.66.16) 20.282 ms 20.316 ms 20.526 ms
5 137.221.83.80 (137.221.83.80) 621.990 ms 622.084 ms 855.965 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.939 ms 6.113 ms 6.103 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.562 ms 5.497 ms 5.478 ms
9 ae-2-3601.edge7.LosAngeles1.Level3.net (4.69.219.45) 5.884 ms 5.766 ms 5.803 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 5.915 ms 5.931 ms 6.078 ms
11 ae204-0.CMDNNJ-VFTTP-303.verizon-gni.net (130.81.221.137) 63.211 ms 62.889 ms 62.589 ms
12 * * *
13 * * *
14 * * *
15 * * *
PING:
PING 108.24.154.83 (108.24.154.83) 56(84) bytes of data.
— 108.24.154.83 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2997ms
TRACEROUTE:
traceroute to 108.24.154.83 (108.24.154.83), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.381 ms 0.288 ms 0.212 ms
2 37.244.23.131 (37.244.23.131) 0.458 ms 0.542 ms 0.552 ms
3 24.105.62.152 (24.105.62.152) 0.848 ms 0.857 ms 0.919 ms
4 137.221.66.10 (137.221.66.10) 1.956 ms 1.969 ms 1.970 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 2.520 ms 2.612 ms 2.590 ms
7 7-1-4.ear7.Chicago2.Level3.net (4.7.196.133) 1.950 ms 2.139 ms 2.122 ms
8 ae-1-3510.edge1.Chicago10.Level3.net (4.69.219.14) 2.641 ms 11.265 ms 11.248 ms
9 Verizon-level3-Chicago10.Level3.net (4.68.37.186) 4.376 ms 2.960 ms 2.956 ms
10 ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net (130.81.221.139) 24.058 ms 24.090 ms 24.100 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
PING:
PING 108.24.154.83 (108.24.154.83) 56(84) bytes of data.
— 108.24.154.83 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
MTR:
Start: Thu Feb 25 05:35:41 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.7 0.8 0.3 1.6 0.0
2.|-- 24.105.18.2 0.0% 10 0.9 1.0 0.5 1.3 0.0
3.|-- 137.221.105.10 0.0% 10 1.1 1.3 0.9 1.6 0.0
4.|-- 137.221.66.16 0.0% 10 0.9 7.2 0.6 63.8 19.9
5.|-- 137.221.83.80 0.0% 10 48.1 772.7 48.1 1480. 453.7
6.|-- 137.221.65.68 90.0% 10 14404 14404 14404 14404 0.0
7.|-- 137.221.68.32 0.0% 10 6.8 18.4 6.2 68.7 19.9
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.6 5.8 5.6 6.4 0.0
9.|-- ae-2-3601.edge7.LosAngeles1.Level3.net 0.0% 10 6.9 7.3 5.9 15.0 2.7
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 6.1 6.9 5.9 13.8 2.4
11.|-- ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net 0.0% 10 62.6 63.8 62.5 67.8 1.7
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
MTR:
Start: Thu Feb 25 05:35:42 2021 Blizzard 1.|-- Blizzard 0.0% 10 1.0 0.7 0.3 1.0 0.0
2.|-- 24.105.18.2 0.0% 10 0.9 0.9 0.6 1.5 0.0
3.|-- 137.221.105.10 0.0% 10 1.0 1.2 0.8 1.7 0.0
4.|-- 137.221.66.16 0.0% 10 1.0 3.3 0.6 22.1 6.7
5.|-- 137.221.83.80 0.0% 10 1319. 864.5 230.6 1379. 422.1
6.|-- 137.221.65.68 90.0% 10 14304 14304 14304 14304 0.0
7.|-- 137.221.68.32 0.0% 10 46.1 17.1 6.0 46.1 14.4
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.6 5.9 5.6 6.4 0.0
9.|-- ae-2-3601.edge7.LosAngeles1.Level3.net 0.0% 10 18.1 11.3 6.2 18.1 3.5
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 6.0 7.5 6.0 17.8 3.6
11.|-- ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net 0.0% 10 62.5 63.3 62.5 65.3 0.7
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
MTR:
Start: Thu Feb 25 05:35:45 2021 Blizzard 1.|-- Blizzard 0.0% 10 1.0 0.7 0.3 1.1 0.0
2.|-- 24.105.18.2 0.0% 10 1.0 0.9 0.6 1.4 0.0
3.|-- 137.221.105.10 0.0% 10 1.1 1.1 0.9 1.4 0.0
4.|-- 137.221.66.16 0.0% 10 62.2 7.0 0.4 62.2 19.4
5.|-- 137.221.83.80 0.0% 10 1256. 820.9 178.1 1409. 390.4
6.|-- 137.221.65.68 90.0% 10 14677 14677 14677 14677 0.0
7.|-- 137.221.68.32 0.0% 10 6.3 6.3 5.9 7.1 0.0
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.7 5.7 5.5 6.1 0.0
9.|-- ae-2-3601.edge7.LosAngeles1.Level3.net 0.0% 10 19.6 9.2 6.0 19.6 4.8
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 6.0 6.3 5.9 7.0 0.0
11.|-- ae204-0.CMDNNJ-VFTTP-303.verizon-gni.net 0.0% 10 62.5 62.5 62.4 62.7 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
TRACEROUTE:
traceroute to 108.24.154.83 (108.24.154.83), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.539 ms 0.539 ms 0.538 ms
2 37.244.23.131 (37.244.23.131) 0.730 ms 0.823 ms 0.904 ms
3 24.105.62.152 (24.105.62.152) 1.171 ms 1.193 ms 1.254 ms
4 137.221.66.10 (137.221.66.10) 2.080 ms 2.083 ms 2.084 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 2.854 ms 2.386 ms 2.880 ms
7 7-1-4.ear7.Chicago2.Level3.net (4.7.196.133) 2.112 ms 2.230 ms 2.272 ms
8 ae-1-3510.edge1.Chicago10.Level3.net (4.69.219.14) 2.740 ms 4.324 ms 4.265 ms
9 Verizon-level3-Chicago10.Level3.net (4.68.37.186) 3.342 ms 2.841 ms 2.833 ms
10 ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net (130.81.221.139) 23.923 ms 23.940 ms 23.943 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
MTR:
Start: Thu Feb 25 05:35:47 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 37.244.23.131 0.0% 10 0.5 0.5 0.4 0.6 0.0
3.|-- 24.105.62.152 0.0% 10 0.8 0.9 0.8 1.2 0.0
4.|-- 137.221.66.10 0.0% 10 2.0 4.5 1.8 27.9 8.2
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 2.3 5.3 2.3 30.5 8.8
7.|-- 7-1-4.ear7.Chicago2.Level3.net 0.0% 10 1.9 2.0 1.9 2.2 0.0
8.|-- ae-1-3510.edge1.Chicago10.Level3.net 0.0% 10 10.2 4.8 2.5 10.2 2.9
9.|-- Verizon-level3-Chicago10.Level3.net 0.0% 10 2.9 4.4 2.7 18.6 4.9
10.|-- ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net 0.0% 10 24.1 24.1 23.8 26.3 0.5
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
PING:
PING 108.24.154.83 (108.24.154.83) 56(84) bytes of data.
— 108.24.154.83 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
TRACEROUTE:
traceroute to 108.24.154.83 (108.24.154.83), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.342 ms 0.356 ms 0.367 ms
2 37.244.23.131 (37.244.23.131) 0.563 ms 0.735 ms 0.770 ms
3 24.105.62.152 (24.105.62.152) 1.596 ms 1.628 ms 1.639 ms
4 137.221.66.10 (137.221.66.10) 1.918 ms 1.945 ms 1.954 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 2.463 ms 2.528 ms 2.522 ms
7 7-1-4.ear7.Chicago2.Level3.net (4.7.196.133) 1.903 ms 1.993 ms 1.979 ms
8 ae-1-3510.edge1.Chicago10.Level3.net (4.69.219.14) 5.775 ms 4.984 ms 4.911 ms
9 Verizon-level3-Chicago10.Level3.net (4.68.37.186) 3.102 ms 2.867 ms 2.864 ms
10 ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net (130.81.221.139) 23.924 ms 23.944 ms 23.940 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
PING:
PING 108.24.154.83 (108.24.154.83) 56(84) bytes of data.
— 108.24.154.83 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3011ms
MTR:
Start: Thu Feb 25 05:35:52 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 0.7 0.0
2.|-- 37.244.23.131 0.0% 10 0.4 0.6 0.4 0.7 0.0
3.|-- 24.105.62.152 0.0% 10 0.7 0.9 0.7 1.2 0.0
4.|-- 137.221.66.10 0.0% 10 1.9 7.2 1.8 54.0 16.4
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 3.2 9.8 2.4 29.5 10.6
7.|-- 7-1-4.ear7.Chicago2.Level3.net 0.0% 10 1.9 2.0 1.9 2.1 0.0
8.|-- ae-1-3510.edge1.Chicago10.Level3.net 0.0% 10 3.0 4.9 2.6 11.8 3.1
9.|-- Verizon-level3-Chicago10.Level3.net 0.0% 10 4.6 4.1 2.8 12.3 2.9
10.|-- ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net 0.0% 10 25.2 24.1 23.8 25.2 0.3
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
MTR:
Start: Thu Feb 25 05:35:58 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.3 1.6 0.0
2.|-- 37.244.23.131 0.0% 10 0.5 0.7 0.5 1.9 0.0
3.|-- 24.105.62.152 0.0% 10 1.0 0.9 0.8 1.1 0.0
4.|-- 137.221.66.10 0.0% 10 1.8 2.2 1.8 5.2 1.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 8.7 13.3 2.3 49.7 16.8
7.|-- 7-1-4.ear7.Chicago2.Level3.net 0.0% 10 2.2 3.1 2.0 12.7 3.3
8.|-- ae-1-3510.edge1.Chicago10.Level3.net 0.0% 10 3.8 5.5 2.5 12.2 3.2
9.|-- Verizon-level3-Chicago10.Level3.net 0.0% 10 2.8 2.9 2.8 3.1 0.0
10.|-- ae203-0.CMDNNJ-VFTTP-303.verizon-gni.net 0.0% 10 25.9 24.2 23.9 25.9 0.6
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
Las Vegas or Los Angeles? almost 14 years playing and never heard of Las Vegas having WoW realms in a data center there.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 362 | 362 | 0 | 0 | 12 | 0 |
| 10.76.224.1 - 10 | 265 | 239 | 0 | 46 | 320 | 84 |
| 100.120.104.72 - 10 | 265 | 239 | 0 | 48 | 320 | 85 |
| 100.120.104.20 - 10 | 265 | 239 | 0 | 49 | 321 | 86 |
| langbprj01-ae1.rd.la.cox.net - 10 | 265 | 239 | 0 | 52 | 398 | 88 |
| 68.105.30.130 - 10 | 265 | 239 | 0 | 54 | 325 | 88 |
| ae1-br01-eqla1.as57976.net - 10 | 265 | 239 | 0 | 255 | 1178 | 228 |
| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe01-eqch2.as57976.net - 10 | 265 | 239 | 0 | 95 | 369 | 138 |
| 24.105.62.129 - 10 | 265 | 239 | 0 | 93 | 369 | 136 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I disconnected during this session.
There’s packet loss happening on all of the ISP nodes. The original 362 packets the computer sent out never made it to Blizzard.
So that’s related to my ISP then correct?
That is correct.
Thank you!