I’m getting 34% packet loss to: et-0-0-2-br01-eqam1.as57976.net
Checking it up: Organization: Blizzard Entertainment, Inc
It’s in your hands this is. Can you fix it any time soon? This has been a problem for months by now that this node is acting up.
edit: Ok, that node is giving me 3k ms as well.
instead of fixing anything they applied a queue as well. but that’s ok we have xp buff. i returned after many months only to see that blizzard got worse. /sigh /no hope
Wonder if it has something to do with adding normie cod which is super popular now to battle net.
That’s a fair point to be honest, but let’s not forget that WoW is pretty normie nowadays 
ae1-br01-eqfr5.as57976.net and et-0-0-2-br01-eqam1.as57976.net are the issues. They’re your nodes, Blizzard.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 89 | 89 | 0 | 0 | 2 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| 192.168.83.2 - 0 | 89 | 89 | 9 | 14 | 32 | 16 |
| static-212-162-183-1.cust.tele2.se - 0 | 89 | 89 | 10 | 16 | 42 | 17 |
| lim-core-1.bundle-ether7.tele2.net - 0 | 89 | 89 | 15 | 20 | 52 | 21 |
| lim-core-1.bundle-ether6.tele2.net - 2 | 86 | 85 | 0 | 38 | 66 | 39 |
| fra36-core-1.bundle-ether6.tele2.net - 0 | 89 | 89 | 34 | 39 | 55 | 39 |
| fra4-core-1.bundle-ether8.tele2.net - 0 | 89 | 89 | 34 | 40 | 57 | 36 |
| 130.244.200.27 - 0 | 89 | 89 | 32 | 41 | 95 | 39 |
| ae1-br01-eqfr5.as57976.net - 11 | 65 | 58 | 38 | 77 | 1831 | 1831 |
| et-0-0-2-br01-eqam1.as57976.net - 10 | 65 | 59 | 37 | 136 | 3299 | 3299 |
| 137.221.78.79 - 3 | 82 | 80 | 0 | 43 | 91 | 80 |
| 185.60.112.157 - 0 | 89 | 89 | 37 | 43 | 62 | 41 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Spiking up to 1.8k on one and 3.3k on the other? With a constant 10% packet loss. Seriously. This has been going on several days, with these nodes.
Wiping in underrot due to this, noticed lag on first boss so I started winmtr. AE1 and ET were lagging like mad. I was having several seconds where the game wouldn’t register anything I pressed and when it resumed the party was dead.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 240 | 240 | 0 | 0 | 16 | 0 |
| No response from host - 100 | 49 | 0 | 0 | 0 | 0 | 0 |
| 192.168.83.2 - 1 | 236 | 235 | 8 | 13 | 25 | 15 |
| static-212-162-183-1.cust.tele2.se - 1 | 236 | 235 | 10 | 15 | 30 | 10 |
| lim-core-1.bundle-ether7.tele2.net - 1 | 236 | 235 | 13 | 18 | 31 | 17 |
| lim-core-1.bundle-ether6.tele2.net - 1 | 232 | 230 | 33 | 37 | 54 | 36 |
| fra36-core-1.bundle-ether6.tele2.net - 1 | 236 | 235 | 34 | 38 | 56 | 40 |
| fra4-core-1.bundle-ether8.tele2.net - 1 | 236 | 235 | 33 | 38 | 54 | 40 |
| 130.244.200.27 - 0 | 240 | 240 | 32 | 40 | 91 | 36 |
| ae1-br01-eqfr5.as57976.net - 7 | 194 | 182 | 0 | 57 | 2263 | 2263 |
| et-0-0-2-br01-eqam1.as57976.net - 6 | 198 | 188 | 37 | 80 | 3519 | 3519 |
| 137.221.78.79 - 0 | 240 | 240 | 36 | 42 | 101 | 43 |
| 185.60.112.157 - 1 | 232 | 230 | 0 | 41 | 67 | 42 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderThere appears to be a bit of a misunderstanding going on here -
eqfr5.as57976.net is a node that does lead to our network, but the data showing up for it is somewhat misleading as said node deliberately throttles/delays certain types of data packets which are commonly used in flooding/DDoS-type attacks.
Said packet types also include ICMP_ECHO (lovingly called “ping” by oldschool-networkers), which tests like WinMTR happen to use - but the node does not throttle or delay any form of actually game-relevant data (so it’d not slow down the game, regardless of what it does to the other packet-types).
In other words: whats showing up in these test results may look strange, but in fact is not indicative of any kind of problem on that level. If a node on our network would have actual issues those would also not be limited to impacting only select individuals - every single player accessing the game within the region would have the exact same trouble, which is demonstrably not the case here.
In all the MTR logs posted in this thread there are however losses showing up much earlier in the connection route (including within the local network in one case), which would very much be worth looking into - they may well be the cause of the troubles people are seeing.
There’s a lot of people having severe problems right now, people complaining exactly at the same time in dungeon runs. From different countries. It’s extremely unlikely we would all have the same packet drops that causes such severe problems at the exactly same time, independently, when we come from different countries, have different ISPs and different routing.
It happens in Overwatch too, people in the games complaining about lag at exactly the same time, from different countries. People have been disconnected at the exactly same time and they’ve been from different countries.
Testing another connection yields me this result:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.42.129 - 0 | 45 | 45 | 0 | 1 | 12 | 1 |
| No response from host - 100 | 10 | 0 | 0 | 0 | 0 | 0 |
| 10.9.47.81 - 0 | 45 | 45 | 22 | 31 | 49 | 22 |
| 10.9.47.22 - 0 | 45 | 45 | 18 | 26 | 46 | 21 |
| 10.9.47.26 - 0 | 45 | 45 | 18 | 29 | 46 | 26 |
| m-b-peer4-link.se.telia.net - 0 | 45 | 45 | 20 | 28 | 48 | 20 |
| kbn-b3-link.telia.net - 0 | 45 | 45 | 23 | 34 | 51 | 24 |
| kbn-bb3-link.telia.net - 0 | 45 | 45 | 36 | 48 | 64 | 46 |
| hbg-bb3-link.telia.net - 0 | 45 | 45 | 32 | 42 | 56 | 33 |
| adm-bb3-link.telia.net - 0 | 45 | 45 | 33 | 44 | 64 | 38 |
| adm-b2-link.telia.net - 0 | 45 | 45 | 36 | 46 | 57 | 38 |
| blizzard-ic-348623-adm-b2.c.telia.net - 0 | 45 | 45 | 34 | 49 | 83 | 38 |
| ae1-br02-eqam1.as57976.net - 15 | 28 | 24 | 40 | 239 | 3519 | 3519 |
| 137.221.78.85 - 0 | 45 | 45 | 34 | 49 | 105 | 39 |
| 137.221.66.43 - 0 | 45 | 45 | 38 | 47 | 57 | 47 |
| 185.60.112.157 - 0 | 45 | 45 | 37 | 48 | 55 | 44 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Right when that “worst” happened on ae1 I was getting freezes in the game right after I started doing the winmtr. You mean to tell me this is a coincidence? That 15% packet loss and huge ping spike exactly when I start freezing in the game is just a coincidence? The issue lies elsewhere?
Restarted it and it spikes yet again on AE1 when I’m getting freezes/spikes in the game.
I have a constant 3% packet loss to ae1 too when measured over a longer period of time.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.42.129 - 0 | 723 | 723 | 0 | 1 | 15 | 1 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| 10.9.47.81 - 0 | 723 | 723 | 18 | 25 | 50 | 24 |
| 10.9.47.22 - 0 | 723 | 723 | 17 | 24 | 47 | 22 |
| 10.9.47.26 - 0 | 723 | 723 | 19 | 26 | 53 | 24 |
| m-b-peer4-link.se.telia.net - 0 | 723 | 723 | 19 | 27 | 136 | 20 |
| kbn-b3-link.telia.net - 0 | 723 | 723 | 20 | 28 | 55 | 25 |
| kbn-bb3-link.telia.net - 0 | 723 | 723 | 32 | 40 | 73 | 37 |
| hbg-bb3-link.telia.net - 0 | 723 | 723 | 32 | 39 | 72 | 35 |
| adm-bb3-link.telia.net - 0 | 723 | 723 | 32 | 40 | 84 | 55 |
| adm-b2-link.telia.net - 0 | 723 | 723 | 32 | 41 | 68 | 42 |
| blizzard-ic-348623-adm-b2.c.telia.net - 0 | 723 | 723 | 33 | 47 | 419 | 53 |
| ae1-br02-eqam1.as57976.net - 3 | 641 | 622 | 32 | 74 | 3908 | 36 |
| 137.221.78.85 - 0 | 723 | 723 | 32 | 43 | 106 | 38 |
| 137.221.66.43 - 0 | 723 | 723 | 32 | 40 | 101 | 40 |
| 185.60.112.157 - 0 | 723 | 723 | 32 | 41 | 82 | 48 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
edit:
So I tried the looking glass tool you have too.
MTR:
Start: Sat Mar 28 14:06:09 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.24.3 0.0% 10 0.4 0.6 0.4 0.9 0.0
3.|-- Blizzard 0.0% 10 1.1 1.9 1.1 5.5 1.2
4.|-- 137.221.66.46 0.0% 10 0.8 5.6 0.5 49.0 15.3
**5.|-- 137.221.78.88 0.0% 10 267.4 349.7 46.9 559.3 161.1**
6.|-- 137.221.78.34 0.0% 10 1.3 4.5 1.0 34.3 10.4
7.|-- adm-b2-link.telia.net 0.0% 10 1.2 1.1 0.9 1.4 0.0
8.|-- adm-bb3-link.telia.net 0.0% 10 13.7 13.7 13.5 13.9 0.0
9.|-- hbg-bb3-link.telia.net 0.0% 10 12.7 12.8 12.6 12.9 0.0
10.|-- 213.155.130.101 0.0% 10 13.9 14.3 13.8 15.9 0.5
11.|-- kbn-b2-link.telia.net 0.0% 10 12.8 14.2 12.8 21.9 2.9
12.|-- ld-h-peer4-link.telia.net 0.0% 10 13.9 16.3 13.9 36.6 7.1
13.|-- ld-h-sec81-link.se.telia.net 0.0% 10 16.4 16.4 16.3 16.7 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
Number 5 is part of your infrastructure, no? Or is it others? That’s giving problems from your side?
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.0.1 | 0 | 597 | 597 | 0 | 0 | 3 | 0 |
| 100.111.43.1 | 0 | 597 | 597 | 0 | 7 | 541 | 6 |
| 94.20.50.65 | 0 | 597 | 597 | 4 | 12 | 538 | 12 |
| 10.50.10.42 | 0 | 597 | 597 | 7 | 15 | 534 | 13 |
| 87.226.177.97 | 0 | 597 | 597 | 13 | 22 | 542 | 17 |
| ae51.frkt-cr2.intl.ip.rostelecom.ru | 0 | 597 | 597 | 24 | 36 | 556 | 30 |
| pr01.eqfr5.blizzardonline.net | 1 | 593 | 592 | 93 | 111 | 624 | 112 |
| ae1-br01-eqfr5.as57976.net | 10 | 429 | 387 | 140 | 184 | 470 | 164 |
| et-0-0-2-br01-eqam1.as57976.net | 9 | 434 | 395 | 248 | 341 | 4331 | 284 |
| 137.221.78.79 | 8 | 455 | 422 | 106 | 343 | 4407 | 111 |
| 185.60.112.157 | 12 | 405 | 357 | 151 | 188 | 464 | 177 |
“Much earlier” Can you explain this then? i’m pretty sure you aren’t going to reply to this one since you cant find any fault from my side and you don’t wanna admit there is a blizzard problem.
Your MS is rather unstable up from the second hop (wost of 500+). It may not be losses, but “you cant find any fault from my side” is quite a bold statement when showing that data.
“much earlier” made me laugh. Blizzard replies to the trace routes they can easily dismiss and make it sound like they are all the same. There are several posts from people with trace routes that point out blizzard nodes and the mentioned “ae1” server as the one causing high latency or packet loss, and they don’t reply to those posts/threads. It all feels a bit “sweeping under the rug”.
Dear Blizz: Even if you can’t fix it or have no clue WHEN it’ll be fixed, please acknowledge it with a reply. Instead of leaving us to wonder if we’re even being heard/taken seriously. We do pay each month for this after all.
PS: sorry for being snappy, it’s just frustrating
Worst don’t matter Packet loss and average does i switched to vpn tethering during the test so the internet was off for mini sec, Here are new traceroutes to back my “Bold statements”
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.0.1 | 0 | 410 | 410 | 0 | 0 | 6 | 0 |
| 100.111.43.1 | 0 | 410 | 410 | 0 | 2 | 30 | 27 |
| 94.20.50.65 | 0 | 410 | 410 | 3 | 6 | 40 | 28 |
| 10.50.10.42 | 0 | 410 | 410 | 10 | 12 | 43 | 43 |
| 87.226.177.97 | 0 | 410 | 410 | 21 | 24 | 91 | 53 |
| ae51.frkt-cr2.intl.ip.rostelecom.ru | 0 | 410 | 410 | 78 | 96 | 125 | 124 |
| pr01.eqfr5.blizzardonline.net | 13 | 274 | 241 | 133 | 171 | 374 | 169 |
| ae1-br01-eqfr5.as57976.net | 11 | 291 | 261 | 241 | 293 | 988 | 320 |
| et-0-0-2-br01-eqam1.as57976.net | 6 | 267 | 251 | 0 | 1326 | 3268 | 1319 |
| 137.221.78.79 | 12 | 279 | 246 | 136 | 173 | 236 | 185 |
| 185.60.112.157 | 10 | 297 | 269 | 241 | 282 | 318 | 278 |
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.0.1 | 0 | 964 | 964 | 0 | 0 | 10 | 0 |
| 100.111.43.1 | 0 | 964 | 964 | 0 | 3 | 34 | 3 |
| 94.20.50.65 | 1 | 960 | 959 | 3 | 7 | 60 | 5 |
| 10.50.10.42 | 0 | 964 | 964 | 10 | 13 | 58 | 11 |
| 87.226.177.97 | 0 | 964 | 964 | 21 | 24 | 66 | 22 |
| ae9.frkt-cr2.intl.ip.rostelecom.ru | 0 | 964 | 964 | 77 | 96 | 138 | 97 |
| pr01.eqfr5.blizzardonline.net | 9 | 725 | 665 | 0 | 172 | 264 | 173 |
| ae1-br01-eqfr5.as57976.net | 10 | 696 | 630 | 241 | 299 | 3750 | 282 |
| et-0-0-2-br01-eqam1.as57976.net | 9 | 610 | 558 | 817 | 1273 | 4025 | 1439 |
| et-0-0-35-pe02-eqam1.as57976.net | 9 | 729 | 670 | 240 | 283 | 361 | 281 |
| 137.221.66.41 | 10 | 702 | 637 | 255 | 295 | 330 | 267 |
| 185.60.112.158 | 10 | 693 | 625 | 0 | 175 | 203 | 176 |
Hi, I have a lot issues when switching zones, I can’t start a MM+ dungeon, 2 times I lag in the dungeon (cannot cast) but still can talk normally. Here is my MTR:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192-222-191-97.qc.cable.ebox.net - 1 | 433 | 432 | 4 | 16 | 76 | 22 |
| 10.170.192.58 - 2 | 414 | 408 | 5 | 15 | 40 | 10 |
| 0.et-5-2-0.er1.mtl7.yul.ebox.ca - 1 | 433 | 432 | 6 | 15 | 52 | 21 |
| motl-b1-link.telia.net - 0 | 437 | 437 | 4 | 15 | 69 | 35 |
| nyk-bb3-link.telia.net - 92 | 93 | 8 | 0 | 103 | 113 | 105 |
| ldn-bb4-link.telia.net - 1 | 421 | 417 | 92 | 102 | 147 | 119 |
| adm-bb4-link.telia.net - 1 | 429 | 427 | 90 | 101 | 135 | 99 |
| adm-b2-link.telia.net - 1 | 430 | 429 | 93 | 100 | 125 | 100 |
| blizzard-ic-348623-adm-b2.c.telia.net - 1 | 429 | 427 | 90 | 106 | 548 | 113 |
| ae1-br02-eqam1.as57976.net - 2 | 401 | 393 | 0 | 145 | 3594 | 125 |
| 137.221.78.83 - 0 | 437 | 437 | 86 | 97 | 164 | 97 |
| 185.60.112.157 - 0 | 437 | 437 | 96 | 103 | 128 | 103 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
After some quests on a rerolls, I had some lags but it seems related to BFA stuff?
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192-222-191-97.qc.cable.ebox.net - 1 | 2808 | 2806 | 4 | 16 | 88 | 17 |
| 10.170.192.58 - 1 | 2793 | 2787 | 5 | 15 | 47 | 21 |
| 0.et-5-2-0.er1.mtl7.yul.ebox.ca - 1 | 2801 | 2797 | 6 | 14 | 52 | 10 |
| motl-b1-link.telia.net - 0 | 2816 | 2816 | 3 | 15 | 69 | 10 |
| nyk-bb3-link.telia.net - 14 | 1808 | 1555 | 0 | 117 | 144 | 129 |
| ldn-bb4-link.telia.net - 17 | 1710 | 1433 | 92 | 106 | 147 | 138 |
| adm-bb4-link.telia.net - 1 | 2738 | 2718 | 90 | 110 | 145 | 126 |
| adm-b2-link.telia.net - 1 | 2726 | 2703 | 91 | 110 | 143 | 111 |
| blizzard-ic-348623-adm-b2.c.telia.net - 1 | 2743 | 2724 | 90 | 114 | 548 | 113 |
| ae1-br02-eqam1.as57976.net - 3 | 2493 | 2420 | 0 | 147 | 4261 | 143 |
| 137.221.78.83 - 1 | 2734 | 2713 | 86 | 110 | 212 | 117 |
| 185.60.112.157 - 1 | 2746 | 2728 | 93 | 113 | 164 | 120 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderWhy just ignore what people are telling you? This is not the way to respond to a large amount of latency issues reports.
I didn’t use to have problems with WoW
I don’t have problems with other games, even NOW. But in WoW i am getting a completely unacceptable amount of lag spikes and sustained lag
What’s more, even within other blizzard games (in my case overwatch, where packet loss and latency would be several times more noticeable than in WoW), this problem does not show up, which makes blaming it on the routing even more silly.
So, please, fix your problems instead of trying to point your fingers at your frustrated users.
For the past few months, since October to be precise, i am having a bigger problem with high ms. The past two weeks this problem is worse and gets alot worse at night. To explain worse … while doing my rotation i am loosing 3 casts get one or two out and then loose 3-4 more. I am experiencing spikes, delays and the game is not enjoyable neither am i performing as i can within my raid. I am doing all my rotation/dps blindly.
I have been checking with my internet provider all this time and the conclusion is that the loss is not happening from their side neither do i have a problem with my landline. All the tracert tests i have done up to now show high ms at your servers and the connecting ones.
Today is a ““good day”” without the usual lag, i am between 198-280home and 330-420world ingame.
It sais that i cannot include links in my posts and i can’t link the looking-glass diagnostic tool results (Silvermoon server is not included nor Draenor) neither the tracert for the 3 European IP’s. (If there is a way to do so pls explain.)
I just logged on do world boss join raid do my dps dc reconnect dc reconnect dc reconnect dc reconnect dc non stop untill boss is dead and my experience is ruined, the biggest issue i have with this that if had this since 8.3 and i am still paying subscription and have pre ordered shadowlands, how dare they charge me money for this horrible service this is not excuseable, and all tech support asks is to try test test test without any changes, stop deluding yourself and compensate everyone, once this pandemic is over i am taking legal action, there no excuse if had no dc issues playing overwatch or other online games, this is a problem with your wow servers fix them or i force you to fix it after this pandemic when i sue you.
Adding to this too, clearly not a blizzard issue 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 0 | 380 | 380 | 0 | 0 | 3 | 0 |
| 10.203.144.1 - 0 | 380 | 380 | 9 | 15 | 23 | 18 |
| 10.242.130.56 - 0 | 380 | 380 | 7 | 11 | 54 | 9 |
| 10.0.30.13 - 0 | 380 | 380 | 9 | 19 | 240 | 17 |
| ae10-0.taas1cr2dk.gc-net. - 0 | 380 | 380 | 10 | 13 | 49 | 28 |
| 213.242.108.193 - 0 | 380 | 380 | 10 | 16 | 50 | 17 |
| ae-2-3211.edge7.Paris1.Level3.nt - 0 | 380 | 380 | 31 | 40 | 76 | 34 |
| BLIZZARD-EN.edge7.Paris1.Level3.n - 20 | 215 | 174 | 32 | 37 | 97 | 37 |
| ae1-br02-eqpa4.as57976.n - 0 | 380 | 380 | 32 | 40 | 133 | 35 |
| et-0-0-3-br02-eqam1.as57976.n - 0 | 380 | 380 | 33 | 39 | 92 | 38 |
| 137.221.78.89 - 0 | 380 | 380 | 32 | 39 | 106 | 40 |
| 137.221.66.47 - 0 | 380 | 380 | 32 | 37 | 46 | 37 |
| 185.60.112.157 - 0 | 380 | 380 | 32 | 36 | 44 | 36 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
same problem here, 26-04-2020 its still a problem, game just freezes but i can still talk in chat, tried every single solution available on the forums, still does it, even with completely reset wow, reset network adapters, restarted router, updated all drivers, run without addons, reset interface… everyting really… this is definently on blizzards end and i wont resub till this is fixed, completely unplayable everytime you enter an instance this happens, like bgs, arenas, raids etc. UNPLAYABLE.
Game unplayable, high latency.
Output from Trace route for this server appears to be my issue
Tracing route to 185.60.112.157 over a maximum of 30 hops
This server is returning a huge delay of 1539ms
> Tracing route to 185.60.112.157 over a maximum of 30 hops
>
> 1 <1 ms <1 ms <1 ms 192.168.1.1
> 2 11 ms 10 ms 11 ms lo0-ecldsl-bba1.gs1.eclipse.net.uk [82.153.1.65]
> 3 12 ms 12 ms 11 ms 86.54.135.72
> 4 11 ms 11 ms 11 ms 6-1-35.ear1.London1.Level3.net [212.113.15.73]
> 5 20 ms 22 ms 18 ms ae-2-3204.edge7.Amsterdam1.Level3.net [4.69.162.181]
> 6 24 ms 19 ms 19 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
> 7 1325 ms 1539 ms 1319 ms ae1-br02-eqam1.as57976.net [137.221.78.35]
> 8 18 ms 18 ms 18 ms 137.221.78.89
> 9 20 ms 19 ms 20 ms 137.221.66.47
> 10 19 ms 18 ms 18 ms 185.60.112.157
>
> Trace complete.
Seems to be a Blizzard load balancing issue!!!
For all those who have wasted their time restarting Pcs, modems and routers you should know that it is not your issue. You could pay for a VPN to force a different route and you wont pass this problematic route… This is a Blizzard issue not yours and they should offer a rebate to all those suffering this issue
When looking up this issue Blizzard advise this:
Zenlaka
321 posts
Customer Support
Feb '19
Hey y’all,
Latency issues can happen for a variety of reasons. Aoirin, you are playing from Brazil and it’s not uncommon for routing issues to start happening between Brazil and the US servers.
If you want to help us pinpoint where the problem may be happening, please reply with a WinMTR test. To do this, download WinMTR 62and type 24.105.62.129 in the “Host” field. Click start, then play for about 20 minutes after you get issues, then click on “Copy text to clipboard” and paste the results here. Highlight everything you just pasted, and hit the “code” button (</>). That’ll make the information much more readable.
Everyone else, it would be best to create your own thread with your ISP and region and include the MTR test in your own thread so there’s no confusion.
When people use this tool Blizzard advise this:
There appears to be a bit of a misunderstanding going on here -
eqfr5.as57976.net
is a node that does lead to our network, but the data showing up for it is somewhat misleading as said node deliberately throttles/delays certain types of data packets which are commonly used in flooding/DDoS-type attacks.
Said packet types also include ICMP_ECHO (lovingly called “ ping ” by oldschool-networkers), which tests like WinMTR happen to use - but the node does not throttle or delay any form of actually game-relevant data (so it’d not slow down the game, regardless of what it does to the other packet-types).
In other words: whats showing up in these test results may look strange, but in fact is not indicative of any kind of problem on that level
Blizzard i am seriously confused on this conflicting advice… Please advise?
Are they tryng to blame it on us? wth