Stuck in match - competitive

I’m currently stuck in a competitive match on the opponents turn. The auto end turn timer is not triggerring.

I let it sit about 5 mins. Then I started a recording of it that is just over 5 Mins long. Further I have uploaded it to youtube another 4-5 mins. Add another 5 mins for youtube to process it.

So far I’ve been stuck for about 20 minutes and counting. I don’t want to lose rank, so conceding is not an option.

Battle.net shows me as connected, I can access all features, friends. chat etc so I have not lost connectivity.

So how long will I have to wait for the match to end with out losing rank?

Video can be found here: https :// youtu.be / UX57nVAgFgM

sounds like:

Ok. So how does the game end with out me losing rank for conceding?

Also what is the IP of the hearthstone server so I can confirm via netstat, that it is indeed connected or not listed (and disconnected as you suggest)

Could it be one of these?:

TCP 192.168.1.33:52958 24.105.28.10:1119 ESTABLISHED
TCP 192.168.1.33:54289 EPSONB0D57F:microsoft-ds ESTABLISHED
TCP 192.168.1.33:59264 24.105.28.10:1119 ESTABLISHED
TCP 192.168.1.33:59284 137.221.106.102:https CLOSE_WAIT
TCP 192.168.1.33:62990 a23-12-144-177:https ESTABLISHED
TCP 192.168.1.33:63204 ec2-52-35-57-148:https ESTABLISHED
TCP 192.168.1.33:63276 151.101.248.193:https ESTABLISHED
TCP 192.168.1.33:63278 151.101.20.193:https ESTABLISHED
TCP 192.168.1.33:63281 49:https TIME_WAIT
TCP 192.168.1.33:63284 151.101.248.193:https ESTABLISHED
TCP 192.168.1.33:63286 a23-12-144-77:https ESTABLISHED
TCP 192.168.1.33:63287 a23-12-144-141:https ESTABLISHED
TCP 192.168.1.33:63289 151.101.248.157:https ESTABLISHED
TCP 192.168.1.33:63290 104.22.19.149:https ESTABLISHED
TCP 192.168.1.33:63293 a23-196-104-19:https ESTABLISHED
TCP 192.168.1.33:63294 server-99-84-221-3:https TIME_WAIT
TCP 192.168.1.33:63298 104.244.42.8:https ESTABLISHED
TCP 192.168.1.33:63302 199.187.193.166:https ESTABLISHED
TCP 192.168.1.33:63303 a104-86-80-239:https ESTABLISHED
TCP 192.168.1.33:63345 server-99-84-185-228:https ESTABLISHED
TCP 192.168.1.33:63415 24.105.29.76:https TIME_WAIT
TCP 192.168.1.33:63420 24.105.29.76:https ESTABLISHED
TCP 192.168.1.33:63429 137.221.106.19:1119 TIME_WAIT
TCP 192.168.1.33:63440 65.55.44.109:https ESTABLISHED

Further, this was posted over a year ago ( Feb 1 2019) I’m sure the dev’s would have discovered what in their software is forcing a (unconfirmed) disconnect in that time and addressed that by now.

40 Mins now. This is the tech support forum right? Can I get some official techsupport please.

Finally. After a lot digging, cross-referencing various netstat, PID entires, and process of elimination, I can confirm that my system still believes it has an ESTABLISHED connection to what can only be determined as the Hearthstone Servers. No thanx to the non-existent techsupport.

So what now? I am connected to the hearthstone servers, but game is still hung?

Still waiting over 22 hrs later. What top notch tech support.

It’s not a bug, Peverin is correct. We actually ran this whole situation by the devs before we posted that on the old forums. That’s where we got the information. Your client is attempting to reconnect, but it has disconnected. This definitely isn’t entirely clear by what’s happening on screen, but we’ve seen these for years and typically work on them until we find the connection error and get it corrected.

For security reasons, we do not post our server IPs or how to find them publically other than the official IPs we use to trace things, as that is the best way to avoid getting DDoSed by someone who decided they were bored. You’re probably connected to our emote server but not the game itself because you dc’d for too long. Are you in a situation where you are getting put back in this game when you log in, or have you successfully quit the game and terminated it? If you’re reconnecting to the game, let me know, that has a slightly different fix.

If it was a temporary issue, but happens regularly, you can try to catch it with a winMTR test which will help us see if there’s packet loss between your house and our servers. If you’re still having this problem, please create a WinMTR test which catches a disconnection. You want to restart the test every 10-15 minutes until you catch one of these problems. Once you’ve caught one red handed, run the test for about 5 more minutes. This will let us look for problems between your house and our servers which may cause this.

If you have problems with posting it due to a link error, go ahead and copy paste this into your next post, and replace “WinMTR goes here” with your test.

~~~~
WinMTR goes here
~~~~

Then why does netstat report it as ESTABLISHED instead of:

CLOSE_WAIT
CLOSED
FIN_WAIT_1
FIN_WAIT_2
LAST_ACK
listEN
SYN_RECEIVED
SYN_SEND
timeD_WAIT

??

This is the whole issue. Why is your game forcing a DC on clients? Everything else about my internet worked fine through out. Only your connection, and more specifically only that one of multiple connections of yours were DC’d. Why just that one? if It was pathing or peer issue, then one would believe that all connections to you would be impacted. but no, it’s just that one while the others were fine. Further my list of 50 some connections were fine (albeit some were local/internal). But only that one single connection of yours DC’d?

I let it sit in game for about 40-50 mins before I took the loss.

This will only really yield traceroute/ping results. It will not show WHAT is causing the disconnect. If your gateways are overloaded, the quantity of load balancer’s is insufficient, you have a bad switch, or port, or something is amiss in the code, this tool will not show that. It also seems very coincidental that this disconnection issue is (supposedly) something external to Blizzard each and every time, and each and every time it occurs just as a player is playing a card (hence the hovering card) It’s not like someone could D/C as a result of something external to Blizzard while say emoting, or attacking, or drawing/discarding. It only seems to randomly occur when someone is playing a card. Why is that?

There seems to be some confusion here about the purpose of the Technical Support forums. We are not developers. We are support agents. If you don’t want to troubleshoot or would like to instead see something changed, then you can submit a bug report at the appropriate forums, or a suggestion in General Discussion. We do not field either of these in the Customer Support forums. As I am not a developer, I’m not going to be able to continue to field all of the questions you have about the inner workings of the game.

I’m here to help you prevent further disconnections if possible, and the point of requesting that test is so that I can try to find the cause of the disconnection which triggered this behavior, as it has valuable packet loss information. That is the cause. The game client behavior is secondary and not something we work on in this forum as we don’t work directly with the devs for the purpose of suggestions or bug reporting. They’ve got a squad that combs the other forums I mentioned for feedback so they can present that info in meetings.

If you’d like further help, please follow the instructions for the winMTR. If not, you’re welcome to post on those other forums.