“sorry, we were unable to log you in.” (time out communicating with blizzard services


#1

I’ve been unable to play Overwatch for the past couple of days. About 4 days ago, every time i’ve logged into Overwatch, i receive this… [“SORRY, WE WERE UNABLE TO LOG YOU IN.” (TIME OUT COMMUNICATING WITH BLIZZARD SERVICES.)]

I have attempted just about every fix I could find, (Clearing DNS, Allowing it through the firewall, checking the game files) but nothing seems to be working. Im honestly lost on what to do at this point. Any help or advice would be greatly appreciated.


#2

same here its been going for weeks


#3

If you’re continuing to have issues connecting after logging in we’ll want to get a traceroute test ran. If you have the option you might want to try testing with a different network. If you have a phone and data plan that supports it we could try a mobile tether for that.


#4

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 *


#5

MTR:
Start: Wed Apr 17 16:05:36 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 0.5 0.6 0.5 0.6 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.5 0.7 0.0
4.|-- 137.221.66.18 0.0% 10 0.6 0.7 0.5 1.2 0.0
5.|-- 137.221.83.66 0.0% 10 30.4 6.7 1.2 30.4 8.6
6.|-- 137.221.65.68 0.0% 10 76.1 12.7 5.6 76.1 22.3
7.|-- 137.221.68.32 0.0% 10 5.5 6.0 5.5 10.4 1.4
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3net 0.0% 10 5.5 5.4 5.3 5.5 0.0
9.|-- 4.68.73.62 0.0% 10 6.2 5.6 5.4 6.5 0.0
10.|-- ae3.kualalumpur1.kua.seabonenet 0.0% 10 187.8 188.5 187.6 194.1 1.9
11.|-- umobile.kualalumpur1.kua.seabonenet 0.0% 10 185.7 188.1 185.6 210.3 7.8
12.|-- 123.136.99.46 0.0% 10 185.7 188.2 185.5 211.2 8.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

17/04/2019 16:05:36 UTC

MTR:
Start: Wed Apr 17 16:05:37 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.3 0.6 0.0 Blizzard 0.0% 10 0.6 1.7 0.5 11.4 3.3
3.|-- 137.221.105.16 0.0% 10 0.8 0.7 0.6 0.9 0.0
4.|-- 137.221.66.18 0.0% 10 0.7 0.7 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 1.2 5.3 0.9 19.9 5.6
6.|-- 137.221.65.68 0.0% 10 6.0 17.2 5.8 88.5 26.1
7.|-- 137.221.68.32 0.0% 10 5.8 5.8 5.6 7.2 0.3
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3net 0.0% 10 5.9 5.6 5.4 5.9 0.0
9.|-- 4.68.73.62 0.0% 10 5.6 5.6 5.4 6.4 0.0
10.|-- ae3.kualalumpur1.kua.seabonenet 0.0% 10 187.7 187.8 187.7 188.4 0.0
11.|-- umobile.kualalumpur1.kua.seabonenet 0.0% 10 185.7 185.6 185.5 185.7 0.0
12.|-- 123.136.99.46 0.0% 10 185.8 186.1 185.6 189.1 1.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

17/04/2019 16:05:37 UTC


Sorry , We were unable to log you Time out communication with blizzard services
#6

Just tried to start up the game once again, but this time on my phones Hotspot. Still nothing, I received the same message as if I was on my home WiFi.

However, I was apple to complete a Traceroute using cmd, here are the results

Tracing route to 24.105.62.129 over a maximum of 30 hops

_ 1 27 ms 4 ms 7 ms homeportal [192.168.1.254] _
_ 2 27 ms 25 ms 24 ms 108-203-104-1.lightspeed.jcsnms.sbcglobal.ne t [108.203.104.1] _
_ 3 20 ms 20 ms 22 ms 99.24.64.158 _
_ 4 26 ms 27 ms 31 ms 99.183.77.126 _
_ 5 29 ms 28 ms 39 ms 12.83.102.17 _
_ 6 35 ms 39 ms 82 ms 12.122.157.6 _
_ 7 33 ms 32 ms 45 ms gar18.attga.ip.att.ne t [12.122.96.89] _
_ 8 33 ms 33 ms 32 ms 12.247.68.74 _
_ 9 97 ms 72 ms 85 ms ae1-br01-eqat2.as57976.ne t [137.221.75.33] _
_ 10 55 ms 58 ms 103 ms et-0-0-4-br02-eqch2.as57976.ne t [137.221.65.46] _
_ 11 140 ms 199 ms 84 ms be2-pe02-eqch2.as57976.ne t [137.221.69.73] _
_ 12 56 ms 56 ms 60 ms 24.105.62.129 _

Trace complete.

In any instance there was a .NET, The T was spaced one spot away from the net, due to not being able to send hyper links

Here are the results for the Looking Glass Test

TRACEROUTE:
traceroute to 45.24.171.116 (45.24.171.116), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.285 ms 0.289 ms 0.291 ms Blizzard(24.105.18.3) 1.342 ms 1.371 ms 1.359 ms
3 137.221.105.12 (137.221.105.12) 0.607 ms 0.708 ms 0.782 ms
4 137.221.66.16 (137.221.66.16) 0.753 ms 0.768 ms 0.774 ms
5 137.221.83.66 (137.221.83.66) 5.900 ms 5.930 ms 5.938 ms
6 137.221.65.68 (137.221.65.68) 5.761 ms 5.929 ms 5.874 ms
7 137.221.68.32 (137.221.68.32) 5.458 ms 5.678 ms 5.693 ms
8 12.245.64.9 (12.245.64.9) 5.796 ms 5.836 ms 5.838 ms
9 cr86.la2ca.ip.att.ne t (12.122.104.78) 39.502 ms 39.170 ms 39.147 ms
10 cr2.dlstx.ip.att.ne t (12.122.2.81) 38.040 ms 44.309 ms 43.766 ms
11 12.122.157.33 (12.122.157.33) 38.424 ms 37.968 ms 40.644 ms
12 * * *
13 * * *
14 99.24.64.161 (99.24.64.161) 61.727 ms 52.192 ms 52.156 ms
15 * * *

18/04/2019 20:08:38 UTC

TRACEROUTE:
traceroute to 45.24.171.116 (45.24.171.116), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.287 ms 0.288 ms 0.290 ms Blizzard(24.105.18.3) 1.161 ms 1.176 ms 1.208 ms
3 137.221.105.12 (137.221.105.12) 0.577 ms 0.678 ms 0.752 ms
4 137.221.66.16 (137.221.66.16) 0.586 ms 0.645 ms 0.667 ms
5 137.221.83.66 (137.221.83.66) 5.812 ms 5.830 ms 5.833 ms
6 137.221.65.68 (137.221.65.68) 21.836 ms 19.611 ms 19.581 ms
7 137.221.68.32 (137.221.68.32) 30.327 ms 30.344 ms 30.345 ms
8 12.245.64.9 (12.245.64.9) 7.280 ms 7.294 ms 7.461 ms
9 cr86.la2ca.ip.att.ne t (12.122.104.78) 41.759 ms 39.936 ms 39.910 ms
10 cr2.dlstx.ip.att.ne t (12.122.2.81) 44.849 ms 43.896 ms 43.875 ms
11 12.122.157.33 (12.122.157.33) 38.450 ms 37.150 ms 37.136 ms
12 * * *
13 99.183.77.129 (99.183.77.129) 42.133 ms 42.104 ms 42.165 ms
14 99.24.64.161 (99.24.64.161) 58.541 ms 52.378 ms 52.637 ms
15 * * *

18/04/2019 20:08:38 UTC

MTR:
Start: Thu Apr 18 20:08:38 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.6 0.5 0.7 0.0
4.|-- 137.221.66.16 0.0% 10 0.5 0.7 0.5 1.5 0.0
5.|-- 137.221.83.66 0.0% 10 5.7 7.5 5.6 23.3 5.5
6.|-- 137.221.65.68 0.0% 10 5.7 5.7 5.6 5.8 0.0
7.|-- 137.221.68.32 0.0% 10 5.6 5.6 5.4 5.9 0.0
8.|-- 12.245.64.9 0.0% 10 5.7 5.7 5.6 5.9 0.0
9.|-- cr86.la2ca.ip.att.ne t 0.0% 10 44.5 41.8 38.2 45.0 2.4
10.|-- cr2.dlstx.ip.att.ne t 0.0% 10 39.8 41.1 37.9 44.9 2.0
11.|-- 12.122.157.33 0.0% 10 39.1 38.9 37.4 40.5 0.7
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 99.24.64.161 0.0% 10 52.9 53.3 52.2 61.0 2.6
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

18/04/2019 20:08:38 UTC

MTR:
Start: Thu Apr 18 20:08:38 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 2.4 0.6 15.5 4.7
3.|-- 137.221.105.12 0.0% 10 0.8 0.7 0.6 0.8 0.0
4.|-- 137.221.66.16 0.0% 10 0.7 0.6 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 6.0 10.2 5.7 32.4 9.4
6.|-- 137.221.65.68 0.0% 10 5.8 5.9 5.8 6.0 0.0
7.|-- 137.221.68.32 0.0% 10 7.9 5.9 5.5 7.9 0.7
8.|-- 12.245.64.9 0.0% 10 5.8 5.9 5.7 6.2 0.0
9.|-- cr86.la2ca.ip.att.ne t 0.0% 10 44.2 42.0 38.4 45.5 2.4
10.|-- cr2.dlstx.ip.att.ne t 0.0% 10 39.1 40.5 37.8 44.0 2.1
11.|-- 12.122.157.33 0.0% 10 38.3 39.1 37.5 40.9 1.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 99.24.64.161 0.0% 10 52.3 54.0 52.3 59.9 2.3
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

18/04/2019 20:08:38 UTC


#7

i tried tethering too but it still doesn’t work


#8

ŊĔȒǾ,

Your Wifi looks slightly unstable, possibly due to the wifi adapter you’re using. Any luck using an ethernet cable? If not, what happens if you download and use a free VPN instead of a mobile hotspot?


#9

Upon using an ethernet cable, i revived the same error message, as well as using multiple free VPNs. I have also tryed using a different usb adapter, but still no luck. This leads me to believe it might be a problem with my game, as other online games work just fine.


#10

Hey ŊĔȒǾ,

Could you try closing the Blizzard app and then deleting the temporary Battle.net files?

If that doesn’t help, let’s run a test to the authentication servers. To do this, download WinMTR and type us.actual.battle.net in the “Host” field. Click start, then run the test for about 20 minutes, then click on Stop and then “Copy text to clipboard” and paste the results here.