I have 240ms now…lol
does anyone else got the same problem?
2 Likes
Yeah, i ve had about the same all morning. comp was essentially unplayable. I had no issues yesterday playing arcade and the new pve, but the lag was heavy this morning. im going to run a WinMTR now and see if anything fishy shows up.
Now my ping is 20 ms higher than b4 patch…
i see a huge jump in latency in my winmtr but i cant copy and paste it here for some reason…
this is from an official bliz post, since you mentioned 20ms higher
Prior to patch 1.21, Overwatch maintained two estimates for your network quality: RTT and ping. Your RTT (round trip time) was measured as the time between sending a packet to the server and hearing a response, which included some application processing time on both ends. Calculating your ping, on the other hand, required us to timestamp every packet at the exact moment it was sent or received, something that became much more expensive after we patched for Meltdown & Spectre. Without these timestamps, your ping and your RTT are effectively the same value.
Rather than report a less accurate and less stable ping, we opted to merge the ping and RTT stats into the single Latency figure you now see in Advanced Performance Stats. You can expect this Latency number to be 10-20ms more than the ping value we previously displayed (higher if your system isn’t hitting 60FPS consistently). The difference between your old Ping and the new Latency figure is purely due to the missing timestamps, and has no effect on your gameplay. Latency measurement will also be more responsive to changes in network quality – your ping previously was averaged over 15 seconds, which made it hard to notice brief latency spikes. The new value is sampled over the last 3 seconds, and should do a better job of capturing brief hiccups in connectivity.
As a part of this patch, we also disabled displaying the Latency statistic if you’re not in a match. The numbers displayed while out of a match were the last stale values from your previous match and did not reflect your current networking environment.
(We missed including this in our patch notes, sorry for any confusion!)
1 Like
^ Is quote from the previous patch.
This is discussion about this Retribution patch and how the Ping/latency is higher now than it was before Retribution. Did have effect on Gameplay.
Yep, i had an increase of 10 ms after the latency patch ( i changed my internet provider (40 ping on ookla (53ms (ow) and 64 (lol) with my old provider ) now i have (6 ping on ookla, same internet speed, a perfect 100/20) 50 ms ( lol) and 60-65 (ow) , after this patch i have 75-80 ms ow ![:expressionless:](https://d74zh8edaijub.cloudfront.net/en/overwatch/images/emoji/twitter/expressionless.png?v=5" ":expressionless:")
it’s weird.
And as you say, i can totally see the difference.
1 Like
Latency increased by much more than 20 ms after this patch…
2 Likes
will they fix the poblem or not
1 Like
Latency increased from 50ms to 110ms, and it is noticeably laggier. I don’t believe for a second that it was just a number change, there is something actually wrong and it affects multiple people.
5 Likes
same here man and i dont know what to do
1 Like
Please remember everyone, regardless of a new patch or not, high latency is usually some problem with your connection between you and the game server. A connection test such as a WinMTR test can map your specific connection route to the game server and look for problems:
WinMTR instructions:
- Download WinMTR from http://winmtr.net/download-winmtr/ (Console players need a Windows Desktop Computer connected to the same network as their console to do this.)
- Unzip the WinMTR.zip file to the Desktop.
- Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
- Run the WinMTR.exe
- Type the IP address you want to trace in the “Host” field. To get the correct IP you will actually need to open up the game and go Practice Vs AI or Quick Play and if you are on PC hit Ctrl+Shift+N and it will bring up the ingame network diagnostic graph, or go to Video > Options > Display Network Performance Graph if you are on any platform including Console. In the top left corner is the IP address you want to run WinMTR to.
note When looking at the IP it will show up ingame as something like 12.34.56.78:12345. You will want to leave the last 5 digits and the colon at the end off and the IP you want to use is just the 12.34.56.78 - Once you notice the connection issue while playing, play for about 6 more minutes, minimize the game and click on “Stop”.
- Click on “Copy text to clipboard”, then return to this forum thread.
- Type two sets of four squiggly lines and then paste the contents of the WinMTR test between:
~~~~ Paste WinMTR Test Results Here ~~~~
If in the event you can’t even connect to Overwatch and get into any game mode at all, please use one of the following IP addresses based on your geographical region:
- US West - 24.105.30.129
- US Central - 24.105.62.129
- Brazil - 54.207.107.12
- Europe - 185.60.114.159
- Europe - 185.60.112.157
- Korea - 211.234.110.1
- Taiwan - 203.66.81.98
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 338 | 338 | 0 | 2 | 87 | 1 |
| 10.223.68.1 - 1 | 331 | 329 | 5 | 10 | 119 | 7 |
| 193.198.227.78 - 0 | 338 | 338 | 7 | 12 | 120 | 10 |
| CN-Srce-03-ES.core.carnet.hr - 2 | 323 | 319 | 6 | 12 | 112 | 8 |
| 193.198.228.117 - 0 | 338 | 338 | 7 | 11 | 134 | 10 |
| 172.20.192.1 - 0 | 338 | 338 | 7 | 12 | 113 | 10 |
| 172.20.192.5 - 0 | 338 | 338 | 7 | 12 | 114 | 7 |
| carnet-ias-geant-gw.vie.at.geant.net - 0 | 338 | 338 | 15 | 20 | 118 | 18 |
| ae6.2.mx1.fra.de.geant.net - 0 | 338 | 338 | 33 | 38 | 70 | 40 |
| ae1.mx1.ams.nl.geant.net - 0 | 338 | 338 | 34 | 39 | 142 | 36 |
|nordunet-ias-nordunet-gw.ams.nl.geant.net - 0 | 338 | 338 | 33 | 38 | 72 | 34 |
| 80.249.208.83 - 0 | 338 | 338 | 34 | 39 | 86 | 36 |
| 37.244.10.35 - 0 | 338 | 338 | 34 | 40 | 83 | 37 |
| 37.244.10.103 - 0 | 338 | 338 | 34 | 39 | 79 | 39 |
| 185.60.114.151 - 1 | 335 | 334 | 34 | 52 | 680 | 34 |
| 5.42.168.121 - 0 | 338 | 338 | 34 | 39 | 76 | 43 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider~~~~Suffering this as well.
This happens after every big patch/event I’ve noticed. It happens with the Brigitte it happened with the last summers game, patch then after a few weeks it went back to normal ping.
Half the time I’m getting routed to servers further away from me than usual. (After checking and comparing pings and locations)
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 172.16.0.2 - 0 | 286 | 286 | 0 | 481 | 1220 | 228 |
| rrcs-24-123-250-169.central.biz.rr.com - 0 | 286 | 286 | 0 | 483 | 1228 | 226 |
| 69.23.10.113 - 0 | 286 | 286 | 1 | 490 | 1241 | 250 |
| be30.clmkohpe02r.midwest.rr.com - 1 | 283 | 282 | 5 | 486 | 1212 | 401 |
| be27.clmkohpe01r.midwest.rr.com - 1 | 283 | 282 | 4 | 486 | 1211 | 350 |
| 107.14.17.252 - 1 | 282 | 281 | 20 | 496 | 1241 | 258 |
| unk-426d0588.adelphiacom.net - 1 | 282 | 281 | 18 | 497 | 1237 | 231 |
| 0.ae1.pr1.chi10.tbone.rr.com - 0 | 286 | 286 | 14 | 499 | 1257 | 241 |
| 24.27.236.201 - 1 | 279 | 277 | 15 | 492 | 1220 | 343 |
| TenGE0-1-0-17.br02.hkg12.pccwbtn.net - 0 | 280 | 280 | 216 | 694 | 1418 | 637 |
| amazon.buneth1.br02.hkg12.pccwbtn.net - 0 | 280 | 280 | 215 | 693 | 1406 | 613 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 57 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider~~~~| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| hitronhub.home - 100 | 117 | 1 | 4 | 4 | 4 | 4 |
| 174.115.68.1 - 0 | 578 | 578 | 9 | 33 | 168 | 167 |
| 8081-dgw01.wlfdle.rmgt.net.rogers.com - 0 | 578 | 578 | 6 | 32 | 175 | 169 |
|0-5-0-6-cgw01.wlfdle.rmgt.net.rogers.com - 0 | 578 | 578 | 8 | 32 | 199 | 199 |
| 69.63.249.26 - 0 | 578 | 578 | 25 | 47 | 219 | 219 |
| eqix-dc2.blizzard.com - 1 | 575 | 574 | 0 | 47 | 352 | 210 |
| ae1-br01-eqdc2.blizzardonline.net - 1 | 575 | 574 | 0 | 48 | 333 | 186 |
| et-0-0-2-br01-eqch2.blizzardonline.net - 1 | 547 | 542 | 0 | 93 | 4407 | 64 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 116 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~Your test results are relatively clean, when running the test did you encounter any disconnections or high latency?
Same thing Aerocia? Did you have any disconnections during the course of the test. Remember it is important to catch the disconnection while the test is running.
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| www.routerlogin.com - 0 | 816 | 816 | 0 | 0 | 5 | 1 |
| HomeBox - 0 | 816 | 816 | 0 | 1 | 11 | 1 |
| lo0-0.lgnqe30.dk.ip.tdc.net - 1 | 792 | 786 | 19 | 20 | 27 | 20 |
| ae1-0.rdnqe10.dk.ip.tdc.net - 1 | 792 | 786 | 19 | 21 | 83 | 21 |
| ae1-0.khk7nqp7.dk.ip.tdc.net - 1 | 792 | 785 | 23 | 25 | 79 | 35 |
| blizzard-1.equinix-am1.nl-ix.net - 1 | 800 | 796 | 36 | 37 | 48 | 37 |
| 37.244.10.35 - 1 | 800 | 796 | 36 | 37 | 48 | 39 |
| 37.244.10.103 - 1 | 800 | 796 | 36 | 37 | 49 | 37 |
| 185.60.114.171 - 1 | 800 | 796 | 36 | 37 | 49 | 37 |
| 5.42.168.93 - 1 | 800 | 796 | 36 | 37 | 46 | 36 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~
The problem were not apparent in "VS AI" but in retribution and other modes it persisted at 100 ish ping or latency as you call it in this case.Royal Babies, are you only seeing the problems in Retribution or Uprising PvE modes and not ANY PvP modes? If so please follow these instructions: