Hello everyone, let me just preface this by saying yes I am aware that the game now reports latency time rather than just ping so a 10-20ms increase is to be expected. With that being said, i used to get between 50-70 ping before the change and now my latency tends to be 140 in game. It occasionally drops down close to 100 but never really below that and I can definitely feel the difference in game to the point where I basically just quit playing recently. Trying to climb to masters playing Widow/Mccree and the change just killed me. Widow no fun when you have 140 latency. Ive tried most basic things, flushed dns, closed backround processes, updated drivers, im hardwired and it makes no difference if i plug into the router or straight into the modem results were identical. Any ideas or help would be greatly appreciated.
Hi there,
I know that higher than normal latency is no fun and hope I can help pin it down. To do so, I would like to have you contact us back with a WinMTR and a Looking Glass report. These will help us track the connection from us to you and you to us.
/Nathardrick
Will do as soon as i am home, unfortunately had to leave the house for a bit. Thanks for the swift response.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Brun - 0 | 578 | 578 | 0 | 0 | 14 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
|host-69-144-131-249.bzm-mt.client.bresnan.net - 0 | 578 | 578 | 8 | 11 | 39 | 12 |
|host-69-144-24-28.lar-wy.client.bresnan.net - 0 | 578 | 578 | 8 | 12 | 37 | 12 |
|host-69-144-47-49.sal-co.client.bresnan.net - 0 | 578 | 578 | 45 | 50 | 168 | 51 |
| 96-34-76-114.static.unas.sc.charter.com - 0 | 578 | 578 | 45 | 50 | 167 | 46 |
| 69.145.174.134 - 0 | 578 | 578 | 45 | 53 | 74 | 57 |
| bbr02snjsca-bue-2.snjs.ca.charter.com - 0 | 578 | 578 | 74 | 82 | 175 | 82 |
| prr01snjsca-bue-6.snjs.ca.charter.com - 0 | 578 | 578 | 74 | 79 | 174 | 89 |
| eqix-ix-sv1.blizzard.com - 0 | 578 | 578 | 74 | 78 | 173 | 76 |
| ae1-br01-eqsv5.blizzardonline.net - 0 | 578 | 578 | 75 | 79 | 211 | 90 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| be2-pe02-eqla1.blizzardonline.net - 0 | 578 | 578 | 81 | 85 | 185 | 82 |
| lax-eqla1-ia-bons-03.blizzardonline.net - 0 | 578 | 578 | 83 | 87 | 172 | 90 |
| 24.105.30.129 - 0 | 578 | 578 | 81 | 86 | 113 | 97 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
TRACEROUTE:
traceroute to 184.166.8.246 (184.166.8.246), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.347 ms 0.348 ms 0.330 ms
2 37.244.22.131 (37.244.22.131) 0.666 ms 0.723 ms 0.825 ms
3 24.105.30.158 (24.105.30.158) 2.347 ms 2.356 ms 2.359 ms
4 137.221.66.4 (137.221.66.4) 1.797 ms 1.807 ms 1.885 ms
5 137.221.68.72 (137.221.68.72) 1.568 ms 1.580 ms 1.583 ms
6 137.221.65.7 (137.221.65.7) 8.504 ms 8.379 ms 8.362 ms
7 137.221.70.32 (137.221.70.32) 8.235 ms 8.233 ms 8.231 ms
8 eqix-sv1.chartercom.com (206.223.116.204) 8.323 ms 8.331 ms 8.330 ms
9 * * *
10 * * *
11 69.145.174.135 (69.145.174.135) 36.826 ms 36.786 ms 36.758 ms
12 host-69-144-47-34.sal-co.client.bresnan.net (69.144.47.34) 43.150 ms 43.198 ms 43.189 ms
13 host-69-144-24-27.lar-wy.client.bresnan.net (69.144.24.27) 43.398 ms 43.409 ms 43.459 ms
14 * * *
15 * * *
14/07/2018 19:00:43 UTC
--------------------
TRACEROUTE:
traceroute to 184.166.8.246 (184.166.8.246), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.985 ms 0.984 ms 0.964 ms
2 37.244.23.130 (37.244.23.130) 1.305 ms 1.345 ms 1.511 ms
3 24.105.62.146 (24.105.62.146) 1.999 ms 2.716 ms 2.731 ms
4 137.221.66.8 (137.221.66.8) 2.795 ms 2.804 ms 2.885 ms
5 137.221.69.66 (137.221.69.66) 4.099 ms 4.113 ms 4.116 ms
6 137.221.65.11 (137.221.65.11) 49.722 ms 49.280 ms 49.268 ms
7 137.221.70.32 (137.221.70.32) 48.979 ms 48.913 ms 48.933 ms
8 eqix-sv1.chartercom.com (206.223.116.204) 49.558 ms 49.424 ms 49.411 ms
9 * * *
10 * * *
11 69.145.174.135 (69.145.174.135) 76.773 ms 76.871 ms 76.736 ms
12 host-69-144-47-34.sal-co.client.bresnan.net (69.144.47.34) 83.126 ms 83.123 ms 83.114 ms
13 host-69-144-24-27.lar-wy.client.bresnan.net (69.144.24.27) 83.952 ms 84.091 ms 84.087 ms
14 * * *
15 * * *
14/07/2018 19:00:43 UTC
--------------------
PING:
PING 184.166.8.246 (184.166.8.246) 56(84) bytes of data.
--- 184.166.8.246 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
14/07/2018 19:00:43 UTC
--------------------
PING:
PING 184.166.8.246 (184.166.8.246) 56(84) bytes of data.
--- 184.166.8.246 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
14/07/2018 19:00:43 UTC
--------------------
MTR:
Start: Sat Jul 14 19:00:43 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.6 0.0
2.|-- 37.244.23.130 0.0% 10 0.4 0.5 0.4 0.8 0.0
3.|-- 24.105.62.146 0.0% 10 1.6 1.6 1.2 3.7 0.6
4.|-- 137.221.66.8 0.0% 10 2.1 2.0 1.9 2.1 0.0
5.|-- 137.221.69.66 0.0% 10 7.0 15.6 1.8 115.4 35.4
6.|-- 137.221.65.11 0.0% 10 49.0 49.0 48.9 49.1 0.0
7.|-- 137.221.70.32 0.0% 10 48.9 49.0 48.8 49.6 0.0
8.|-- eqix-sv1.chartercom.com 0.0% 10 49.7 49.6 49.3 50.1 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 69.145.174.135 0.0% 10 76.8 77.1 76.8 77.7 0.0
12.|-- host-69-144-47-34.sal-co.client.bresnan.net 0.0% 10 83.4 83.9 83.0 90.1 2.2
13.|-- host-69-144-24-27.lar-wy.client.bresnan.net 0.0% 10 83.9 84.0 83.7 84.3 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14/07/2018 19:00:43 UTC
--------------------
MTR:
Start: Sat Jul 14 19:00:43 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- 37.244.22.131 0.0% 10 0.5 1.3 0.4 6.5 1.8
3.|-- 24.105.30.158 0.0% 10 1.7 1.2 0.8 2.3 0.3
4.|-- 137.221.66.4 0.0% 10 1.6 1.6 1.5 2.0 0.0
5.|-- 137.221.68.72 0.0% 10 1.2 4.2 1.2 25.6 7.6
6.|-- 137.221.65.7 0.0% 10 8.4 8.4 8.3 8.7 0.0
7.|-- 137.221.70.32 0.0% 10 8.3 8.5 8.2 9.1 0.0
8.|-- eqix-sv1.chartercom.com 0.0% 10 8.3 8.4 8.2 8.7 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 69.145.174.135 0.0% 10 48.7 38.4 36.8 48.7 3.7
12.|-- host-69-144-47-34.sal-co.client.bresnan.net 0.0% 10 43.2 43.3 43.1 44.2 0.0
13.|-- host-69-144-24-27.lar-wy.client.bresnan.net 0.0% 10 43.5 43.5 43.4 43.9 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14/07/2018 19:00:43 UTC
--------------------Same problem constant lag spikes,friends from around the world reporting the same
on my mtr massive spikes on ping to et-0-0-3-br02-eqam1.blizzardonline.net
2443ms Highest spike
NO OTHER TRACE HOPS HAVE HIGH PING, its your servers blizzard
Same here, just tried PingPlotter. The latency starts at the blizzard hop. Game is nearly unplayable. I just log on to see if it’s any better.
Hey there,
This WinMTR test wasn’t run to the correct server IP. Can you follow the instructions in the WinMTR article for how to get the IP from in game? The looking glass looks fine - we just need to see your actual path from your house to whatever server you’re having high latency on.
so my server seems to be different every time i join a custom game… Can i start the game, then start the mtr after i know the current server im connected to? The article says to start the mtr THEN launch the game so i just used the west coast server provided in that article. Im just unsure how to know what server to run the mtr if im supposed to start it before im in game… Thanks.
Right, just start the game, connect to a server, then grab the server IP from that game (assuming you’re having bad latency on it.) If you’re not, repeat until you get on to a server with worse latency. Those other steps are more for if you can’t log in or are getting rapidly disconnected. Sorry for the confusion there!
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| Brun - 0 | 533 | 533 | 0 | 0 | 5 | 3 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| host-69-144-131-249.bzm-mt.client.bresnannet - 0 | 533 | 533 | 8 | 12 | 39 | 13 |
| host-69-144-24-28.lar-wy.client.bresnannet - 0 | 533 | 533 | 8 | 13 | 47 | 13 |
| host-69-144-47-49.sal-co.client.bresnannet - 0 | 533 | 533 | 45 | 50 | 74 | 48 |
| 96-34-76-114.static.unas.sc.chartercom - 0 | 533 | 533 | 45 | 50 | 92 | 47 |
| 69.145.174.134 - 0 | 533 | 533 | 45 | 54 | 80 | 63 |
| bbr02snjsca-bue-2.snjs.ca.chartercom - 0 | 533 | 533 | 74 | 82 | 103 | 80 |
| prr01snjsca-bue-6.snjs.ca.chartercom - 0 | 533 | 533 | 73 | 78 | 103 | 73 |
| eqix-ix-sv1.blizzardcom - 0 | 533 | 533 | 73 | 78 | 100 | 74 |
| ae1-br01-eqsv5.blizzardonlinenet - 0 | 533 | 533 | 74 | 79 | 201 | 76 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
My ping in game was 95-100ish but stable which is best case for me. east servers seem to be 140ish.
i have the same thing i use to play on 76 80 all the time . but not i am on 160-170 stable ?! i am like maybe my internet and then i played like so many other games my ping was like 60-70 again and now i am here and i see not only me have this kinda of problem and tried everything to fix but there nothing i can do TBH please fix it fast as possible Ty i love overwatch please ;(
i have the same thing i use to play on 76 80 all the time . but not i am on 160-170 stable ?! i am like maybe my internet and then i played like so many other games my ping was like 60-70 again and now i am here and i see not only me have this kinda of problem and tried everything to fix but there nothing i can do TBH please fix it fast as possible Ty i love overwatch please ;(
again today lag spikes …
So it’s been a few days since Stinky Whisper posted his stats. Please help him, I miss playing with him.
Soooooooooooooooooooo…we just let this move off and die?
So you ask the man to do some steps, he does them and then you go quiet? Even a message of this really isn’t our issue or we don’t have a solutions would be nice.
But silence?! that just looks bad.
I want my friend back.
Hey again,
Sorry for the delays, we had a major patch with WoW the other day and I missed your reply in the chaos until your friend replied to me directly. That’s totally my bad.
That said, there’s nothing in your WinMTR that shows why you should be getting higher latency. With those numbers, you should be right around 70 ms. Is the 140 ms constant for you, or just spiky? Could you email us an MSinfo file? Our files email is techinfo@blizzard.com and you can use the subject ATTN: Drakuloth - stinkywhispr latency problems. If you can do that and reply directly to this message, I’ll give it a look and see if we can find any reason why this is happening.
Email is sent and my ping rarely ever spikes. It seems stable at 100ish, seemingly west coast, and 140ish, seemingly east coast. Thanks for the help.
Thanks for sending that in! If we’re lucky, I may have found our culprit. You’ve got killer network manager, and it’s somewhat out of date. When that’s the case, the quality of service settings on Killer will sometimes turn down the priority on data packets to certain games. Try updating your killer drivers and your killer control center from this link and let me know how things go after. Fingers crossed on this one.
Unfortunately that didn’t seem to change anything:( It was definitely worth a shot though.