Yesterday and once again today I’ve been having very strange lag only in Overwatch that makes it impossible to play the game. My ping will be normal around 40 and then every couple seconds oscillate up to as high as 600-2000 and then come back down causing me to slide around and not be able to shoot anything or play properly. I never can predict when this is going to happen which has caused me to leave a couple of competitive matches. I’ve tried reinstalling Battlenet client and Overwatch and I still get the same issue.
Hey LunarPlains,
If you’ve already tried these steps, then we should run a MTR test so we can pinpoint the problem. I’d suggest avoiding competitive matches to prevent any additional penalties or rating loss.
- Download WinMTR
- 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 ~~~~
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Fios_Quantum_Gateway.fios-router.home - 6 | 206 | 194 | 1 | 126 | 4087 | 3 |
| 24.105.13.15 - 6 | 205 | 193 | 7 | 135 | 4091 | 24 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~It looks like you are getting some latency spikes and packet loss to the modem. Can you try a wired connection from the computer directly to the modem? You may also want to try testing another network like a mobile hotspot to compare the difference.
Part of the problem could also be that I’m getting routed the LA servers when I live on the east coast
Lo mismo me pasa… querido blizzard cada parche nuevo que instalan mi ping incrementa, ya me cambie de compañia de internet porque jugaba con cable hoy estoy con fibra optica: empeze jugando con 38-42 de ping y tras cada parche ha ido incrementado. Hasta el dia de ayer jugaba con 68-72 y ayer ameneci con 90-100 y el detalle parece ser que nunca es problema de sus servidores, si no de mi compañia provedora… anteriormente ya habia abierto un tiquet y habia hecho todas las pruebas que aqui pencionan, donde uno de sus GM me dijo que el problema no eran ustedes si no me internet cuando Overwatch es el unico juego donde tengo este problema de ping, anexo mis resultados de la ultima ves para que vean:
Soy Especialista técnico Rachiomyst. Espero que estas teniendo un buen día y gracias por enviar los archivos. Revise la prueba MTR y la captura de pantalla y honestamente se ve normal. Se que tenias mejor latencia antes, pero no hay perdida de paquetes y los picos de latencia no son suficiente para causar problemas de conexión. Ahora lo que si se ve es en la ruta si sube el promedio a los 50s:
| ipdsl-sin-emiliano-33-l0.uninet.net.mx - 0 | 623 | 623 | 1 | 2 | 50 | 2 |
| bb-dallas-stemmons-7-be12.uninet.net.mx - 0 | 623 | 623 | 53 | 57 | 63 | 55 | <<<
Desde ese punto la latencia sube un poquito, pero no mucho. Al fin te da latencia entre los 60s. En este caso temo decir que nosotros no podemos hacer algo directamente como el aumento de latencia es por la ruta de conexión. Lo mejor será revisar con su proveedor para ver si ellos pueden hacer algo. Indicando que sube la latencia en esa parte de la conexión posiblemente puede ayudar.
Espero que esa información ayuda.
Cuídese.
Hi Zenlaka, same issues from time to time here and getting assigned to different regions.
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 2 | 529 | 523 | 0 | 0 | 1 | 0 |
| 10.0.0.1 - 0 | 553 | 553 | 0 | 0 | 2 | 1 |
| host-168-90-59-158.zaapnet.com.br - 0 | 553 | 553 | 0 | 1 | 3 | 3 |
| host-168-90-56-17.zaapnet.com.br - 0 | 553 | 553 | 1 | 3 | 37 | 4 |
| ldnbt-br-1.visaonet.com.br - 0 | 553 | 553 | 1 | 2 | 20 | 2 |
| 173.186.125.189.static.impsat.net.br - 100 | 112 | 1 | 23 | 23 | 23 | 23 |
| 64.209.11.186 - 0 | 553 | 553 | 18 | 20 | 35 | 19 |
| amazon-com.xe-5-2-1.ar4.gru1.gblx.net - 0 | 553 | 553 | 19 | 20 | 29 | 20 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| 52.93.44.205 - 0 | 553 | 553 | 19 | 26 | 81 | 29 |
| 52.93.146.80 - 0 | 553 | 553 | 22 | 24 | 65 | 24 |
| 52.93.146.38 - 0 | 553 | 553 | 31 | 33 | 52 | 32 |
| 52.93.146.11 - 60 | 155 | 63 | 0 | 946 | 3876 | 3764 |
| 54.240.244.171 - 0 | 553 | 553 | 24 | 24 | 43 | 24 |
| 54.240.244.80 - 0 | 553 | 553 | 29 | 31 | 48 | 32 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 111 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~este el nuevo que acabo de hacer:
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 216 | 216 | 0 | 0 | 3 | 0 |
| ipdsl-sin-emiliano-33-l0.uninet.net.m - 0 | 216 | 216 | 1 | 2 | 35 | 2 |
| bb-dallas-stemmons-7-be12.uninet.net.m - 0 | 216 | 216 | 53 | 57 | 62 | 54 |
|dsl-189-247-127-94-dyn.prod-infinitum.com.m - 0 | 216 | 216 | 53 | 57 | 115 | 55 |
| ae1-br02-eqda6.as57976.ne - 0 | 216 | 216 | 63 | 65 | 179 | 63 |
| et-0-0-2-br02-swlv10.as57976.ne - 0 | 216 | 216 | 63 | 65 | 133 | 64 |
| 137.221.65.122 - 0 | 216 | 216 | 63 | 83 | 387 | 64 |
| et-0-0-2-br01-eqla1.as57976.ne - 7 | 156 | 146 | 64 | 331 | 4806 | 210 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
Lunar,
More likely the problem we pointed out is the reason you’re getting randomly put on the wrong servers. You have an average of 120ms before you even leave your house. Any luck on ethernet? If you’re already on ethernet, power cycle and retry. If the problem persists beyond that, let’s snag a new winMTR while you’re on an ethernet cable.
Hi,
So I tried all that stuff but what seems to have fixed it for me is changing my DNS server from my router default to Google’s Public DNS servers. Other people having the same problem as me could try the same thing.
1 Like
^ No, this is not a solution, this would increase the initial time for resolving but that is immediately cached. I am also having this issue, I assure you it is not my internet, it is not my computer, the PTR worked great, this is very recent and probably has to do with either a update you made between the PTR and live or the latest Windows 10 patch / Nvidia Patch. There are also crazy random IND spikes now as well. Please fix your stuff blizzard.
I can confirm I had the problem a day or two before Live got updated, so it was not the Role Queue patch. Also that it’s not a recent GeForce update because June/July’s update made me drop performance drastically, so I rolled back and I’m currently on May’s version.
I can’t discard WU because I don’t have a system restore from back then, but I’d had loved to test it out.
Changing DNS doesn’t seem to have done anything either, for the record.
Ok what.
Ok What.
WHAT
Changing DNS doesn’t seem to have done anything either, for the record.
I take this back. Changing from 1.1.0.0 to 8.8.8.8, and restarting my router and computer, has brought back my ping back to a steady 130ms, which is even below my usual average.
The ONLY thing I did apart from this was updating my antivirus client (Avast), but I can’t see how this would be related. But I mention it anyways because I’d rather let the technicians decide what’s relevant.
No, I don’t understand it, but I won’t complain. It’s… solved? Seriously? What o_o. It’s COMPLETELY fixed.
Alright, I’ll be bringing this back to my own topic, but at least I’ll leave an explanation here of what I’ve seen from more testing.
- Cloudflare’s DNS (1.1.0.0) was making me get placed in high ping servers.
- Switching to Google’s DNS (8.8.8.8) stopped that, but I started to get occasional lag spikes (kinda like all characters doing Tracer blinks at the same time, lol).
- Using the program DNS Benchmark still placed Cloudflare’s DNS as the fastest (that is why I was using it, after all), but placed OpenDNS second.
- Switching to OpenDNS (208.67.222.220) is giving me the best results. I still get the very rare lag spike, but the difference is as night and day.
But details aside, I’m just happy to be able to play. Thanks for finding this out!
Edit: Can’t double-post in my own topic, so I’ll be adding the closure through an edit.
Yeah, My dns setup is a local DNS MASQ that then gets forwarded to 8.8.8.8 -> 8.8…4.4. I am suffering form the second effect, the lag is ok, CRAZY IND spikes and teleporting. Regardless though, Blizzard needs to get on this, ‘Switch to Google DNS servers’ is not a valid response (not from you, but from the official account). I am a developer, I need my DNS setup for a whole lot of stiff to work, having to switch it every time is kinda ridiculous. I have a cable modem in bridge mode with multiple Ethernet ports that will give unique public ips, so I am going to go attempt to 100% bypass the internal network stack, but I am not optimistic. I should also note Intel has been releases microde updates for their recent debacle, and I have done a recent BIOS upgrade, should not be relevant, this is a 12 core CPU, 64 gig ddr4, 1080TI PC, even a little overhead should not be enough to effect overwatch. best of luck to everyone
Exactly. Take my “advice” with a grain of salt but it personally improved things for me. Blizzard needs to stop saying it’s an ISP issue it’s just dishonest.
If a DNS change fixes the problem, it’s an ISP issue, or if you were already using a third party DNS, with that DNS itself. If you didn’t manually set up a DNS, you get your DNS lookups from your ISP.
Appreciate you letting us know though!
I believe I’m having this issue as well. Ping is normally 56 ms, which is what it sits at roughly until the lag/freeze happens.
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 354 | 354 | 0 | 0 | 2 | 0 |
| cm-1-acr13.arvada.co.denver.comcast.net - 0 | 354 | 354 | 8 | 12 | 25 | 10 |
|ae-113-rur101.arvada.co.denver.comcast.net - 0 | 354 | 354 | 9 | 13 | 44 | 9 |
| ae-21-ar01.denver.co.denver.comcast.net - 0 | 354 | 354 | 10 | 16 | 81 | 12 |
|be-33652-cr02.1601milehigh.co.ibone.comcast.net - 0 | 354 | 354 | 11 | 15 | 27 | 11 |
|be-12124-cr02.dallas.tx.ibone.comcast.net - 0 | 354 | 354 | 24 | 28 | 42 | 30 |
|be-12495-pe03.1950stemmons.tx.ibone.comcast.net - 0 | 354 | 354 | 24 | 27 | 41 | 24 |
| 50.208.232.130 - 0 | 354 | 354 | 24 | 31 | 90 | 27 |
| ae1-br01-eqda6.as57976.net - 0 | 354 | 354 | 38 | 43 | 120 | 40 |
| et-0-0-4-br01-eqch2.as57976.net - 0 | 354 | 354 | 38 | 49 | 298 | 47 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 71 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~Then why was it fixed in a patch? rolls eyes, you need to stop assuming some of your customers are not in high profile tech jobs and just sweeping everything under ‘umm, DNS’. If your system is so heavily propagated on the initial DNS resolve in the first place for server assignment, then that itself is an issue
1 Like
Fact of the matter is Customer Service is only authorized to suggest MTR, DNS and potential fixes for stupid problems. They will always blame the ISP, despite not even having half as many regional hosts as their competitors. Not to mention that the game continues to be entirely unfair and biased towards those with sub 15ms latency, and the skyrocketing number of reports siting unplayable lag.
In my tests, 60ms with a consistent netgraph showed spikes in the thousands on the MTR in the worst column, before getting masked out, and they wouldn’t even acknowledge it because of a previous MTR that was connected to their global IP that showed the latency going away before the masked hops, and a completely different route than the game server.
Even with a consistent netgraph at 60ms, I get constant yellow warning popping up and have to wait for things like rubber banding when blinking or dashing, hit detection delays, if it even triggers damage after the hit fx.
Between the old forums and the new, I’ve counted thousands of of these reports all without a decent resolution. Not trying very hard are they?