Hello :))
So 3 days ago I wanted to get back into overwatch so i opened the game , but when I got to the title screen every time I pressed A to get in the game I got a “login error” and I still do . The login error is BC-152 , I’ve seen a few solutions on reddit and such but none have worked .
Here is a list of the thing I have tried : - Uninstalling and reinstalling the game (I did this 4 times)
- Hard resetting the console
- Unplugging the console
- Unplugging the router
- Reseting the router ( this seemed to be the most successful attempt at getting in the game as it didn’t display the error as soon as I pressed A)
- I also tried a wired connection to the router but that also didn’t work
Also , I forgot to mention that I have this problem on Xbox
If any of you know a solution to this please tell me and if you do not know a solution to this issue could you please leave blizzards contact info in the comment so I can contact them directly .
Please help me out as soon as y’all can :((
This points to it being an issue with your router or the connection in general. Have you consulted your ISP?
Yes i have.They said that my router is kinda weak but it works just fine . I’ve tried other things such as login in from another account , changing the xb1 DNS settings . My NAT type was moderate , which needed to be open , after i refreshed the NAT type it was open but the game still gave me the error. I really don’t know what to do , I literally tried everything .
Not sure what they mean by this. Overwatch does require a steady 60 packets or more per second. If your signal is weak, you’ll have trouble connecting or staying connected.
Hi, what is the best way to strengthen the signal for a steady amount of packets per second?
What I meant is that my router is not that powerful , but it works as it should. I’m going to replace it with a more powerful one but the one I have now is working completely fine . I even have a wired connection .
Since you’re playing on a console the connection troubleshooting is very limited here on the forum. Players on PC will have access to other network tools we can use for troubleshooting.
Please run a Looking Glass test from the browser on your console and post the results here.
http://us-looking-glass.battle.net/
I already did one , but I did not share the outcome . I will do another one and post the details here .
Responding here, in case, there’s any issues with posting the Looking Glass test!
I’ll do the test tomorrow since today was really busy but I’ll keep u up to date with the test results
No rush. Following up in case there’s any issues posting here as a new user.
[The test results (sorry if he photos aren’t clear enough)](http://IMG_3263.HEIC
IMG_3262.HEIC
IMG_3261.HEIC
IMG_3260.HEIC
IMG_3259.HEIC
IMG_3258.HEIC
IMG_3257.HEIC
IMG_3256.HEIC
IMG_3255.HEIC
IMG_3254.HEIC
IMG_3264.HEIC)
(sorry for not sending them earlier) i dunno if you are going to be able to see the photos but i don’t know how to share photos on here
No need for any images. Just copy the text and paste it here. Add spaces to any links to break them so you can post.
K I’ll do that and send u the results.Do i have to do the test on my xbox or can i do it on my computer ?
It’s recommended to run the tests on the device that’s experiencing problems so an accurate reading is provided, but it may help to gather a WinMTR test on the PC as well. Run this test for 5 minutes to the game servers. Copy and paste the text file created and paste it between two ~~~ like so:
~~~
WinMTR Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
TRACEROUTE:
traceroute to 81.196.209.195 (81.196.209.195), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.505 ms 3.492 ms 3.490 ms
2 37.244.24.131 (37.244.24.131) 4.161 ms 4.170 ms 4.194 ms
3 Blizzard Blizzard 4.267 ms 4.311 ms 4.387 ms
4 137.221.66.44 (137.221.66.44) 4.150 ms 4.149 ms 4.148 ms
5 * * *
6 137.221.78.34 (137.221.78.34) 95.191 ms 89.516 ms 89.472 ms
7 xr01.amsterdam.rdsnet.ro (80.249.208.51) 1.355 ms 1.260 ms 1.243 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
02/06/2020 08:42:43 UTC
--------------------
TRACEROUTE:
traceroute to 81.196.209.195 (81.196.209.195), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.301 ms 0.284 ms 0.284 ms
2 37.244.25.2 (37.244.25.2) 0.566 ms 0.651 ms 0.739 ms
3 Blizzard Blizzard 1.481 ms 1.521 ms 1.553 ms
4 137.221.66.32 (137.221.66.32) 1.124 ms 1.144 ms 1.144 ms
5 * * *
6 137.221.65.19 (137.221.65.19) 7.492 ms 7.672 ms 7.677 ms
7 137.221.79.34 (137.221.79.34) 7.675 ms 7.795 ms 7.797 ms
8 xr01.london.rdsnet.ro (195.66.224.46) 46.061 ms 46.076 ms 46.076 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
02/06/2020 08:42:43 UTC
--------------------
PING:
PING 81.196.209.195 (81.196.209.195) 56(84) bytes of data.
--- 81.196.209.195 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
02/06/2020 08:42:43 UTC
--------------------
PING:
PING 81.196.209.195 (81.196.209.195) 56(84) bytes of data.
--- 81.196.209.195 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
02/06/2020 08:42:43 UTC
--------------------
MTR:
Start: Tue Jun 2 08:42:43 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.3 0.0
2.|-- 37.244.24.131 0.0% 10 1.5 0.7 0.5 1.5 0.0
3.|-- Blizzard 0.0% 10 1.1 1.3 1.1 2.4 0.3
4.|-- 137.221.66.44 0.0% 10 7.5 7.3 0.6 60.4 18.8
5.|-- 137.221.78.86 80.0% 10 13592 12517 11443 13592 1519.4
6.|-- 137.221.78.34 0.0% 10 1.3 1.2 1.1 1.4 0.0
7.|-- xr01.amsterdam.rdsnet.ro 0.0% 10 1.4 12.1 1.3 68.4 23.4
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
02/06/2020 08:42:43 UTC
--------------------
MTR:
Start: Tue Jun 2 08:42:43 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 37.244.25.2 0.0% 10 0.7 0.7 0.6 0.8 0.0
3.|-- Blizzard 0.0% 10 1.6 1.4 1.1 1.6 0.0
4.|-- 137.221.66.32 0.0% 10 1.2 1.1 1.0 1.5 0.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.65.19 0.0% 10 59.2 15.5 7.4 59.2 17.7
7.|-- 137.221.79.34 0.0% 10 7.7 7.7 7.6 7.8 0.0
8.|-- xr01.london.rdsnet.ro 0.0% 10 8.4 8.6 8.1 10.3 0.6
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
02/06/2020 08:42:43 UTC
--------------------
These are the results from the looking glass test on the xbox (i’m actually writing this on my xbox lol).I hope the test is helpful and that it helps u find the problem!!!
Falspanac,
I don’t see any glaring problems in this test. Everything that looks odd appears to be mitigation to avoid DDoS attacks. If you’re still having this problem, does linking your xbox account to your battle.net account help?
I don’t know . I’ll try to link my account and tell you if it worked !
Edit: It did not work :((. Is there any way i can get this fixed before the anniversary event ends ? I’ve been having this problem for 2 weeks or so
Falspanac,
Troubleshooting is unfortunately a time intensive process sometimes, and on the forums, you’re likely to only get a reply or two in any given day from us, because we don’t sync up. Beyond what I recommended here, I’d see if you can run it on a different account on that XBox, just for diagnostics’ sake. We also want you to try disconnecting your console from your internet, turning on your phone’s 3g/4g connection, and connecting the console to your phone to see if it lets you log in then. (If you have the option to do this with your phone plan.) If either works, let me know. If that doesn’t work, try contacting support for more rapid help. All this said, it’s possible you’re running into an ISP issue, and if that’s the case, there’s not a whole lot you can do other than use a different network (different ISP or using your phone connection to connect until the ISP problem is resolved.)