Hello, I cannot pass opening screen with hearthstone logo and door. Tried PC/phone/ipad all facing same issue, tried restart PC/game/battlenet log in, none of those works… Could you please investigate please… thanks !
4 Likes
same issue on me when region is America, but when I change into Europe I was able to log in, reinstall right now…
update: reinstall didn’t work
Same for me. I did a bunch of trouble shooting - deleted cache, flush dns, rebooted computer and modem, reinstalled, scan and repair. When I change my region to Europe it goes through without a hitch.
I can’t even open a ticket with blizzard because it will either spin at after selecting “contact us”, or when I finally do get through and add all the requested information it just spins more and finally says “You can’t submit this ticket. An error has occurred. This may be a temporary error, so please try again later”. It’s been doing this for 2 hours now.
I’ve had 2 friends successfully get on, though they live in different states.
An investigation or update would be appreciated.
1 Like
Havent been able to log in for about 4 hours - stuck at the splash screen also. On a desktop
I’ve had the same issue on my Fire tablet since about 3am cst.
Hey y’all,
We have been receiving similar reports from players using Verizon FIOS. If possible, please provide a Looking-Glass report. Click “Copy Results to Clipboard” then type two sets of four squiggly lines and then paste the contents of the test between: ~~~~ Paste LookingGlass Test Results Here ~~~~
In the mean time, try testing another network like a mobile hotspot or a free VPN to see if there’s any improvement.
traceroute to 174.244.224.174 (174.244.224.174), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.337 ms 0.333 ms 0.337 ms
2 24.105.18.130 (24.105.18.130) 0.620 ms 0.759 ms 0.945 ms
3 137.221.105.14 (137.221.105.14) 0.898 ms 0.920 ms 0.987 ms
4 137.221.66.18 (137.221.66.18) 0.735 ms 0.732 ms 0.737 ms
5 137.221.83.82 (137.221.83.82) 772.120 ms 772.151 ms 772.161 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.877 ms 6.004 ms 6.282 ms
8 las-b21-link.telia.net (62.115.178.200) 5.814 ms 5.804 ms 5.803 ms
9 157.130.245.25 (157.130.245.25) 5.727 ms 5.749 ms 7.518 ms
10 * * *
11 230.sub-69-83-16.myvzw.com (69.83.16.230) 106.246 ms 106.348 ms 106.353 ms
12 189.sub-69-82-8.myvzw.com (69.82.8.189) 112.921 ms 112.946 ms 112.950 ms
13 * * *
14 * * *
15 * * *
28/10/2020 21:32:58 UTC
--------------------
MTR:
Start: Wed Oct 28 21:32:58 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.6 0.4 0.3 0.6 0.0
2.|-- 24.105.18.130 0.0% 10 0.9 2.0 0.5 9.1 2.9
3.|-- 137.221.105.14 0.0% 10 1.0 1.2 0.8 3.3 0.7
4.|-- 137.221.66.18 0.0% 10 0.6 2.0 0.4 14.5 4.4
5.|-- 137.221.83.82 0.0% 10 378.1 543.8 74.9 1051. 349.3
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.2 10.3 6.0 25.8 7.6
8.|-- las-b21-link.telia.net 0.0% 10 5.7 6.8 5.6 15.6 3.0
9.|-- 157.130.245.25 0.0% 10 5.8 6.2 5.6 8.4 0.8
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 230.sub-69-83-16.myvzw.com 10.0% 10 104.6 105.8 100.1 109.2 2.7
12.|-- 189.sub-69-82-8.myvzw.com 20.0% 10 108.2 107.7 103.4 112.4 2.8
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
28/10/2020 21:32:58 UTC
--------------------
TRACEROUTE:
traceroute to 173.71.196.159 (173.71.196.159), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.347 ms 0.350 ms 0.354 ms
2 24.105.18.2 (24.105.18.2) 1.124 ms 1.159 ms 1.166 ms
3 137.221.105.10 (137.221.105.10) 1.171 ms 1.176 ms 1.182 ms
4 137.221.66.16 (137.221.66.16) 21.299 ms 21.324 ms 21.329 ms
5 137.221.83.80 (137.221.83.80) 416.252 ms 416.256 ms 635.977 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.827 ms 6.017 ms 6.015 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.581 ms 5.719 ms 5.714 ms
9 ae-1-3501.edge7.LosAngeles1.Level3.net (4.69.219.41) 8.809 ms 5.661 ms 5.616 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 5.562 ms 5.568 ms 5.479 ms
11 ae199-21.CLPPVA-VFTTP-306.verizon-gni.net (100.41.23.103) 106.610 ms 106.756 ms 107.066 ms
12 * * *
13 * * *
14 * * *
15 * * *
28/10/2020 21:58:10 UTC
--------------------
PING:
PING 173.71.196.159 (173.71.196.159) 56(84) bytes of data.
--- 173.71.196.159 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
28/10/2020 21:58:10 UTC
--------------------
MTR:
Start: Wed Oct 28 21:58:10 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.2 0.6 0.0
2.|-- 24.105.18.2 0.0% 10 0.7 1.0 0.5 3.4 0.7
3.|-- 137.221.105.10 0.0% 10 0.9 1.0 0.8 1.2 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 0.6 0.4 0.8 0.0
5.|-- 137.221.83.80 0.0% 10 508.2 584.0 41.2 1377. 437.6
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 17.3 6.0 61.9 23.4
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.6 5.6 5.4 6.1 0.0
9.|-- ae-1-3501.edge7.LosAngeles1.Level3.net 0.0% 10 6.5 8.7 5.7 17.2 4.6
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 6.0 5.8 5.7 6.0 0.0
11.|-- ae199-21.CLPPVA-VFTTP-306.verizon-gni.net 10.0% 10 94.6 103.9 94.6 110.7 5.3
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
28/10/2020 21:58:10 UTC
--------------------
I was able to get in but here’s my results
traceroute to 173.66.155.29 (173.66.155.29), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.334 ms 0.382 ms 0.393 ms
2 24.105.18.2 (24.105.18.2) 1.308 ms 1.325 ms 1.346 ms
3 137.221.105.14 (137.221.105.14) 0.913 ms 0.929 ms 0.957 ms
4 137.221.66.22 (137.221.66.22) 0.663 ms 0.683 ms 0.688 ms
5 137.221.83.86 (137.221.83.86) 881.803 ms 881.870 ms 1099.591 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.917 ms 5.969 ms 5.973 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.496 ms 5.511 ms 5.512 ms
9 ae-2-3601.edge7.LosAngeles1.Level3.net (4.69.219.45) 25.681 ms 22.106 ms 22.035 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 5.714 ms 5.710 ms 5.772 ms
11 100.41.25.33 (100.41.25.33) 103.834 ms 103.857 ms 103.859 ms
12 pool-173-66-155-29.washdc.fios.verizon.net (173.66.155.29) 106.174 ms 110.271 ms 110.265 ms
28/10/2020 21:55:53 UTC
--------------------
PING:
PING 173.66.155.29 (173.66.155.29) 56(84) bytes of data.
64 bytes from 173.66.155.29: icmp_seq=1 ttl=48 time=108 ms
64 bytes from 173.66.155.29: icmp_seq=2 ttl=48 time=113 ms
64 bytes from 173.66.155.29: icmp_seq=3 ttl=48 time=115 ms
64 bytes from 173.66.155.29: icmp_seq=4 ttl=48 time=108 ms
--- 173.66.155.29 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 108.459/111.678/115.850/3.122 ms
28/10/2020 21:55:53 UTC
--------------------
MTR:
Start: Wed Oct 28 21:55:53 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.3 0.2 0.5 0.0
2.|-- 24.105.18.130 0.0% 10 0.8 1.9 0.4 13.3 4.0
3.|-- 137.221.105.14 0.0% 10 1.0 0.9 0.6 1.2 0.0
4.|-- 137.221.66.18 0.0% 10 0.7 6.1 0.4 55.8 17.5
5.|-- 137.221.83.82 0.0% 10 199.1 879.9 199.1 1689. 428.7
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 10.5 5.8 28.3 8.5
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.6 5.5 5.4 5.7 0.0
9.|-- ae-2-3601.edge7.LosAngeles1.Level3.net 0.0% 10 7.6 6.2 5.6 7.6 0.7
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 5.7 6.8 5.7 15.6 3.0
11.|-- 100.41.25.31 0.0% 10 101.2 105.8 101.2 111.1 3.2
12.|-- pool-173-66-155-29.washdc.fios.verizon.net 10.0% 10 110.7 112.0 106.0 120.6 4.5
28/10/2020 21:55:53 UTC
--------------------~~~~I cant enter the game , only if i change the region.
TRACEROUTE:
traceroute to 186.223.164.224 (186.223.164.224), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.807 ms 0.825 ms 0.826 ms
2 24.105.18.2 (24.105.18.2) 1.547 ms 1.551 ms 1.552 ms
3 137.221.105.14 (137.221.105.14) 1.552 ms 1.554 ms 1.555 ms
4 137.221.66.22 (137.221.66.22) 1.506 ms 1.521 ms 1.522 ms
5 137.221.83.94 (137.221.83.94) 43.119 ms 43.135 ms 43.139 ms
6 137.221.65.66 (137.221.65.66) 42.870 ms 42.871 ms 42.857 ms
7 137.221.65.100 (137.221.65.100) 42.819 ms 42.832 ms 42.926 ms
8 137.221.65.49 (137.221.65.49) 42.866 ms 42.868 ms 42.819 ms
9 137.221.75.34 (137.221.75.34) 43.448 ms 43.480 ms 43.437 ms
10 ebt-B57-intl02.atl.embratel.net.br (200.214.14.10) 42.442 ms 46.375 ms 45.707 ms
11 ebt-B12261-tcore01.rjoen.embratel.net.br (200.230.220.221) 154.174 ms 153.731 ms 154.728 ms
12 ebt-B2102-tcore01.rjo.embratel.net.br (200.230.252.158) 158.978 ms 158.001 ms 157.992 ms
13 200.244.19.240 (200.244.19.240) 153.739 ms 153.272 ms 153.233 ms
14 badfa4e0.virtua.com.br (186.223.164.224) 178.159 ms 173.908 ms 173.870 ms
02/11/2020 07:34:08 UTC
MTR:
Start: Mon Nov 2 07:34:08 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 24.105.18.2 0.0% 10 6.5 1.2 0.4 6.5 1.8
3.|-- 137.221.105.14 0.0% 10 0.8 0.9 0.8 1.2 0.0
4.|-- 137.221.66.22 0.0% 10 0.5 4.1 0.3 36.1 11.2
5.|-- 137.221.83.94 0.0% 10 42.6 42.7 42.5 43.1 0.0
6.|-- 137.221.65.66 0.0% 10 42.7 43.0 42.3 46.9 1.3
7.|-- 137.221.65.100 0.0% 10 42.7 54.3 42.5 139.2 30.5
8.|-- 137.221.65.49 0.0% 10 42.7 47.8 42.5 93.8 16.1
9.|-- 137.221.75.34 0.0% 10 42.7 45.5 42.6 64.4 6.9
10.|-- ebt-B57-intl02.atl.embratel.net.br 0.0% 10 45.9 46.7 42.5 49.7 2.4
11.|-- ebt-B12261-tcore01.rjoen.embratel.net.br 0.0% 10 155.7 154.7 153.3 155.8 0.7
12.|-- ebt-B2102-tcore01.rjo.embratel.net.br 0.0% 10 155.3 157.8 154.5 160.9 2.0
13.|-- 200.244.19.240 0.0% 10 153.4 153.2 153.0 153.5 0.0
14.|-- badfa4e0.virtua.com.br 0.0% 10 194.4 190.7 154.1 221.2 23.4
02/11/2020 07:34:08 UTC
Thank you for including the looking glass tests here everyone! Checking on the tests so far, it is showing loss on the ISP’s peering as it makes it’s way back to the home connect. This should generally indicate a connection routing issue that will need to be addressed by the internet provider.
11.|-- 230.sub-69-83-16.myvzw.com
10.0% 10 104.6 105.8 100.1 109.2 2.7
12.|-- 189.sub-69-82-8.myvzw.com
11.|-- ae199-21.CLPPVA-VFTTP-306.verizon-gni.net
12.|-- pool-173-66-155-29.washdc.fios.verizon.net
With the tests showing the packet loss on the ISP’s peering, an alternative connection or VPN should work around the issue.
We strongly recommend to contact Verizon with these looking glass tests to have them look into the packet loss issues if the VPN or alternative connection seems to have worked. In these situations, we can gather data for our network team, but our team and Blizzard has no control over verizon’s peering. These tests are purely to help gather data and track the issue for better communication if its needed.
@Filekko, it looks like you’re on NET Virtua here. This thread is specifically to track Verizon login. Could you start your own thread or contact support directly?