Earlier just before the new update the game had been running completely fine, although my computer is a tad old so I have to run Overwatch on low graphics for the game to not crash, but in any case it still was playable yet after I downloaded the new update it just opens up, works for a few seconds and crashes,
I’ve tried scanning and repairing multiple times yet it just refuses to work so im kinda out of ideas at this point.
1 Like
For a good while after the update the servers were unstable. A dev posted that after a crash in the servers they also ran some fixes so might be related.
ooh thanks for the help, I hadn’t heard about that earlier. It could possibly be the problem as I can’t see what else could have caused the crashing.
I’m having the same problem here,i think the fault is the new menù locked in 60 fps.I have to run Overwatch with low settings too and normally i have to try 3/4 times to enter into the game before everything starts to work well,but after the update i can’t even enter.Hoping Blizzard makes a disable menu option.
Heya Outback,
Sorry to hear the game is disconnecting! So we may better assist you, please update the thread with a winMTR file.
Once you have the tool installed, please use CTRL+SHIFT+N to open NetGraph (after joining a quick play or other similar game mode) and grab the server IP. Continue running the winMTR tool until the disconnection happens so we can ensure it records the problem.
Once you have it, post the results here! Be sure to use quotes, it should look like this once it’s posted.
I’m not too sure if I can get the server IP as my game crashes before I can join any game mode.
Use the IP that is closest to your region/area of the country.
If our servers are down, or you are unable to launch the game, use the IPs in this list to run your test.
Region IP Address The Americas 24.105.30.129 (US West) 24.105.62.129 (US Central) Brazil (Americas) 54.207.107.12 Europe 185.60.114.159 185.60.112.157 Korea 211.234.110.1 Taiwan 203.66.81.98
Hopefully I got this right,
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 99 | 93 | 1 | 7 | 7 | 7 | 7 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
|basl-core-2a-xe-304-0.network.virginmedia. net - 3 | 406 | 394 | 10 | 16 | 44 | 16 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| m686-mp2.cvx1-b.lis.dial.ntli. net - 2 | 427 | 420 | 14 | 21 | 74 | 22 |
| 213.46.175.254 - 3 | 411 | 400 | 14 | 21 | 61 | 20 |
| ae1-br01-eqld5.as57976. net - 7 | 358 | 334 | 21 | 31 | 173 | 28 |
| et-0-0-2-br02-eqpa4.as57976. net - 4 | 398 | 384 | 22 | 44 | 2367 | 23 |
| be2-pe02-eqpa4.as57976. net - 2 | 423 | 415 | 21 | 28 | 66 | 23 |
| 185.60.114.159 - 0 | 453 | 453 | 19 | 26 | 102 | 21 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Heya Outback,
Looks like you got it! Going over the report I’m noticing some packet loss that gets increasingly worse as the signal progresses through the ISP network. Would it be at all possible to test this by temporarily connecting through a mobile hotspot?
Of course this is just a test measure. I would basically just set it up, login, connect to a training map temporarily as a test, then disconnect the hotspot. That way you don’t have to worry about running up your data plan.
Let us know if this works for you.
Yeah, that sounds good to me!
Hey. I’m having the exact same problems since update on my PS4 Pro
I’ve had issue for 2 weeks now. When I play on a VPN I Don’t get Disconeccted. Please help. Comcast says there are no issues and I have made 7 calls replaced the modem 2 Techs out to the house and Tier2 twice. All saying no problems.
PLEASE HELP! THANKS IN ADVANCE!!!
TRACEROUTE:
traceroute to 50.196.153.222 (50.196.153.222), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.990 ms 0.991 ms 0.993 ms Blizzard(24.105.18.3) 0.995 ms 1.815 ms 1.876 ms
3 137.221.105.16 (137.221.105.16) 0.989 ms 1.836 ms 1.870 ms
4 137.221.66.18 (137.221.66.18) 1.813 ms 1.815 ms 1.825 ms
5 137.221.83.66 (137.221.83.66) 6.292 ms 6.313 ms 6.319 ms
6 137.221.65.68 (137.221.65.68) 6.196 ms 5.864 ms 5.853 ms
7 137.221.68.32 (137.221.68.32) 5.699 ms 5.813 ms 5.946 ms
8 te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcast.net (23.30.206.153) 5.819 ms 5.834 ms 5.915 ms
9 be-11545-cr02.losangeles.ca.ibone.comcast.net (68.86.84.233) 8.197 ms 8.216 ms 7.538 ms
10 be-11525-cr01.9greatoaks.ca.ibone.comcast.net (68.86.84.150) 14.214 ms 13.266 ms 14.682 ms
11 be-7922-ar01.hayward.ca.sfba.comcast.net (68.86.94.154) 13.596 ms 13.660 ms 13.935 ms
12 be-399-rar01.hayward.ca.sfba.comcast.net (68.86.143.90) 13.553 ms 13.727 ms 13.717 ms
13 162.151.79.154 (162.151.79.154) 14.805 ms 14.823 ms 14.824 ms
14 lag-2-acr09.sanjose.ca.sfba.comcast.net (162.151.30.234) 14.130 ms 14.164 ms 14.285 ms
15 50-196-153-222-static.hfc.comcastbusiness.net (50.196.153.222) 27.723 ms 25.554 ms 30.204 ms
19/04/2019 11:46:45 UTC
PING:
PING 50.196.153.222 (50.196.153.222) 56(84) bytes of data.
64 bytes from 50.196.153.222: icmp_seq=1 ttl=49 time=29.8 ms
64 bytes from 50.196.153.222: icmp_seq=2 ttl=49 time=23.4 ms
64 bytes from 50.196.153.222: icmp_seq=3 ttl=49 time=34.6 ms
64 bytes from 50.196.153.222: icmp_seq=4 ttl=49 time=27.8 ms
— 50.196.153.222 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 23.404/28.955/34.677/4.049 ms
19/04/2019 11:46:45 UTC
MTR:
Start: Fri Apr 19 11:46:45 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0 Blizzard 0.0% 10 0.7 3.4 0.5 28.7 8.9
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.18 0.0% 10 0.6 0.6 0.5 0.7 0.0
5.|-- 137.221.83.66 0.0% 10 6.0 19.9 5.7 116.0 34.7
6.|-- 137.221.65.68 0.0% 10 36.3 9.3 5.7 36.3 9.5
7.|-- 137.221.68.32 0.0% 10 5.6 6.4 5.4 14.1 2.6
8.|-- te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcast.net 0.0% 10 5.9 5.7 5.6 6.0 0.0
9.|-- be-11545-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 7.4 7.1 6.4 7.8 0.0
10.|-- be-11525-cr01.9greatoaks.ca.ibone.comcast.net 0.0% 10 13.8 14.0 13.3 15.1 0.3
11.|-- be-7922-ar01.hayward.ca.sfba.comcast.net 0.0% 10 13.8 14.0 13.8 14.1 0.0
12.|-- be-399-rar01.hayward.ca.sfba.comcast.net 0.0% 10 13.8 15.0 13.6 22.4 2.8
13.|-- 162.151.79.154 0.0% 10 14.7 14.8 14.7 14.9 0.0
14.|-- lag-2-acr09.sanjose.ca.sfba.comcast.net 0.0% 10 14.3 14.1 14.1 14.3 0.0
15.|-- 50-196-153-222-static.hfc.comcastbusiness.net 0.0% 10 26.9 24.2 22.5 28.0 1.8
19/04/2019 11:46:45 UTC
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| pfsense.bigbrother - 0 | 345 | 345 | 0 | 0 | 4 | 0 |
| 10.1.10.1 - 2 | 330 | 326 | 1 | 7 | 202 | 2 |
| 96.120.88.81 - 0 | 345 | 345 | 9 | 16 | 139 | 14 |
|be-10009-rur01.sanjose.ca.sfba.comcast.net - 0 | 345 | 345 | 10 | 16 | 141 | 17 |
|be-231-rar01.santaclara.ca.sfba.comcast.net - 0 | 345 | 345 | 10 | 19 | 134 | 11 |
|be-3651-cr02.sunnyvale.ca.ibone.comcast.net - 0 | 345 | 345 | 11 | 20 | 461 | 12 |
|be-11025-cr01.9greatoaks.ca.ibone.comcast.net - 0 | 345 | 345 | 12 | 19 | 145 | 17 |
|be-12544-pe01.9greatoaks.ca.ibone.comcast.net - 0 | 345 | 345 | 11 | 19 | 299 | 15 |
| 66.208.216.238 - 0 | 345 | 345 | 11 | 20 | 302 | 21 |
| ae1-br01-eqsv5.as57976.net - 0 | 345 | 345 | 18 | 27 | 148 | 25 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 0 | 345 | 345 | 19 | 38 | 305 | 34 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Can you guys please stop blaming ISPs and look into your patch? I work for an ISP and connected straight into our switching equipment I see no problems with the connection and yet I still have these drop outs playing your game. At home connecting through a different ISP I see the exact same problem. you keep blaming level 3 and yet if I ping the level 3 directly I see no IP fluctuation if I ping your servers routed through level 3 I do see a slight change but this does not happen during the connection loss.
2 Likes
Omg I thought I was the only one having this problem. I tried reinstalling the game, even lowering the resolution and it continues freezing. Most of the times the sound does not work and if I try to look at what’s new it just freezes with the first skin.
At first I thought it was my graphic card but if I’m not alone in this maybe there is some problem with the new patch for people that plays in low graphics and fps
Honestly, what does one man need to do to play a simple event without crashing.
I’m pretty sure that there’ll be a maintenance on the 25th so if lucky it might fix the disconnections.
1 Like
Same problem, keeps randomly crashing
Outback,
Did you end up still having problems? If so, can you run another winMTR?
For the rest of you, please keep in mind that we do not investigate multiple issues of this nature on one thread unless we suspect a common cause. We don’t currently suspect this is the case. If you’re having your own issue, create your own thread with a WinMTR test in the reply. We’ll use that to look for problems.