Joining the post
tried everything, changing to 3 different isp, nordvpn, and nothing.
I get disconnects multiple times hour
Joining the post
tried everything, changing to 3 different isp, nordvpn, and nothing.
I get disconnects multiple times hour
Joining the post.
Few days ago i got like 4 crashes in less then 1hour.
Stoped counting since then.
Same here. Keep crashing my graphic driver
Same here. I’m not really playing wow at the moment, but it’s unbearable in Overwatch.
endless dcs both in overwatch and wow classic for the past two months
realy not playable
Same issue @Hearthstone
Hey everyone.
Thank you all for getting back to us and keeping us up to date on these issues.
I want to touch on a few things that was mentioned here. The first is these tests that we have asked for, they don’t have to be exactly when the problem occurs. It is helpful if they are but having some information is better than none.
However, please do note that for us to investigate this further we really do need more information. Someone saying “I have this problem too” is good in terms of trying to understand the impact but it does not help us dig into the specific details as to what is causing this issue.
The second thing is, I understand this is a frustrating situation that leads to other issues such as disconnects or problems trying to raid with your guild. And while we can not deal with those issues here on the forums, please know that the reason we asked for this information is because it is what we need to try and help.
So if you havent done so already please take the time to go through our “connection troubleshooting” steps so that we can rule that out as a possible solution. And if you continue having issues please consider following the instructions above and provide the requested information.
Thank you all.
I agree with this post 100%
Supporting the post, please help us fix this.
Crazy amount of DCs.
Adding my support to the post. At least in Bezeq International’s case, this happens with all Blizzard services. On some disconnects not even bnet web services are available. (e.g.: eu.battle.net is unresponsive) This is accompanied by no general connectivity loss (everything else keeps working), and isn’t due to equipment or location. I’ve tried multiple routers, modems, addresses, ISPs, FTTH/DSL, etc.
With Overwatch I can side-step this issue with Haste (multipathing) but since they don’t support WoW, I can’t use it here. When this happens, there’s a “black hole” between Blizzard services and my/our computer(s), no matter the ISP. No packets are answered (and no ICMP unreachables are sent).
There are some classic disconnects sometimes. Some of them are, funnily enough, just the game server. Meaning in some cases in Overwatch I get booted to the main menu and can just “rejoin match” immediately.
I’ve done the following tests while not disconnected, but a couple times I’ve looked at Wireshark when it happened (in a particularly bad, minutes-long disconnect) and I can see packets being entirely unanswered; no “ICMP unreachable”, no routing error, just a black hole between me and Blizzard.
I’ve removed the specific parts of my IP (keeping the subnet intact) for privacy reasons.
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.???.???
2 7 ms 7 ms 7 ms bzq-79-180-72-1.red.bezeqint.net [79.180.72.1]
3 8 ms 8 ms 7 ms 10.250.10.78
4 7 ms 8 ms 7 ms bzq-25-77-26.cust.bezeqint.net [212.25.77.26]
5 60 ms 61 ms 69 ms bzq-114-65-1.cust.bezeqint.net [192.114.65.1]
6 60 ms 60 ms 60 ms bzq-219-189-230.cablep.bezeqint.net [62.219.189.230]
7 61 ms 61 ms 60 ms bzq-161-217.pop.bezeqint.net [212.179.161.217]
8 60 ms 61 ms 61 ms ffm-b2-link.telia.net [80.239.128.149]
9 63 ms 63 ms 63 ms ffm-bb3-link.telia.net [62.115.142.204]
10 70 ms 69 ms 69 ms prs-bb3-link.telia.net [62.115.123.13]
11 68 ms 70 ms 68 ms prs-b8-link.telia.net [62.115.138.133]
12 69 ms 123 ms 69 ms blizzard-ic-348624-prs-b8.c.telia.net [62.115.178.205]
13 72 ms 72 ms 72 ms ae1-br02-eqpa4.as57976.net [137.221.77.35]
14 76 ms 76 ms 76 ms et-0-0-3-br02-eqam1.as57976.net [137.221.65.93]
15 116 ms 73 ms 73 ms et-0-0-67-pe01-eqam1.as57976.net [137.221.78.71]
16 72 ms 72 ms 72 ms 185.60.112.157
Tracing route to 185.60.112.158 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.???.???
2 7 ms 7 ms 8 ms bzq-79-180-72-1.red.bezeqint.net [79.180.72.1]
3 8 ms 7 ms 17 ms 10.250.10.70
4 8 ms 8 ms 8 ms bzq-25-77-18.cust.bezeqint.net [212.25.77.18]
5 59 ms 59 ms 59 ms bzq-114-65-1.cust.bezeqint.net [192.114.65.1]
6 63 ms 63 ms 63 ms bzq-219-189-78.dsl.bezeqint.net [62.219.189.78]
7 60 ms 60 ms 60 ms bzq-161-217.pop.bezeqint.net [212.179.161.217]
8 59 ms 60 ms 60 ms ffm-b2-link.telia.net [80.239.128.149]
9 63 ms 63 ms 62 ms ffm-bb3-link.telia.net [62.115.142.204]
10 68 ms 68 ms 69 ms prs-bb3-link.telia.net [62.115.123.13]
11 67 ms 67 ms 67 ms prs-b8-link.telia.net [62.115.138.133]
12 115 ms 68 ms 68 ms blizzard-ic-348624-prs-b8.c.telia.net [62.115.178.205]
13 71 ms 71 ms 71 ms ae1-br02-eqpa4.as57976.net [137.221.77.35]
14 75 ms 76 ms 75 ms et-0-0-3-br02-eqam1.as57976.net [137.221.65.93]
15 71 ms 70 ms 70 ms et-0-0-67-pe02-eqam1.as57976.net [137.221.78.73]
16 71 ms 71 ms 71 ms 185.60.112.158
Tracing route to 185.60.112.159 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.???.???
2 7 ms 12 ms 7 ms bzq-79-180-72-1.red.bezeqint.net [79.180.72.1]
3 8 ms 8 ms 7 ms 10.250.10.78
4 8 ms 7 ms 7 ms bzq-25-77-26.cust.bezeqint.net [212.25.77.26]
5 60 ms 60 ms 60 ms bzq-114-65-1.cust.bezeqint.net [192.114.65.1]
6 60 ms 61 ms 60 ms bzq-219-189-230.cablep.bezeqint.net [62.219.189.230]
7 61 ms 61 ms 60 ms bzq-161-217.pop.bezeqint.net [212.179.161.217]
8 61 ms 60 ms 60 ms ffm-b2-link.telia.net [80.239.128.149]
9 61 ms 60 ms 60 ms ffm-bb2-link.telia.net [62.115.142.194]
10 70 ms 70 ms 70 ms prs-bb4-link.telia.net [62.115.122.138]
11 73 ms 73 ms 74 ms prs-b8-link.telia.net [62.115.138.139]
12 70 ms 69 ms 70 ms blizzard-ic-348624-prs-b8.c.telia.net [62.115.178.205]
13 72 ms 73 ms 73 ms ae1-br02-eqpa4.as57976.net [137.221.77.35]
14 89 ms 77 ms 77 ms et-0-0-3-br02-eqam1.as57976.net [137.221.65.93]
15 73 ms 74 ms 72 ms et-0-0-67-pe02-eqam1.as57976.net [137.221.78.73]
185.60.112.159 doesn’t answer to pings.
Looking Glass traceroutes (EU - World of Warcraft - Khadgar) (my router doesn’t respond to pings, ISP does, you can assume last node is me)
TRACEROUTE:
traceroute to 79.180.*.* (79.180.*.*), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.283 ms 0.279 ms 0.280 ms
2 37.244.24.3 (37.244.24.3) 0.517 ms 0.619 ms 0.723 ms
3 Blizzard Blizzard 1.108 ms 1.182 ms 1.229 ms
4 137.221.66.40 (137.221.66.40) 1.150 ms 1.161 ms 1.162 ms
5 137.221.78.66 (137.221.78.66) 6.528 ms 6.557 ms 6.565 ms
6 137.221.65.28 (137.221.65.28) 6.292 ms 6.511 ms 6.483 ms
7 137.221.80.32 (137.221.80.32) 6.443 ms 6.480 ms 6.438 ms
8 * * *
9 bzq-179-124-125.cust.bezeqint.net (212.179.124.125) 65.022 ms 65.106 ms 65.110 ms
10 bzq-179-124-85.cust.bezeqint.net (212.179.124.85) 63.903 ms 63.801 ms 63.905 ms
11 bzq-25-77-21.cust.bezeqint.net (212.25.77.21) 64.638 ms 64.703 ms 64.449 ms
12 * * *
13 * * *
14 * * *
15 * * *
28/01/2020 01:56:05 UTC
--------------------
TRACEROUTE:
traceroute to 79.180.*.* (79.180.*.*), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.410 ms 0.405 ms 0.402 ms
2 37.244.24.3 (37.244.24.3) 1.080 ms 1.459 ms 1.611 ms
3 Blizzard Blizzard 1.281 ms 1.446 ms 1.488 ms
4 137.221.66.40 (137.221.66.40) 1.278 ms 1.276 ms 1.276 ms
5 137.221.78.66 (137.221.78.66) 6.755 ms 6.764 ms 6.764 ms
6 137.221.65.28 (137.221.65.28) 20.086 ms 29.912 ms 29.894 ms
7 137.221.80.32 (137.221.80.32) 6.711 ms 6.416 ms 6.402 ms
8 * * *
9 bzq-179-124-125.cust.bezeqint.net (212.179.124.125) 65.017 ms 65.014 ms 65.185 ms
10 bzq-179-124-85.cust.bezeqint.net (212.179.124.85) 64.660 ms 66.453 ms 66.434 ms
11 bzq-25-77-21.cust.bezeqint.net (212.25.77.21) 64.809 ms 64.770 ms 64.493 ms
12 * * *
13 * * *
14 * * *
15 * * *
28/01/2020 01:56:05 UTC
--------------------
TRACEROUTE:
traceroute to 79.180.*.* (79.180.*.*), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.163 ms 1.146 ms 1.141 ms
2 37.244.24.3 (37.244.24.3) 2.293 ms 2.345 ms 2.398 ms
3 Blizzard Blizzard 2.304 ms 2.466 ms 2.529 ms
4 137.221.66.40 (137.221.66.40) 2.231 ms 2.233 ms 2.231 ms
5 137.221.78.66 (137.221.78.66) 7.410 ms 7.408 ms 7.408 ms
6 137.221.65.28 (137.221.65.28) 20.735 ms 29.935 ms 29.904 ms
7 137.221.80.32 (137.221.80.32) 6.956 ms 6.918 ms 6.909 ms
8 * * *
9 bzq-179-124-125.cust.bezeqint.net (212.179.124.125) 65.028 ms 65.447 ms 65.418 ms
10 bzq-179-124-85.cust.bezeqint.net (212.179.124.85) 66.564 ms 65.469 ms 65.442 ms
11 bzq-25-77-21.cust.bezeqint.net (212.25.77.21) 64.560 ms 64.539 ms 64.521 ms
12 * * *
13 * * *
14 * * *
15 * * *
28/01/2020 01:56:05 UTC
--------------------
TRACEROUTE:
traceroute to 79.180.*.* (79.180.*.*), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.333 ms 0.329 ms 0.328 ms
2 37.244.25.130 (37.244.25.130) 0.988 ms 0.989 ms 0.988 ms
3 Blizzard Blizzard 0.893 ms 0.909 ms 0.956 ms
4 137.221.66.34 (137.221.66.34) 1.087 ms 1.202 ms 1.307 ms
5 137.221.77.66 (137.221.77.66) 19.534 ms 19.539 ms 19.544 ms
6 137.221.65.27 (137.221.65.27) 9.289 ms 9.409 ms 9.390 ms
7 137.221.80.34 (137.221.80.34) 15.838 ms 15.867 ms 15.870 ms
8 * * *
9 bzq-179-124-254.cust.bezeqint.net (212.179.124.254) 60.407 ms 60.342 ms 60.325 ms
10 bzq-179-124-85.cust.bezeqint.net (212.179.124.85) 64.601 ms 64.497 ms 64.646 ms
11 bzq-179-124-81.cust.bezeqint.net (212.179.124.81) 60.328 ms 60.547 ms 60.526 ms
12 bzq-25-77-17.cust.bezeqint.net (212.25.77.17) 64.535 ms 64.673 ms 64.686 ms
13 * * *
14 * * *
15 * * *
28/01/2020 01:56:05 UTC
--------------------
TRACEROUTE:
traceroute to 79.180.*.* (79.180.*.*), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.282 ms 0.282 ms 0.282 ms
2 37.244.25.130 (37.244.25.130) 0.747 ms 0.765 ms 0.766 ms
3 Blizzard Blizzard 2.101 ms 2.101 ms 2.104 ms
4 137.221.66.34 (137.221.66.34) 2.066 ms 2.080 ms 2.087 ms
5 137.221.77.66 (137.221.77.66) 65.670 ms 65.696 ms 65.703 ms
6 137.221.65.27 (137.221.65.27) 9.292 ms 9.579 ms 9.581 ms
7 137.221.80.34 (137.221.80.34) 9.577 ms 9.581 ms 9.565 ms
8 * * *
9 bzq-179-124-254.cust.bezeqint.net (212.179.124.254) 60.582 ms 60.569 ms 60.565 ms
10 bzq-179-124-85.cust.bezeqint.net (212.179.124.85) 64.546 ms 65.158 ms 64.487 ms
11 bzq-179-124-81.cust.bezeqint.net (212.179.124.81) 60.182 ms 60.192 ms 60.224 ms
12 bzq-25-77-17.cust.bezeqint.net (212.25.77.17) 64.584 ms 64.527 ms 64.520 ms
13 * * *
14 * * *
15 * * *
28/01/2020 01:56:05 UTC
--------------------
TRACEROUTE:
traceroute to 79.180.*.* (79.180.*.*), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.292 ms 0.275 ms 0.825 ms
2 37.244.25.130 (37.244.25.130) 0.827 ms 0.826 ms 0.824 ms
3 Blizzard Blizzard 1.401 ms 1.456 ms 1.502 ms
4 137.221.66.34 (137.221.66.34) 1.263 ms 2.766 ms 2.772 ms
5 137.221.77.66 (137.221.77.66) 32.874 ms 32.905 ms 32.910 ms
6 137.221.65.27 (137.221.65.27) 9.404 ms 9.575 ms 9.544 ms
7 137.221.80.34 (137.221.80.34) 9.509 ms 9.455 ms 9.820 ms
8 * * *
9 bzq-179-124-254.cust.bezeqint.net (212.179.124.254) 60.463 ms 60.303 ms 60.337 ms
10 bzq-179-124-85.cust.bezeqint.net (212.179.124.85) 64.819 ms 64.670 ms 66.097 ms
11 bzq-179-124-81.cust.bezeqint.net (212.179.124.81) 61.717 ms 61.743 ms 61.252 ms
12 bzq-25-77-17.cust.bezeqint.net (212.25.77.17) 65.173 ms 64.728 ms 64.708 ms
13 * * *
14 * * *
15 * * *
28/01/2020 01:56:05 UTC
--------------------
Pathping returns exact same route and ping as above. No difference or variation.
Hi.
I thought to get back to game and start subscription.
I logged into my 20 lvl character and wanted to check what is going with game.
Then i joined Dungeon Finder, found team and started to do it.
But after 20-30 min I got disconnect.
I closed the game client, run it again, logged into game, picked one of my char and tried to enter world, but again got disconnect.
After 10 - 20 min i tried the same steps, and got inside world.
And latency monitor show around 10 000 - 20 000 ms home latency / 70 world latency . During around 30 min playing home latency got to it common value 70. I repeated all these steps many times to check.
So, steps are -
1 - Log into game.
2 - Pick character and enter world, latency home 70 / world 70.
3 - Start dungeon.
4 - After 20-30 min playing dungeon get disconnect.
5 - Log into game.
5 - Pick character and trying to enter world.
7 - Get disconnect.
8 - Wait 10-20 min
9 - Log into game again.
10 - Pick character and trying to enter world
11 - Enter world, latency home 10 000 - 20 000 / world 70
12 - Wait inside the game around 30 min, home latency gradually get to 70 and i have home 70 / world 70
13 - Then again join dungeon.
14 - Play 10-20 min inside dungeon and get disconnect.
I thought to fix it.
I removed all blizzard folders in AppData, ProgramData.
I removed WTF, Cash, Interface Folders, got completely fresh game, flush dns etc. and repeated all the steps. result was the same: disconnect from the game with insane high home latency.
In other hand i did the same with character on other low populated realm
and didn’t got disconnect at all.
Other online games like eveonline , world of tank run smoothly. no one get disconnect.
I ask Blizzard to allow me transfer all my mains away from lagging Outland to any low populated realm. Then i will pay subscription for playing.
thx
Oh my is this an Israel wide problem? I saw some Turkish players complaining too. Maybe the whole middle east.
I know this is a bump, but there might be an issue grander than the individual user.
Same here, isreali player, can’t play the game, getting hugh lag spikes and then game freeze > DC…
i guess ill unsub, no other choice, wasting my time and not having fun.
Hello? Can we get a fix for this issue, it is very annoying, to dc in the middle of a boss fight.
Joining the post.
Please fix the godamn problem…
Another Israeli player here with the same connection issues.
I guess theres nothing they will do to fix this tbh…
I thought they fixed it, cause i had no troubles with that since january, but last week i have like 5 disconnects in an hour aswell as crazy ping time after time.
Can blizzard please do somethng already or they just dont care about people? Thanks.
This post is rather old and inactive for almost 3 months until now. If any of you are still experiencing connection issues however, please create your own threads so we can help you.
You can find a great article to get you started here. In your threads, please include a copy of your system files and a winmtr created while you are seeing issues. You can upload these to pastebin.com and include with the links to the files using the preformatted text option to encapsulate the links.