It’s totally irritating -,-
I see “game completed and recorded! Restart Hearthstone to continue.” after every finished game.
This game has been discouraging me for over a week.
We need more reports and tests to determine the common issue causing this problem. Please include the WinMTR test as requested above if at all possible. Without this information, we’re unable to see what the issue is and if we’re seeing a common peering issue across all the tests. It’s greatly appreciated if this information can be gathered so that we can compare the tests!
Yeah, sure. This is a 30 minutes test while I am playing HS. I am from Turkey, my internet is totally fine, I have no problems in apps or games other than Hearthstone. Thanks.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Tenda.Home - 1 | 3453 | 3448 | 1 | 9 | 572 | 3 |
|212.156.201.178.static.turktelekom.com.tr - 1 | 3457 | 3453 | 5 | 16 | 626 | 8 |
| 81.212.2.223.static.turktelekom.com.tr - 1 | 3464 | 3462 | 6 | 15 | 399 | 10 |
|03-afyon-t2-2---03-afyon-t3-1.statik.turktelekom.com.tr - 1 | 3468 | 3467 | 6 | 14 | 378 | 10 |
|81.212.218.46.05-amasya-t3-1.06-ulus-t3-7.statik.turktelekom.com.tr - 1 | 3457 | 3453 | 10 | 21 | 629 | 11 |
|06-ebgp-ulus-sr12e-k---06-ulus-xrs-t2-1.statik.turktelekom.com.tr - 1 | 3445 | 3438 | 10 | 20 | 628 | 16 |
|308-buk-col-1---06-ebgp-ulus-sr12e-k.statik.turktelekom.com.tr - 1 | 3457 | 3453 | 26 | 37 | 644 | 28 |
| 83.217.231.25 - 1 | 3457 | 3453 | 27 | 38 | 644 | 34 |
| ae-0.level3.buchro01.ro.bb.gin.ntt.net - 1 | 3449 | 3443 | 35 | 47 | 651 | 37 |
| ae-1-3104.edge7.Amsterdam1.Level3.net - 1 | 3445 | 3438 | 63 | 76 | 496 | 65 |
| BLIZZARD-EN.edge7.Amsterdam1.Level3.net - 1 | 3457 | 3453 | 63 | 78 | 579 | 65 |
| ae1-br02-eqam1.as57976.net - 1 | 3438 | 3431 | 64 | 83 | 4499 | 106 |
| et-0-0-67-pe01-eqam1.as57976.net - 1 | 3457 | 3453 | 60 | 74 | 686 | 61 |
| 137.221.66.43 - 1 | 3457 | 3453 | 65 | 76 | 682 | 69 |
| 185.60.112.157 - 1 | 3457 | 3453 | 64 | 74 | 485 | 69 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
This is a 50 minutes test. I am from Ukraine. This problem arose after the maintenance of the European server on February 14th. In other games, everything is in order, such a problem only in HS.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router - 0 | 5517 | 5517 | 0 | 0 | 7 | 0 |
| 10.2.21.250 - 0 | 5516 | 5516 | 1 | 30 | 505 | 24 |
| 93.170.216.219 - 0 | 5516 | 5516 | 9 | 35 | 544 | 29 |
| ae3-228.rt.bmb.kiv.ua.retn. net - 0 | 5516 | 5516 | 9 | 39 | 545 | 19 |
| ae4-2.rt.eqx.fkt.de.retn. net - 0 | 5516 | 5516 | 39 | 71 | 556 | 46 |
| pr01.eqfr5.blizzardonline. net - 0 | 5516 | 5516 | 40 | 73 | 553 | 47 |
| ae1-br01-eqfr5.as57976. net - 1 | 5512 | 5511 | 43 | 72 | 591 | 103 |
|et-0-0-2-br01-eqam1.as57976. net - 1 | 5510 | 5509 | 43 | 76 | 1549 | 94 |
|et-0-0-31-pe01-eqam1.as57976. net - 1 | 5512 | 5511 | 44 | 72 | 596 | 55 |
| 185.60.112.157 - 1 | 5512 | 5511 | 44 | 73 | 558 | 109 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
same problem in the EU and Really tired because I am haveing a 5 min logging after that again…suks Norway!
i quit suckstone, because its really irritating… first i discovered this problem about 4-5 month ago, but didnt happen any repair, or update. small indie company… meh…
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
No response from host | 100 | 43 | 0 | 0 | 0 | 0 | 0 |
10.146.0.1 | 0 | 212 | 212 | 1 | 3 | 26 | 2 |
mpts-ss-51.msk.mts-internet.net | 0 | 212 | 212 | 3 | 6 | 35 | 6 |
mag9-cr01-be12.51.msk.mts-internet.net | 0 | 212 | 212 | 3 | 5 | 7 | 4 |
oct-cr03-be1.78.spb.mts-internet.net | 0 | 212 | 212 | 14 | 16 | 23 | 15 |
kivi-cr02-ae8.78.hel.mts-internet.net | 28 | 100 | 72 | 46 | 47 | 52 | 46 |
bro-cr01-be7.135.stk.mts-internet.net | 0 | 212 | 212 | 26 | 29 | 67 | 27 |
tct-cr02-ae6.150.ams.mts-internet.net | 0 | 212 | 212 | 43 | 44 | 56 | 46 |
80.249.208.83 | 0 | 212 | 212 | 44 | 48 | 108 | 45 |
ae1-br02-eqam1.as57976.net | 0 | 212 | 212 | 44 | 49 | 150 | 45 |
et-0-0-67-pe02-eqam1.as57976.net | 0 | 212 | 212 | 44 | 51 | 121 | 47 |
185.60.112.158 | 0 | 212 | 212 | 44 | 46 | 51 | 45 |
Thank you, everyone! We’re getting this over to our tracking and comparing the tests provided to pinpoint the problem. For any new folks on this thread, please continue to provide a WinMTR test as requested above.
this time i was trowen out before entering
|
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.10.1 - 0 | 64 | 64 | 0 | 32 | 2002 | 1 |
81.88.77.67 - 0 | 64 | 64 | 14 | 77 | 2025 | 40 |
81.88.77.65 - 0 | 64 | 64 | 15 | 77 | 2022 | 42 |
ae0.1302.b01-dpu-osl-no.nexthop. no - 0 | 64 | 64 | 16 | 80 | 2030 | 44 |
83.145.7.145 - 0 | 64 | 64 | 14 | 79 | 2030 | 42 |
nlams0003-rc1.ip-only. net - 0 | 64 | 64 | 35 | 97 | 2058 | 72 |
80.249.208.83 - 0 | 64 | 64 | 39 | 103 | 2061 | 87 |
ae1-br02-eqam1.as57976 .net - 0 | 64 | 64 | 33 | 102 | 2061 | 78 |
et-0-0-67-pe02-eqam1.as57976. net - 0 | 64 | 64 | 39 | 105 | 2063 | 71 |
185.60.112.157 - 0 | 64 | 64 | 39 | 100 | 2063 | 78 |
________________________________________________ | ______ | ______ | ______ | ______ | _____ |
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.10.1 - 0 | 1865 | 1865 | 1 | 49 | 2076 | 1 |
81.88.77.67 - 1 | 1835 | 1826 | 8 | 81 | 2125 | 24 |
81.88.77.65 - 1 | 1824 | 1812 | 7 | 82 | 2144 | 25 |
ae0.1302.b01-dpu-osl-no.nexthop. no - 1 | 1818 | 1804 | 8 | 81 | 2140 | 26 |
83.145.7.145 - 1 | 1831 | 1821 | 8 | 83 | 2127 | 26 |
nlams0003-rc1.ip-only. net - 1 | 1809 | 1792 | 27 | 98 | 2199 | 44 |
80.249.208.83 - 1 | 1831 | 1821 | 26 | 106 | 2205 | 42 |
ae1-br02-eqam1.as57976. net - 1 | 1830 | 1820 | 28 | 104 | 2205 | 39 |
et-0-0-67-pe01-eqam1.as57976. net- 1 | 1817 | 1803 | 28 | 105 | 2205 | 43 |
185.60.112.158 - 1 | 1825 | 1813 | 28 | 101 | 2205 | 43 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
same problem here I live in India…
i am glad this problem seems to have good amount of attention
Since the today’s patch, my disconnection problems are gone. Last 10 games there were no disconnections. I am wondering, did servers get maintained or smth like that or not?
EDIT: FALSE ALARM. Today disconnection errors came back again.
Vznikl jiný problém,nelze odeslat pozvánku ke přátelství v mobilní verzi,i když proběhla aktualizace.
problem is still occuring for me while playing in Europe server…
There is WINMTR reports as you suggested so what now??? Any update on situation pls?
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.
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”.
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.
[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