problem is still occuring for me while playing in Europe server…
1 Like
There is WINMTR reports as you suggested so what now??? Any update on situation pls?
3 Likes
Ha! You should know by now that Blizzard isn’t exactly caring too much.
Though they should, as until this is fixed, I won’t spend a dime on HS.
4 Likes
I have the same… “We just ran into a network problem as we were loading up all the cards in your collection. Please relaunch Hearthstone to access your collection and resume your duels”. 
2 Likes
Thank you, folks and appreciate the connection tests! We are seeing connection issues with Scandinavia and Blizzard Services that may impact a few of you here. I’ll try and see if we can push this up the ladder and update you all here, but we only have 4 unique WinMTR tests provided. Our network engineers may need more to look into this issue further.
If you are experiencing either one of these errors:
Encountered some network issues while reading your card collection.
Closed - We just ran into a network problem as we were loading up all the cards in your collection. Please relaunch Hearthstone to access your collection and resume your duels!
This is not the same issue as the reports here. Please refer to this forum post, so that we can make sure we are tracking each situation accordingly.
1 Like
[Update] We’re going to see if a reverse test can be run and I’ll follow up as soon as I can here if we can run a successful test. This problem is predominantly happening for the Eastern European region.
We are aware of the issue with Scandanivia. This is being treated separately from this issue at the currently moment. This issue is a common peering node where the problems are happening and it’s impacting multiple Blizzard games.
This is a frustrating issue and we want to pinpoint where the problem is. While the connection tests here are a bit low, we’re not seeing a common issue within the connection tests. For those of you running into the “Game completed and recorded” error, could you include a Looking Glass test? This test is a bit different, but should give us a better idea of the connection route from Blizzard to your device.
For those on mobile devices, this test should be available to run. Copy and paste the text file created and paste it between two ~~~ like so:
~~~
Connection Test Here
~~~
When does this error occur? Does it happen before a match, during the match, or after a match is completed?
Thanks for sticking with us and including the details here! I cannot overstate this enough, your reports are appreciated and helpful for our team to compare all the information gathered 
1 Like
TRACEROUTE:
traceroute to 212.14.0.156 (212.14.0.156), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.772 ms 0.762 ms 0.760 ms
2 37.244.24.131 (37.244.24.131) 0.979 ms 1.064 ms 1.177 ms
3 Blizzard Blizzard 2.697 ms 2.713 ms 2.713 ms
4 137.221.66.44 (137.221.66.44) 1.070 ms 1.072 ms 1.099 ms
5 137.221.78.86 (137.221.78.86) 1.475 ms 1.486 ms 1.487 ms
6 137.221.78.34 (137.221.78.34) 19.114 ms 16.259 ms 16.231 ms
7 * * *
8 * * *
9 212.14.0.156 (212.14.0.156) 20.807 ms 20.811 ms 20.805 ms
02/03/2020 20:40:43 UTC
PING:
PING 212.14.0.156 (212.14.0.156) 56(84) bytes of data.
64 bytes from 212.14.0.156: icmp_seq=1 ttl=245 time=21.5 ms
64 bytes from 212.14.0.156: icmp_seq=2 ttl=245 time=20.6 ms
64 bytes from 212.14.0.156: icmp_seq=3 ttl=245 time=20.5 ms
64 bytes from 212.14.0.156: icmp_seq=4 ttl=245 time=21.3 ms
— 212.14.0.156 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 20.580/21.041/21.531/0.452 ms
02/03/2020 20:40:43 UTC
MTR:
Start: Mon Mar 2 20:40:43 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 1.3 0.0
2.|-- 37.244.24.131 0.0% 10 0.5 0.5 0.4 0.7 0.0
3.|-- Blizzard 0.0% 10 1.1 1.3 1.0 2.4 0.3
4.|-- 137.221.66.44 0.0% 10 0.6 4.1 0.5 35.4 11.0
5.|-- 137.221.78.86 0.0% 10 1.0 1.4 0.9 5.1 1.2
6.|-- 137.221.78.34 0.0% 10 69.8 8.9 1.0 69.8 21.5
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- 212.14.0.156 0.0% 10 20.8 22.8 20.6 40.6 6.2
02/03/2020 20:40:43 UTC
I is happening after every single game, doesn’t matter Battlegrounds or Classic. I’m from Poland, and play on Europe.
1 Like
i starterd having same problem after latest battlegrounds update (dragons) my game need restart saying game recorded restar heartshtone to continue i happens only on my Pc iam from Czechia reinstalling heartshtone dindt help what shoud i do
1 Like
Hello Blizzard,
it spikes the issue. Lately either the issue in this thread occurs or I cannt acces the MODES play (arena and BG) due to network issues. Here my trace to HS:
TRACEROUTE:
traceroute to 81.95.5.41 (81.95.5.41), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.383 ms 0.355 ms 0.353 ms
2 37.244.24.3 (37.244.24.3) 0.766 ms 0.962 ms 1.277 ms
3 Blizzard Blizzard 1.236 ms 1.295 ms 1.356 ms
4 137.221.66.40 (137.221.66.40) 0.899 ms 0.908 ms 0.894 ms
5 137.221.78.82 (137.221.78.82) 1.070 ms 1.070 ms 1.057 ms
6 137.221.78.34 (137.221.78.34) 37.930 ms 34.726 ms 34.676 ms
7 ae4-0.ams10.core-backbonecom (80.249.209.128) 1.268 ms 1.435 ms 1.517 ms
8 ae16-2074.fra10.core-backbonecom (81.95.2.137) 6.654 ms 6.685 ms 6.798 ms
9 ae2-2001.nbg30.core-backbonecom (81.95.15.161) 9.581 ms 9.600 ms 9.598 ms
10 ae0-4018.nbg24.core-backbonecom (81.95.15.62) 10.534 ms 13.400 ms 13.408 ms
11 81.95.5.41 (81.95.5.41) 9.345 ms 9.346 ms 9.348 ms
03/03/2020 14:47:00 UTC
PING:
PING 81.95.5.41 (81.95.5.41) 56(84) bytes of data.
64 bytes from 81.95.5.41: icmp_seq=1 ttl=54 time=9.25 ms
64 bytes from 81.95.5.41: icmp_seq=2 ttl=54 time=9.28 ms
64 bytes from 81.95.5.41: icmp_seq=3 ttl=54 time=9.26 ms
64 bytes from 81.95.5.41: icmp_seq=4 ttl=54 time=9.26 ms
— 81.95.5.41 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 9.257/9.268/9.281/0.096 ms
03/03/2020 14:47:00 UTC
MTR:
Start: Tue Mar 3 14:46:59 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 37.244.24.3 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- Blizzard 0.0% 10 1.2 1.1 1.0 1.3 0.0
4.|-- 137.221.66.40 0.0% 10 0.9 2.2 0.6 15.8 4.7
5.|-- 137.221.78.82 0.0% 10 27.3 3.7 0.9 27.3 8.3
6.|-- 137.221.78.34 0.0% 10 1.1 4.5 1.0 34.6 10.6
7.|-- ae4-0.ams10.core-backbonecom 0.0% 10 3.0 1.5 1.2 3.0 0.5
8.|-- ae16-2074.fra10.core-backbonecom 0.0% 10 6.6 7.6 6.5 14.4 2.4
9.|-- ae2-2001.nbg30.core-backbonecom 0.0% 10 9.6 9.6 9.4 9.8 0.0
10.|-- ae0-4018.nbg24.core-backbonecom 0.0% 10 10.4 10.9 10.2 12.6 0.7
11.|-- 81.95.5.41 0.0% 10 9.4 9.4 9.3 9.4 0.0
03/03/2020 14:46:59 UTC
and to BNET Auth:
TRACEROUTE:
traceroute to 81.95.5.41 (81.95.5.41), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.345 ms 0.330 ms 0.330 ms
2 37.244.24.3 (37.244.24.3) 0.591 ms 0.716 ms 0.779 ms
3 Blizzard Blizzard 1.015 ms 1.053 ms 1.129 ms
4 137.221.66.40 (137.221.66.40) 1.442 ms 1.457 ms 1.457 ms
5 137.221.78.82 (137.221.78.82) 1.456 ms 1.454 ms 1.454 ms
6 137.221.78.34 (137.221.78.34) 1.187 ms 1.442 ms 1.385 ms
7 ae4-0.ams10.core-backbonecom (80.249.209.128) 1.346 ms 1.575 ms 1.549 ms
8 ae16-2074.fra10.core-backbonecom (81.95.2.137) 6.564 ms 6.869 ms 6.859 ms
9 ae2-2001.nbg30.core-backbonecom (81.95.15.161) 9.734 ms 9.749 ms 9.587 ms
10 ae0-4018.nbg24.core-backbonecom (81.95.15.62) 10.975 ms 11.534 ms 10.700 ms
11 81.95.5.41 (81.95.5.41) 9.321 ms 9.352 ms 9.345 ms
03/03/2020 14:50:55 UTC
MTR:
Start: Tue Mar 3 14:50:55 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 37.244.24.3 0.0% 10 0.5 0.7 0.5 2.8 0.6
3.|-- Blizzard 0.0% 10 2.5 1.3 1.0 2.5 0.3
4.|-- 137.221.66.40 0.0% 10 0.7 4.3 0.5 25.1 8.3
5.|-- 137.221.78.82 0.0% 10 1.0 1.3 1.0 4.2 0.8
6.|-- 137.221.78.34 0.0% 10 1.2 1.3 1.0 2.7 0.5
7.|-- ae4-0.ams10.core-backbonecom 0.0% 10 1.7 1.6 1.1 3.9 0.7
8.|-- ae16-2074.fra10.core-backbonecom 0.0% 10 6.6 9.3 6.5 29.7 7.2
9.|-- ae2-2001.nbg30.core-backbonecom 0.0% 10 9.6 9.5 9.4 9.7 0.0
10.|-- ae0-4018.nbg24.core-backbonecom 0.0% 10 10.4 11.1 10.2 14.4 1.5
11.|-- 81.95.5.41 0.0% 10 9.4 9.4 9.3 9.5 0.0
03/03/2020 14:50:55 UTC
1 Like
TRACEROUTE:
traceroute to 178.255.168.24 (178.255.168.24), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.472 ms 0.474 ms 0.472 ms
2 37.244.24.3 (37.244.24.3) 1.216 ms 1.247 ms 1.263 ms
3 Blizzard Blizzard 1.253 ms 1.246 ms 1.330 ms
4 137.221.66.46 (137.221.66.46) 1.215 ms 1.202 ms 1.201 ms
5 137.221.78.80 (137.221.78.80) 6.664 ms 6.682 ms 6.683 ms
6 137.221.65.28 (137.221.65.28) 6.386 ms 6.391 ms 6.370 ms
7 137.221.80.32 (137.221.80.32) 6.498 ms 6.407 ms 6.912 ms
8 * * *
9 92.62.238.254 (92.62.238.254) 27.739 ms 27.066 ms 27.043 ms
10 nat-24.starnet.cz (178.255.168.24) 17.316 ms 17.304 ms 17.217 ms
03/03/2020 15:20:54 UTC
PING:
PING 178.255.168.24 (178.255.168.24) 56(84) bytes of data.
64 bytes from 178.255.168.24: icmp_seq=1 ttl=49 time=17.1 ms
64 bytes from 178.255.168.24: icmp_seq=2 ttl=49 time=17.0 ms
64 bytes from 178.255.168.24: icmp_seq=3 ttl=49 time=17.3 ms
64 bytes from 178.255.168.24: icmp_seq=4 ttl=49 time=17.0 ms
— 178.255.168.24 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 17.080/17.173/17.332/0.138 ms
03/03/2020 15:20:54 UTC
MTR:
Start: Tue Mar 3 15:20:54 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.6 0.5 0.4 0.8 0.0
3.|-- Blizzard 0.0% 10 1.1 1.1 1.0 1.4 0.0
4.|-- 137.221.66.46 0.0% 10 0.8 0.7 0.6 0.9 0.0
5.|-- 137.221.78.80 0.0% 10 6.5 6.3 6.2 6.5 0.0
6.|-- 137.221.65.28 0.0% 10 6.4 9.4 6.2 37.5 9.8
7.|-- 137.221.80.32 0.0% 10 6.6 12.7 6.3 47.4 13.9
8.|-- starnet.peering.cz 10.0% 10 20.2 21.2 16.9 24.5 2.4
9.|-- 92.62.238.254 0.0% 10 200.1 37.8 17.7 200.1 57.2
10.|-- nat-24.starnet.cz 0.0% 10 17.2 17.2 17.1 17.5 0.0
03/03/2020 15:20:53 UTC
1 Like
TRACEROUTE:
traceroute to 178.255.168.25 (178.255.168.25), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.390 ms 0.373 ms 0.371 ms
2 37.244.24.3 (37.244.24.3) 2.632 ms 2.651 ms 2.714 ms
3 Blizzard Blizzard 1.113 ms 1.158 ms 1.223 ms
4 137.221.66.40 (137.221.66.40) 0.731 ms 0.746 ms 0.747 ms
5 137.221.78.74 (137.221.78.74) 6.586 ms 6.602 ms 6.603 ms
6 137.221.65.28 (137.221.65.28) 6.369 ms 6.357 ms 6.325 ms
7 137.221.80.32 (137.221.80.32) 6.403 ms 6.417 ms 6.416 ms
8 * * *
9 92.62.238.254 (92.62.238.254) 19.950 ms 19.063 ms 19.033 ms
10 nat-25.starnet.cz (178.255.168.25) 18.678 ms 18.682 ms 18.091 ms
03/03/2020 15:40:03 UTC
MTR:
Start: Tue Mar 3 15:40:03 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.5 0.6 0.4 1.1 0.0
3.|-- Blizzard 0.0% 10 2.1 1.2 1.0 2.1 0.0
4.|-- 137.221.66.40 0.0% 10 0.8 6.0 0.5 53.7 16.7
5.|-- 137.221.78.74 0.0% 10 6.2 11.5 6.2 30.8 9.4
6.|-- 137.221.65.28 0.0% 10 6.3 6.4 6.2 6.7 0.0
7.|-- 137.221.80.32 0.0% 10 6.4 6.5 6.4 6.5 0.0
8.|-- starnet.peering.cz 20.0% 10 16.5 20.5 16.5 28.3 3.6
9.|-- 92.62.238.254 0.0% 10 17.6 27.5 17.2 87.4 23.1
10.|-- nat-25.starnet.cz 0.0% 10 17.6 17.7 17.5 18.2 0.0
03/03/2020 15:40:03 UTC
1 Like
Hi, I’m having issues with playing the game using a relatively old phone as a router with an unlimited data plan. All the other games work as normal with decent ping 40-70, depending on the game and I have no issues playing them. I haven’t experienced a single disconnect while playing games on steam. The connection is stable as I described but what happens with hearthstone is it instantly crashes at launch most of the time and barely let’s me play on the hotspot. Approximately 1 in 10 restarts lets me play a match after which it gives me the message I’ve been disconnected and the game has been recorded while I had no reconnecting message or issues during the match. It happens both on my phone and my laptop. As soon as I switch to my limited mobile data plan on my main phone it works as normal. This issue prevents me from playing the game on my laptop as I prefer a bigger screen and my limited data plan is for emergencies only, when the unlimited one has no signal/service. I know the issue is not in the unlimited data plan service, as I’ve played the game on it for a long time. The issue could be the old phone, but that doesn’t explain how I can play all the other games with no issues. It’s quite an inconvenience. Please help.
1 Like
I’m from the UK and have been experiencing this issue for every game as well. Has any solution been found yet?
2 Likes
can i ask what should i do iam really desperate i need help
3 Likes
Still no solution to this.amazing. there is no need for winmtr or glass reports anymore, it is so obvious that there is a problem on your server side. This game is full of crap things in and out.wow.
3 Likes
Almost a month and still no fix (european servers, connection or otherwise)? Quite frustrating to relaunch the game after every single match or even entering crafting mode. I tried to tune my internet connection, but nothing wrong there.
I hope it won´t stay that way for another month 
I like the game, but not in this condition.
2 Likes
UK here, still happening. I tried Asia servers too and the same thing. I get kicked sometimes as HS is loading the main menu or whilst creating a deck etc. Then when I do get into a game it will disconnect straight after so it could be a standard constructed match or a whole game of battlegrounds, it doesn’t DC during the game but always straight after.
Edit: I have even tried starting a game then conceding straight away in case it was a time based thing but the same issue occurs.
Every other internet application, game, consoles, firestick etc all work as they should. Just HS is failing.
5 Likes
Austria here. I still have this problem too. If I remember correctly, the problem started around the time when the Galakrond adventure got released. Also the game seems to update every time I start the battlenet launcher, although it’s not really downloading anyhing. At this point, this really discouraged me from playing the game the last month. Just frustrating having to start the game again after every match. One of the more recent updates just screwed the game up, I am not sure if it was the Galakrond Solo adventure update or the Battlegrounds Dragons update, I think the first one. I remember when Descent of Dragons came out, it still worked flawlessly, so it was one of the updates after that one.
1 Like