I have for several months had an issue where i will be able to launch connect to and then enter overwatch only to suddenly have my screen freeze and after roughly 2 minutes i will be kicked from the main menu and the “Lost conncetion to game server” message will appear. I have tried evrything i can think of to fix this, including; Uninstalling and reinstalling, scanning and repairing, using task manager to close battle net, plain old restarting, and even searching for the battle net files in my pc in order to delete them and retry. Nothing works. I am completely stumped and don’t know what to do, the only times i can play the game are right after big patches and then only for one session until the old problem re-emerges. I would be very grateful if anyone could help me out. I have run WinMTR to give anyone trying to help me out some specific info so here that is
It seems that the problem starts here:
|glfd-core-2b-xe-801-0.network.virginmedia.net - 1 | 617 | 616 | 9 | 15 | 486 | 25 |
I would recommend contacting your internet provider and present the problem together with a WinMTR test.
Singlewreck, as Raxr said, there seems to be packet loss at several points along the connection, starting pretty early. The best thing to do would be contacting your internet provider and passing along the WinMTR to them, so they can review your case and make sure everything is working properly.
The thing is, as long as there is packet loss along the connection, we can’t possibly know if there’s anything else that could be causing your issue. Most likely, it’s due to the packet loss.
If you ever connect from another place and the same happens, it would be convenient if you could run a WinMTR from that connection so we can check if there are issues or anything else affecting.
separate problem that i have is i can’t seem to uninstall the blizzard app, i’m trying this to see if that will make any difference to my issues before i contact my ISP
Reinstalling the app shouldn’t really affect connection issues. You can always delete the Blizzard folders; sometimes clearing cache does actually help with some issues.
Everytime that i try to uninstall it i get a message telling me it is still running which doesn’t make sense because I closed everything down before i try
Some Battle.net processes might still be running in the background. I’d suggest opening the Windows Task Manager using the Ctrl+Alt+Delete keys and terminating any currently active Battle.net processes you see there. Usually they’re called ‘Blizzard Battle.net App’ and ‘Blizzard Update Agent’. Try uninstalling afterwards.
I have tried several different things to do with my router and nothing has had an effect, I think that it might be something to do with my PC I’m playing on an HP Pavilion G6-2250SA, I don’t know if my PC no longer meets the base level requirements for Overwatch
A “Lost conncetion to game server” error doesn’t usually have to do with the computer not meeting requirements. It’s more of a connection issue; there are high chances that it’s caused by the packet loss your WinMTR was showing, but it could also be that there are programs in your computer interfering with the connection.
You can see packet loss in here as well. They start on that first node I quoted, and carry on for the rest of the path your connection takes to our servers.
Hi, I get the exact same issue, As soon as I load overwatch I load into a game and then go to around 7fps and then straight after it says “lost connection to the game server” This is really annoying and now I have 12 matches to play with -75% Has anyone found a fix yet?
I would start by following all the steps in this article, including the advanced troubleshooting: battle.net/support/article/99037
If that doesn’t help, we’ll need more data so we can investigate. It would be better if you open your own topic, so we don’t mix up different cases in the same one; it will be easier to follow up for everyone. The data we need is:
Details of issue:
Date/time it started:
City/Country:
Internet Provider:
Traceroute (right after a disconnection or whenever you’re experiencing the issue)
Pathping (right after a disconnection or whenever you’re experiencing the issue)
WinMTR (right after a disconnection or whenever you’re experiencing the issue)
i have now run a path ping and traceroute from the main connection, here are the results:
0 singlewreck [192.168.0.9]
1 routerlogin.net [192.168.0.1]
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 singlewreck [192.168.0.9]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% routerlogin.net [192.168.0.1]
Trace complete. ~~~~
And:
~~~~ Tracing route to 185.60.114.159 over a maximum of 30 hops
1 2 ms 2 ms 2 ms routerlogin.net [192.168.0.1]
2 * * * Request timed out.
3 13 ms 14 ms 19 ms glfd-core-2b-xe-801-0.network.virginmedia.net [80.7.14.17]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 27 ms 19 ms 19 ms manc-ic-1-ae1-0.network.virginmedia.net [62.254.42.242]
8 32 ms 28 ms 32 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
9 32 ms 30 ms 28 ms ldn-b1-link.telia.net [213.248.84.25]
10 25 ms 29 ms 29 ms ldn-bb3-link.telia.net [62.115.114.234]
11 21 ms 26 ms 19 ms ldn-b4-link.telia.net [62.115.134.135]
12 27 ms 24 ms 35 ms blizzard-ic-316507-slou-b1.c.telia.net [62.115.145.217]
13 30 ms 29 ms 19 ms ae1-br01-eqld5.blizzardonline.net [137.221.79.33]
14 ~~~~
The pathping doesn’t go further than your router, and the traceroute shows a lot of nodes that seem to be protected. Maybe another WinMTR would work better.
In any case, previous diagnostics indicated packet loss along the connection, so I would still recommend contacting your internet provider so they can make sure everything is working properly.