Hello Blizzard,
I’ve been experiencing high latency and absurd lag spikes for over a month, getting to the point where I can’t even do basic quests. At certain times, it’s not even possible with a VPN. I’ve posted several times on the forum in my region, but I have absolutely NO response from the company to help me. I’ve noticed that it’s not just me facing this problem. I have already contacted my ISP and they told me that nothing was wrong with my connection. I have nowhere else to turn, as there is no response or assistance from Blizzard technical support in my region.
Let’s start with a winmtr to the server you play on
- Download WinMTR
- Extract the contents of the .zip file to your desktop.
- Open the WinMTR folder, then open the folder that matches your version of Windows (32-bit or 64-bit) and run WinMTR.exe.
- Enter the IP address you want to test in the Host field. Select a game from the dropdown below for a list of IP addresses.
5.Note: If multiple IPs are listed, run a WinMTR test for each IP address.* - Click Start, then launch the game you’re testing. If no connection issue is found in the first 5 minutes, restart the test.
- When a connection error occurs, play for at least 5 more minutes, then click Stop in WinMTR.
- Click “Export Text” and save the .txt file to your desktop. Name this file WinMTR.
- Open above file copy and paste to this thread
Hello Northernlite,
Thanks for replying.
I Have a little colletction here, with WinMtr an PingPloter results
Target Name: (US Central)
IP: 24.105.62.129
Date/Time: 01/01/2024 15:49:55 - 01/01/2024 15:59:55
Hop Sent PL% Min Max Avg Host Name / [IP]
1 10 0 0,31 1,61 0,54 MyRouter [192.168.1.1]
2 10 0 4,50 12,50 7,62 186-230-220-107.ded.intelignet.com.br [186.230.220.107]
3 10 0 4,69 8,04 5,93 10.221.252.34 [10.221.252.34]
4 10 0 3,92 12,31 5,24 10.223.238.246 [10.223.238.246]
5 10 0 3,34 14,73 6,57 5.178.44.38 [5.178.44.38]
6 10 100 0 0 0 [-]
7 10 0 104,51 112,13 106,39 “blizzard.miami15.mia.seabone . net” [89.221.41.3]
8 10 20 148,26 327,95 294,58 “ae1-br01-eqmi2.as57976 . net” [137.221.76.33]
9 10 0 147,30 391,27 304,52 “xe-0-0-0-1-br01-eqat2.as57976 . net” [137.221.65.50]
10 10 100 0 0 0 [-]
11 10 0 186,41 352,44 278,83 137.221.69.87 [137.221.69.87]
12 10 0 200,33 341,55 280,76 137.221.67.65 [137.221.67.65]
13 10 0 136,95 341,61 260,87 (US Central) [24.105.62.129]
Target Name: (US Central)
IP: 24.105.62.129
Date/Time: 03/01/2024 21:00:20 - 03/01/2024 21:10:20
Hop Sent PL% Min Max Avg Host Name / [IP]
1 239 0 0,30 17,61 0,73 MyRouter [192.168.1.1]
2 239 0 1,00 32,67 7,88 186-230-220-107.ded.intelignet.com.br [186.230.220.107]
3 239 0 4,00 25,26 6,09 10.221.252.34 [10.221.252.34]
4 239 0 3,00 105,15 11,46 10.223.238.246 [10.223.238.246]
5 239 0 2,00 33,67 4,51 5.178.44.38 [5.178.44.38]
6 239 100 0 0 0 [-]
7 239 0 103,03 160,54 108,01 blizzard.miami15.mia.seabone. net [89.221.41.3]
8 239 2 135,27 376,06 261,36 ae1-br01-eqmi2.as57976. net [137.221.76.33]
9 239 5 138,04 379,30 251,64 xe-0-0-0-1-br01-eqat2.as57976. net [137.221.65.50]
10 239 100 0 0 0 [-]
11 239 1 136,00 373,52 263,60 137.221.69.87 [137.221.69.87]
12 239 9 137,65 353,31 244,77 137.221.67.65 [137.221.67.65]
13 239 0 135,00 354,24 261,97 (US Central) [24.105.62.129]
Target Name: (US Central)
IP: 24.105.62.129
Date/Time: 04/01/2024 17:30:03 - 04/01/2024 17:31:03
Hop Sent PL% Min Max Avg Host Name / [IP]
1 23 0 0,34 1,50 0,49 MyRouter [192.168.1.1]
2 23 0 4,04 26,73 7,85 186-230-220-107.ded.intelignet.com.br [186.230.220.107]
3 23 0 4,41 23,33 6,50 10.221.252.20 [10.221.252.20]
4 23 0 3,97 93,62 10,95 10.223.238.244 [10.223.238.244]
5 23 35 3,67 6,06 4,38 213.144.160.100 [213.144.160.100]
6 23 0 130,01 158,28 133,25 195.22.199.179 [195.22.199.179]
7 23 0 130,67 212,10 136,04 89.221.41.3 [89.221.41.3]
8 23 0 162,81 186,87 165,56 ae1-br01-eqmi2.as57976 .net [137.221.76.33]
9 23 0 162,39 196,26 166,15 xe-0-0-0-1-br01-eqat2.as57976. net [137.221.65.50]
10 23 100 0 0 0 [-]
11 23 0 162,91 181,59 164,34 137.221.69.85 [137.221.69.85]
12 23 0 162,88 167,09 163,49 (US Central) [24.105.62.129]
Target Name: (US Central)
IP: 24.105.62.129
Date/Time: 05/01/2024 22:01:13 - 05/01/2024 22:11:13
Hop Sent PL% Min Max Avg Host Name / [IP]
1 23 48 0,28 0,44 0,35 MyRouter [192.168.1.1]
2 24 0 3,56 15,85 8,57 186-230-220-107.ded.intelignet.com.br [186.230.220.107]
3 24 0 4,04 12,86 6,85 10.221.252.20 [10.221.252.20]
4 24 0 3,73 93,35 14,05 10.223.238.244 [10.223.238.244]
5 24 25 3,23 18,36 5,82 213.144.160.100 [213.144.160.100]
6 24 0 129,81 136,38 131,14 195.22.199.179 [195.22.199.179]
7 24 0 130,32 192,81 135,08 89.221.41.3 [89.221.41.3]
8 24 8 162,58 369,73 198,24 ae1-br01-eqmi2.as57976. net [137.221.76.33]
9 24 0 160,77 379,16 218,87 xe-0-0-0-1-br01-eqat2.as57976. net [137.221.65.50]
10 24 100 0 0 0 [-]
11 24 8 162,16 377,13 196,21 137.221.69.85 [137.221.69.85]
12 24 0 161,83 383,99 216,60 (US Central) [24.105.62.129]
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|---|
MyRouter | 0 | 268 | 268 | 0 | 0 | 12 | 0 |
186-230-220-107.ded.intelignet.com.br | 0 | 268 | 268 | 4 | 8 | 33 | 5 |
10.221.252.20 | 0 | 268 | 268 | 4 | 7 | 24 | 6 |
10.223.238.244 | 0 | 268 | 268 | 3 | 18 | 153 | 7 |
213.144.160.100 | 21 | 148 | 117 | 0 | 6 | 83 | 5 |
195.22.199.179 | 0 | 268 | 268 | 128 | 133 | 194 | 131 |
89.221.41.3 | 1 | 260 | 258 | 130 | 135 | 192 | 131 |
ae1-br01-eqmi2.as57976. net | 11 | 188 | 168 | 0 | 182 | 384 | 376 |
xe-0-0-0-1-br01-eqat2.as57976. net | 11 | 186 | 166 | 163 | 180 | 403 | 358 |
No response from host | 100 | 54 | 0 | 0 | 0 | 0 | 0 |
137.221.69.85 | 12 | 186 | 165 | 0 | 179 | 393 | 374 |
24.105.62.129 | 12 | 183 | 162 | 162 | 179 | 395 | 374 |
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
MyRouter | 0 | 40 | 40 | 0 | 0 | 12 | 0 |
186-230-220-107.ded.intelignet.com.br | 0 | 40 | 40 | 3 | 13 | 28 | 28 |
10.221.252.20 | 0 | 40 | 40 | 2 | 12 | 23 | 14 |
10.223.238.244 | 0 | 40 | 40 | 2 | 10 | 21 | 11 |
213.144.160.100 | 32 | 16 | 11 | 0 | 8 | 18 | 18 |
89.221.41.177 | 0 | 40 | 40 | 128 | 135 | 146 | 134 |
89.221.41.3 | 0 | 40 | 40 | 125 | 139 | 169 | 136 |
ae1-br01-eqmi2.as57976.net | 0 | 40 | 40 | 159 | 167 | 179 | 163 |
xe-0-0-0-1-br01-eqat2.as57976.net | 0 | 40 | 40 | 161 | 169 | 187 | 161 |
No response from host | 100 | 8 | 0 | 0 | 0 | 0 | 0 |
137.221.69.85 | 0 | 40 | 40 | 160 | 167 | 183 | 162 |
24.105.62.129 | 0 | 40 | 40 | 159 | 167 | 178 | 161 |
I tried with Hotspot too and this was the result:
WinMTR StatisticsWinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.178.192 | 0 | 34 | 34 | 1 | 2 | 4 | 2 |
No response from host | 100 | 6 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 6 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 6 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 6 | 0 | 0 | 0 | 0 | 0 |
213.144.160.100 | 36 | 14 | 9 | 0 | 26 | 41 | 19 |
No response from host | 100 | 6 | 0 | 0 | 0 | 0 | 0 |
89.221.41.3 | 0 | 34 | 34 | 117 | 143 | 227 | 120 |
ae1-br01-eqmi2.as57976.net | 0 | 34 | 34 | 149 | 168 | 217 | 151 |
xe-0-0-0-1-br01-eqat2.as57976.net | 0 | 34 | 34 | 150 | 167 | 217 | 151 |
No response from host | 100 | 6 | 0 | 0 | 0 | 0 | 0 |
137.221.69.85 | 0 | 34 | 34 | 147 | 167 | 226 | 147 |
24.105.62.129 | 0 | 34 | 34 | 149 | 167 | 217 | 156 |
Looks like you are getting spikes starting at this node which is a local node for your ISP. That would also explain why a VPN does not help. The issue is to close to you for a VPN to route around
Hello, thanks for your answer, I’m having connection issues for weeks (I think for one month, since 10.2 launch)
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
[My IP] | 0 | 469 | 469 | 0 | 0 | 6 | 0 |
186-230-207-108.ded.intelignet.com.br | 0 | 468 | 468 | 2 | 2 | 12 | 2 |
10.230.82.31 | 0 | 468 | 468 | 17 | 18 | 23 | 18 |
10.230.1.159 | 0 | 468 | 468 | 19 | 21 | 29 | 21 |
10.224.150.189 | 0 | 468 | 468 | 18 | 20 | 41 | 21 |
10.239.253.33 | 0 | 468 | 468 | 18 | 21 | 100 | 20 |
10.223.255.114 | 0 | 468 | 468 | 18 | 23 | 103 | 19 |
10.213.247.30 | 0 | 468 | 468 | 18 | 20 | 106 | 22 |
195.22.219.32 | 3 | 434 | 425 | 19 | 20 | 58 | 20 |
89.221.41.177 | 3 | 429 | 419 | 123 | 129 | 267 | 127 |
89.221.41.3 | 3 | 433 | 424 | 124 | 135 | 374 | 125 |
ae1-br01-eqmi2.as57976.net | 18 | 276 | 227 | 151 | 212 | 430 | 152 |
xe-0-0-0-1-br01-eqat2.as57976.net | 5 | 402 | 385 | 151 | 251 | 457 | 152 |
No response from host | 100 | 95 | 0 | 0 | 0 | 0 | 0 |
137.221.69.87 | 18 | 280 | 232 | 151 | 211 | 365 | 152 |
137.221.67.65 | 18 | 275 | 226 | 151 | 209 | 366 | 152 |
24.105.62.129 | 4 | 410 | 395 | 150 | 255 | 376 | 152 |
I did some trace route earlier
Rastreando a rota para 24.105.62.129 com no m ximo 30 saltos
1 <1 ms <1 ms <1 ms [My IP]
2 3 ms 2 ms 2 ms 186-230-207-108.ded.intelignet.com.br [186.230.207.108]
3 19 ms 18 ms 18 ms 10.230.82.31
4 19 ms 20 ms 19 ms 10.230.1.159
5 20 ms 19 ms 20 ms 10.224.150.189
6 18 ms 18 ms 18 ms 10.239.253.33
7 19 ms 19 ms 19 ms 10.213.247.38
8 * * * Esgotado o tempo limite do pedido.
9 127 ms 130 ms 123 ms 89.221.41.175
10 151 ms 125 ms 125 ms 89.221.41.3
11 336 ms 349 ms 352 ms ae1-br01-eqmi2.as57976.net [137.221.76.33]
12 340 ms 337 ms 348 ms xe-0-0-0-1-br01-eqat2.as57976.net [137.221.65.50]
13 * * * Esgotado o tempo limite do pedido.
14 348 ms 344 ms * 137.221.69.87
15 * 361 ms * 137.221.67.65
16 352 ms 364 ms 343 ms 24.105.62.129
Rastreamento conclu¡do.
So the solution will be to stop playing, because my ISP informs me that everything is ok and there is nothing they can do.
VPN doesn’t work…
I can’t take this frustration anymore! A progression game, where I can’t play due to internet problems!
I’ll try to have fun in any game that isn’t Blizz!
Not sure what type of connection you have but have you tried having your ISP replace your modem/Router?
1Gb/s Fiber.
I can try this replace with my ISP, but would that solve the route issue?
It could help the issues down stream. A modem should always ping zero or 1 you are getting some spikes starting there it could not hurt.
while you have some minor issues before this you are getting some very high latency spikes at this point.
Unplayable !!!
Target Name: (US Central)
IP: 24.105.62.129
Date/Time: 06/01/2024 22:04:00 - 06/01/2024 22:14:00
Hop Sent PL% Min Max Avg Host Name / [IP]
1 239 0 0,30 11,91 0,65 MyRouter [192.168.1.1]
2 239 0 3,00 37,16 7,80 186-230-220-107.ded.intelignet.com.br [186.230.220.107]
3 239 0 3,47 34,75 6,81 10.221.252.34 [10.221.252.34]
4 239 0 3,00 88,04 11,04 10.223.238.246 [10.223.238.246]
5 239 0 3,00 25,52 4,97 5.178.44.38 [5.178.44.38]
6 239 1 102,53 126,78 106,03 89.221.41.177 [89.221.41.177]
7 239 0 103,82 190,14 110,47 89.221.41.3 [89.221.41.3]
8 239 7 136,20 334,24 159,67 ae1-br01-eqmi2.as57976. net [137.221.76.33]
9 239 5 136,88 347,92 164,80 xe-0-0-0-1-br01-eqat2.as57976. net [137.221.65.50]
10 239 100 0 0 0 [-]
11 239 0 135,53 361,02 166,69 137.221.69.87 [137.221.69.87]
12 239 1 136,59 373,77 171,20 137.221.67.65 [137.221.67.65]
13 239 5 134,83 338,53 160,44 (US Central) [24.105.62.129]
Your latency issues are happening in your ISP’s network or peering partners, before you reach Blizzard’s peer nodes or their servers.
It might be a company they contract with for routing and not their own network nodes. We are not network engineers at your ISP, so we don’t have that information. But your problem is not with any WoW server.
Hello,
I spoke to my ISP and they came to my house and exchanged my modem/router for a more modern one.
I noticed that there is a change in the behavior of routes through Pingploter. Can you tell me if there is still a problem on my side?
Target Name: (US Central)
IP: 24.105.62.129
Date/Time: 08/01/2024 11:41:51 - 08/01/2024 11:51:51
Hop Sent PL% Min Max Avg Host Name / [IP]
1 168 0 0,31 5,07 0,62 Broadcom.Home [192.168.1.1]
2 168 0 3,02 31,06 9,03 186-230-220-107.ded.intelignet.com.br [186.230.220.107]
3 168 0 3,36 24,00 6,33 10.221.252.34 [10.221.252.34]
4 168 0 3,00 156,15 12,90 10.223.238.246 [10.223.238.246]
5 168 0 3,00 23,28 4,92 5.178.44.38 [5.178.44.38]
6 168 0 102,58 148,09 106,67 et5-1-2.miami15.mia.seabone. net [89.221.41.175]
7 168 0 104,12 266,67 111,19 blizzard.miami15.mia.seabone. net [89.221.41.3]
8 168 0 135,87 354,49 141,40 ae1-br01-eqmi2.as57976. net [137.221.76.33]
9 168 0 135,23 358,42 142,94 xe-0-0-0-1-br01-eqat2.as57976. net [137.221.65.50]
10 168 100 0 0 0 [-]
11 168 0 136,00 357,62 139,35 137.221.69.87 [137.221.69.87]
12 168 0 135,85 352,09 139,65 137.221.67.65 [137.221.67.65]
13 168 3 135,00 348,07 149,08 (US Central) [24.105.62.129]
The ping between Brasil and Miami is about 102 to 120ms, so the test looks normal now. From your location, you have to connect through Miami to reach the US servers.
Hi there!
Thank you for trying to help, here are my results from WinMTR:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
Broadcom.Home - 0 | 75 | 75 | 1 | 1 | 26 | 1 |
186-230-221-127.ded.intelignet.c om . br - 0 | 75 | 75 | 2 | 6 | 30 | 24 |
10.40.8.129 - 0 | 75 | 75 | 2 | 3 | 29 | 2 |
10.192.254.44 - 0 | 75 | 75 | 3 | 4 | 30 | 3 |
10.223.238.238 - 0 | 75 | 75 | 2 | 4 | 30 | 3 |
No response from host - 100 | 15 | 0 | 0 | 0 | 0 | 0 |
et5-1-5.miami15.mia.seabone . net - 0 | 75 | 75 | 112 | 114 | 138 | 113 |
blizzard.miami15.mia.seabone. net - 0 | 75 | 75 | 108 | 113 | 169 | 109 |
137.221.76.35 - 0 | 75 | 75 | 167 | 170 | 198 | 169 |
xe-0-0-1-1-br01-eqda6.as57976. n et - 0 | 75 | 75 | 168 | 171 | 213 | 168 |
et-0-0-2-br02-swlv10.as57976. n et - 0 | 75 | 75 | 168 | 174 | 254 | 169 |
et-0-0-1-pe02-swlv10.as57976. n et - 0 | 75 | 75 | 169 | 171 | 199 | 170 |
las-swlv10-ia-bons-02.as57976. n et - 0 | 75 | 75 | 168 | 170 | 198 | 169 |
137.221.105.2 - 0 | 75 | 75 | 169 | 171 | 199 | 169 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
It usually happens at night around 10pm and later on. I get around 3k global ms and tried everything. Not a problem from ISP as well.
This would point to network congestion. From the test, your ping is already hitting 30ms only a little distance from your home line, which is kind of high. However, your ping to Miami is an average of 114ms, which seems normal to me.
Additionally, you’re playing on a different server than the other person I was helping. They’re connecting to a Chicago-based server, and you’re connecting to Las Vegas-based sever (or that is where you ran the test to). The distance from Miami to Las Vegas (2529mi/4070km) is much farther than Miami to Chicago (1380mi/2221km), so you will always see a higher ping.
Same problem here, also on a Brazilian server (Gallywix).
Generally 1k global and 200ms local, in my case the spikes are happening after reaching Blizzard nodes.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.