Game is quite unplayable when this happens in raid. I had to skip two raids as tank because once this happens during the pull, well, you gonna wipe no matter what.
My DCs look like this: every 10 minutes or so, I got micro lag and got disconnect even from Battlenet. As I do not play as often right now as there in nothing much to do in the game, I can´t tell if this happens regularly or not. Weird about this is that I had this problem 2 weeks ago and than it disappeared for some time just to return today.
Same problem here. Not just with WoW, but with Diablo 3 as well, so presumably anything using battle.net.
I’ll add to it that this has also been occuring with me and a few of our raid members as well.
Primarily it seemed to affect people connecting from southeastern EU.
I am from Northeast.
Every time it occurs, the problem is in one of Blizzards edge router/firewalls.
The typical traceroute looks like this:
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
- 192.168.2.1 0.0% 3 0.1 0.1 0.1 0.1 0.0
- 90.191.16.3 0.0% 3 1.6 1.6 1.5 1.6 0.0
- 194.126.123.2 0.0% 3 2.0 1.8 1.5 2.0 0.0
- 213.248.99.34 0.0% 3 16.3 16.0 15.4 16.4 0.0
- 213.155.134.214 0.0% 2 33.6 33.5 33.4 33.6 0.0
- 62.115.141.237 0.0% 2 32.7 37.0 32.7 41.3 6.1
- 213.248.76.103 0.0% 2 33.7 33.2 32.7 33.7 0.0
- ???
- 137.221.65.29 0.0% 2 32.1 32.1 32.1 32.1 0.0
- 137.221.78.69 0.0% 2 31.1 31.5 31.1 31.8 0.0
- 137.221.66.45 0.0% 2 32.0 32.1 32.0 32.2 0.0
- 185.60.114.167 0.0% 2 32.0 31.9 31.9 32.0 0.0
- ???
The problem hops being the first Blizzard DNS named entities. #7
This is just an FYI. The problem is your end. What’s causing it, might not be but yeah. Just so you know.
If it isn’t dying hardware, probably a DOS.
Any plans on actually giving a statement on this? Or potentially fixing it?
Would be nice if you can do something about this before next raid tier
I have to note here that I kept the mtr(linux traceroute) running afterwards for the whole evening and the link with packet drops ended upat 99.7%, as if the router/firewall or whatever it is(load balanced?) was shut off? But I don’t frankly know what exactly, because higher TTLs still passed onto the next link and the path was running fine.
Some sort of a switchover failure is happening there?
iam still getting disconnects 2x - 3x per day i dont think wipe UI / addons will help. It happen also in battle.net app it just DC and login back random. Can anyone check this test below? Dont know if i have everything ok or no - iam not IT expert. ISP O2 Czech Repiblic 25Mbit VDSL
PING:
PING 85.70.191.229 (85.70.191.229) 56(84) bytes of data.
64 bytes from 85.70.191.229: icmp_seq=1 ttl=51 time=46.7 ms
64 bytes from 85.70.191.229: icmp_seq=2 ttl=51 time=45.7 ms
64 bytes from 85.70.191.229: icmp_seq=3 ttl=51 time=44.7 ms
64 bytes from 85.70.191.229: icmp_seq=4 ttl=51 time=45.2 ms
--- 85.70.191.229 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 44.767/45.653/46.794/0.780 ms
16/05/2019 02:55:46 UTC
--------------------
PING:
PING 85.70.191.229 (85.70.191.229) 56(84) bytes of data.
64 bytes from 85.70.191.229: icmp_seq=1 ttl=51 time=45.1 ms
64 bytes from 85.70.191.229: icmp_seq=2 ttl=51 time=45.6 ms
64 bytes from 85.70.191.229: icmp_seq=3 ttl=51 time=45.9 ms
64 bytes from 85.70.191.229: icmp_seq=4 ttl=51 time=44.9 ms
--- 85.70.191.229 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 44.924/45.408/45.917/0.419 ms
16/05/2019 02:55:46 UTC
--------------------
TRACEROUTE:
traceroute to 85.70.191.229 (85.70.191.229), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.072 ms 2.064 ms 2.075 ms
2 37.244.24.130 (37.244.24.130) 2.075 ms 2.077 ms 2.078 ms
3 Blizzard Blizzard 2.077 ms 2.079 ms 2.080 ms
4 137.221.66.44 (137.221.66.44) 0.847 ms 0.850 ms 0.849 ms
5 137.221.78.72 (137.221.78.72) 5.614 ms 5.629 ms 5.630 ms
6 137.221.78.34 (137.221.78.34) 0.768 ms 1.549 ms 1.594 ms
7 xe-9-1-3.edge6.Amsterdam1.Level3.net (213.19.197.253) 1.560 ms 1.569 ms 0.726 ms
8 * * *
9 * * *
10 O2-CZECH-RE.bear1.Prague1.Level3.net (212.162.8.98) 31.264 ms 30.450 ms 30.434 ms
11 194.228.190.161 (194.228.190.161) 28.280 ms 28.303 ms 28.411 ms
12 127.197.broadband16.iol.cz (90.183.197.127) 30.396 ms 29.595 ms 29.580 ms
13 * * *
14 229.191.broadband3.iol.cz (85.70.191.229) 45.126 ms 45.031 ms 45.024 ms
16/05/2019 02:55:46 UTC
--------------------
TRACEROUTE:
traceroute to 85.70.191.229 (85.70.191.229), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.341 ms 0.332 ms 0.334 ms
2 37.244.24.130 (37.244.24.130) 1.036 ms 1.041 ms 1.043 ms
3 Blizzard Blizzard 1.124 ms 1.167 ms 1.211 ms
4 137.221.66.44 (137.221.66.44) 0.976 ms 1.008 ms 1.009 ms
5 137.221.78.72 (137.221.78.72) 4.615 ms 4.645 ms 4.648 ms
6 137.221.78.34 (137.221.78.34) 0.981 ms 1.062 ms 1.077 ms
7 xe-9-1-3.edge6.Amsterdam1.Level3.net (213.19.197.253) 1.040 ms 1.042 ms 1.041 ms
8 * * *
9 * * *
10 O2-CZECH-RE.bear1.Prague1.Level3.net (212.162.8.98) 33.309 ms 32.494 ms 32.470 ms
11 194.228.190.161 (194.228.190.161) 32.389 ms 32.409 ms 32.410 ms
12 127.197.broadband16.iol.cz (90.183.197.127) 32.408 ms 31.584 ms 31.576 ms
13 * * *
14 229.191.broadband3.iol.cz (85.70.191.229) 45.279 ms 45.480 ms 45.512 ms
16/05/2019 02:55:46 UTC
--------------------
PING:
PING 85.70.191.229 (85.70.191.229) 56(84) bytes of data.
64 bytes from 85.70.191.229: icmp_seq=1 ttl=51 time=48.1 ms
64 bytes from 85.70.191.229: icmp_seq=2 ttl=51 time=47.8 ms
64 bytes from 85.70.191.229: icmp_seq=3 ttl=51 time=48.9 ms
64 bytes from 85.70.191.229: icmp_seq=4 ttl=51 time=48.3 ms
--- 85.70.191.229 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 47.879/48.315/48.902/0.382 ms
16/05/2019 02:55:50 UTC
--------------------
TRACEROUTE:
traceroute to 85.70.191.229 (85.70.191.229), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.308 ms 0.295 ms 0.298 ms
2 37.244.25.2 (37.244.25.2) 1.482 ms 1.499 ms 1.501 ms
3 Blizzard Blizzard 1.162 ms 1.510 ms 1.519 ms
4 137.221.66.36 (137.221.66.36) 1.059 ms 1.124 ms 1.193 ms
5 137.221.77.68 (137.221.77.68) 77.274 ms 77.313 ms 77.331 ms
6 137.221.77.32 (137.221.77.32) 0.583 ms 1.072 ms 1.045 ms
7 7-1-23.ear2.Paris1.Level3.net (212.73.205.157) 1.733 ms 1.780 ms 2.336 ms
8 * * *
9 * * *
10 O2-CZECH-RE.bear1.Prague1.Level3.net (212.162.8.98) 36.639 ms 35.951 ms 35.923 ms
11 194.228.190.161 (194.228.190.161) 33.620 ms 33.659 ms 33.832 ms
12 127.197.broadband16.iol.cz (90.183.197.127) 33.788 ms 31.037 ms 31.602 ms
13 * * *
14 229.191.broadband3.iol.cz (85.70.191.229) 47.754 ms 48.487 ms 47.686 ms
16/05/2019 02:55:49 UTC
--------------------
TRACEROUTE:
traceroute to 85.70.191.229 (85.70.191.229), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.306 ms 0.286 ms 0.284 ms
2 * * *
3 * * *
4 137.221.66.38 (137.221.66.38) 1.086 ms 1.125 ms 1.200 ms
5 137.221.77.72 (137.221.77.72) 1.302 ms 1.310 ms 1.311 ms
6 137.221.77.34 (137.221.77.34) 0.682 ms 0.632 ms 0.756 ms
7 7-1-23.ear2.Paris1.Level3.net (212.73.205.157) 1.116 ms 1.326 ms 1.654 ms
8 ae-1-11.bear1.Prague1.Level3.net (4.69.211.13) 30.790 ms 30.960 ms 31.193 ms
9 ae-1-11.bear1.Prague1.Level3.net (4.69.211.13) 31.782 ms 31.963 ms 31.792 ms
10 * * *
11 194.228.190.161 (194.228.190.161) 30.897 ms 30.636 ms 31.334 ms
12 127.197.broadband16.iol.cz (90.183.197.127) 30.979 ms 31.632 ms 31.539 ms
13 * * *
14 229.191.broadband3.iol.cz (85.70.191.229) 48.168 ms 48.392 ms 47.585 ms
16/05/2019 02:55:53 UTC
--------------------
PING:
PING 85.70.191.229 (85.70.191.229) 56(84) bytes of data.
64 bytes from 85.70.191.229: icmp_seq=1 ttl=51 time=47.8 ms
64 bytes from 85.70.191.229: icmp_seq=2 ttl=51 time=49.0 ms
64 bytes from 85.70.191.229: icmp_seq=3 ttl=51 time=48.2 ms
64 bytes from 85.70.191.229: icmp_seq=4 ttl=51 time=47.8 ms
--- 85.70.191.229 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 47.851/48.259/49.033/0.544 ms
16/05/2019 02:55:54 UTC
--------------------
MTR:
Start: Thu May 16 02:55:46 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.3 0.2 0.5 0.0
2.|-- 37.244.24.130 0.0% 10 0.7 0.7 0.5 1.2 0.0
3.|-- Blizzard 0.0% 10 1.4 1.4 1.1 2.4 0.0
4.|-- 137.221.66.44 0.0% 10 0.9 1.3 0.8 4.3 1.0
5.|-- 137.221.78.72 0.0% 10 19.8 12.1 2.4 26.2 8.0
6.|-- 137.221.78.34 0.0% 10 0.9 0.8 0.7 1.2 0.0
7.|-- xe-9-1-3.edge6.Amsterdam1.Level3.net 0.0% 10 0.9 0.8 0.7 0.9 0.0
8.|-- ae-1-11.bear1.Prague1.Level3.net 90.0% 10 27.5 27.5 27.5 27.5 0.0
9.|-- ae-1-11.bear1.Prague1.Level3.net 90.0% 10 27.8 27.8 27.8 27.8 0.0
10.|-- O2-CZECH-RE.bear1.Prague1.Level3.net 0.0% 10 30.4 31.1 28.8 34.5 1.5
11.|-- 194.228.190.161 0.0% 10 28.9 28.3 28.1 28.9 0.0
12.|-- 127.197.broadband16.iol.cz 0.0% 10 28.4 28.5 28.1 28.9 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 229.191.broadband3.iol.cz 0.0% 10 45.8 45.5 45.0 45.8 0.0
16/05/2019 02:55:46 UTC
--------------------
MTR:
Start: Thu May 16 02:55:46 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.24.130 0.0% 10 0.6 1.7 0.5 11.0 3.2
3.|-- Blizzard 0.0% 10 1.5 1.4 1.2 1.6 0.0
4.|-- 137.221.66.44 0.0% 10 0.9 0.8 0.7 1.0 0.0
5.|-- 137.221.78.72 0.0% 10 40.7 13.8 1.5 46.9 16.1
6.|-- 137.221.78.34 0.0% 10 0.9 0.8 0.7 1.0 0.0
7.|-- xe-9-1-3.edge6.Amsterdam1.Level3.net 0.0% 10 1.8 4.2 0.8 24.7 7.3
8.|-- ae-1-11.bear1.Prague1.Level3.net 90.0% 10 27.5 27.5 27.5 27.5 0.0
9.|-- ae-1-11.bear1.Prague1.Level3.net 90.0% 10 27.5 27.5 27.5 27.5 0.0
10.|-- O2-CZECH-RE.bear1.Prague1.Level3.net 0.0% 10 29.4 30.7 27.4 34.3 2.6
11.|-- 194.228.190.161 0.0% 10 28.7 29.2 27.8 39.7 3.7
12.|-- 127.197.broadband16.iol.cz 0.0% 10 28.7 28.5 28.2 29.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 229.191.broadband3.iol.cz 0.0% 10 46.0 45.6 44.7 46.3 0.0
16/05/2019 02:55:46 UTC
--------------------
MTR:
Start: Thu May 16 02:55:49 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- 37.244.25.2 0.0% 10 0.6 0.6 0.4 1.2 0.0
3.|-- Blizzard 0.0% 10 1.6 1.2 0.9 1.6 0.0
4.|-- 137.221.66.36 0.0% 10 0.9 1.2 0.8 3.0 0.3
5.|-- 137.221.77.68 0.0% 10 0.9 25.0 0.9 102.2 36.6
6.|-- 137.221.77.32 0.0% 10 0.8 0.8 0.6 0.9 0.0
7.|-- 7-1-23.ear2.Paris1.Level3.net 0.0% 10 1.3 1.3 1.2 1.5 0.0
8.|-- ae-1-11.bear1.Prague1.Level3.net 90.0% 10 30.5 30.5 30.5 30.5 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- O2-CZECH-RE.bear1.Prague1.Level3.net 0.0% 10 37.8 34.1 30.6 38.1 2.7
11.|-- 194.228.190.161 0.0% 10 30.2 30.5 30.2 31.6 0.3
12.|-- 127.197.broadband16.iol.cz 0.0% 10 31.0 31.3 30.9 32.4 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 229.191.broadband3.iol.cz 0.0% 10 48.2 48.1 47.5 48.9 0.0
16/05/2019 02:55:49 UTC
--------------------
MTR:
Start: Thu May 16 02:55:50 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 37.244.25.130 40.0% 10 0.5 0.5 0.5 0.6 0.0
3.|-- Blizzard 40.0% 10 1.1 1.0 0.9 1.3 0.0
4.|-- 137.221.66.38 10.0% 10 1.0 2.2 1.0 11.2 3.4
5.|-- 137.221.77.72 0.0% 10 0.8 17.1 0.8 84.8 30.3
6.|-- 137.221.77.34 0.0% 10 2.9 1.8 0.6 8.6 2.5
7.|-- 7-1-23.ear2.Paris1.Level3.net 0.0% 10 1.1 2.2 1.0 11.0 3.1
8.|-- ae-1-11.bear1.Prague1.Level3.net 90.0% 10 30.0 30.0 30.0 30.0 0.0
9.|-- ae-1-11.bear1.Prague1.Level3.net 90.0% 10 30.1 30.1 30.1 30.1 0.0
10.|-- O2-CZECH-RE.bear1.Prague1.Level3.net 40.0% 10 32.8 33.9 30.7 37.9 2.4
11.|-- 194.228.190.161 0.0% 10 30.9 30.8 30.4 31.4 0.0
12.|-- 127.197.broadband16.iol.cz 0.0% 9 30.8 31.6 30.8 33.6 0.6
13.|-- ??? 100.0 9 0.0 0.0 0.0 0.0 0.0
14.|-- 229.191.broadband3.iol.cz 0.0% 9 48.3 48.1 47.6 48.4 0.0
16/05/2019 02:55:50 UTC
--------------------
Both me and my best friend are getting random dc’s too. It always disconnects the bnet launcher as well, then it comes back after a short while. I can’t believe Blizzard are still blaming the players for this. When so many people in different countries, with different computers and ISP’s have the same problem, it’s on the players’ end?
Any update on this? Still happening several times a day…
edit: nvm, fault was on my end
Any update on this issue?
Having problem disconnection problems. Well, my wife disconnects so much. We play on the same computer setups, same updates, same connection but she experiences the disconnects the most.
Multiple times a day.
1 Like
Hello again,
Any update on this issue? Feels like all these forum posts about the same bnet disconnect issues just get swept under the rug by blizzard. Replying with the generic troubleshooting message is not gonna cut it tbh.
3 Likes
Hello again friends,
Apologies for posting again but i don’t see how else we are gonna get blizzard’s attention on this issue. Any updates??
1 Like
iam trying to login to beta stress test … after start game LOGIN SERVER IS FULL and then i have same error like in normal wow … RLY???
WOW51900319
- also every this disconnect game hide my extra action bars and disable scrolling combat text
I have something similar I play and suddenly the game does not react I run around nothing happens and I don´t get disconnect from the game immediately but have no interaction with the monsters or npc. After like 10 sec I drop the game manually and relog. Sometimes I get disconnected after like 10-20 seconds in this state. It started yesterday for me.
| WinMTR statistics |
Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
192.168.10.1 - 0 |
19263 |
19263 |
0 |
4 |
21 |
0 |
1.79-160-40.customer.lyse.ne - 1 |
19261 |
19260 |
2 |
10 |
61 |
7 |
217.213-167-114.customer.lyse.ne - 1 |
19260 |
19259 |
2 |
10 |
60 |
3 |
et-0-0-23.bar1.Oslo2.Level3.ne - 1 |
19252 |
19249 |
2 |
11 |
89 |
5 |
ae-2-3209.edge3.Frankfurt1.Level3.ne - 0 |
19264 |
19264 |
24 |
31 |
77 |
36 |
level3-gw.neterra.ne - 0 |
19264 |
19264 |
24 |
33 |
96 |
34 |
ae1-br01-eqfr5.as57976.ne - 1 |
19258 |
19257 |
27 |
37 |
1539 |
31 |
et-0-0-2-br01-eqam1.as57976.ne - 1 |
18902 |
18879 |
27 |
67 |
4839 |
68 |
et-0-0-31-pe02-eqam1.as57976.ne - 1 |
19260 |
19259 |
27 |
33 |
119 |
33 |
137.221.66.47 - 1 |
19260 |
19259 |
27 |
33 |
117 |
38 |
Destination network unreachable. - 1 |
19264 |
19263 |
27 |
33 |
105 |
29 |
________________________________________________ |
______ |
______ |
______ |
______ |
______ |
|
Ip for “Destination network unreachable” is 185.60.112.157
This was running while I disconnected.
Following. Have the same problem. Happens in both wow and diablo.
Hello again,
Any update?? Still same issue and no useful information from blizzard :))
1 Like
I’ve had the same Issue. Disabled IPv6-Protocol (my provider already uses IPv6), so my network card only uses IPv4 and the problems disappeared