Hello, I’m experiencing horrible latency in overwatch lately and I’m not sure why. I use a ethernet cable plugged directly into pc, I have a good isp provider (or I think) Sepctrum The 100 Mgb plan, I changed my dns server, I tweaked settings by forwarding my ports TCP and UDP, and I’ve tried almost every guide in existence. I usually have 60ms which is alright, but lately I’ve been getting 250ms+. I have absolutely no idea what to do at this point. If anyone has any idea what I can do to try to fix this problem, I would greatly appreciate it. Thanks everyone and have a great day.
Hey there,
If you’re getting a stable 250ms (and it’s not spiking or going lower than that) you may be getting placed on a server outside of your normal regional area. The best thing to do here would be to open the Network Graph by hitting Shift+Ctrt+N while in a match, then look for the server name in [ ] brackets followed by the IP address.
Running a WinMTR can help identify if there’s an issue along the route that would be causing higher latency. Let us know what server name you’re seeing as well.
- Download WinMTR
- Right-click on the downloaded .zip folder and select “Extract All”, to extract the files to a new folder.
- Open the new folder that was created, then open the WinMTR_x64 folder.
- Right-click on the WinMTR application and select “Run as administrator”.
- Launch Overwatch and join a match. Once you’re in the match, press Ctrl+Shift+N to open the Network Graph.
- Look for the server name displayed in brackets and the IP address at the top. Note you will need to remove the colon and port number after the IP address before running the test. (12.345.67.89:PORT)
- Alt+Tab back to WinMTR, then type the server IP address in the “Host” field.
- Click on “Start” and Alt+Tab back into the game. Allow the test to run for at least 10 minutes or the duration of a match. Click on “Stop” when you’re done playing after you have experienced the latency or connection issue.
- Click on “Copy Text to Clipboard”, paste the results here, then highlight everything and hit the </> button in the posting section so it will allow links.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| SAGEMCOM - 0 | 923 | 923 | 0 | 0 | 15 | 0 |
| 142.254.145.81 - 0 | 923 | 923 | 10 | 23 | 241 | 23 |
| 24.164.118.141 - 0 | 923 | 923 | 11 | 27 | 246 | 16 |
| 24.164.236.2 - 0 | 923 | 923 | 10 | 25 | 241 | 15 |
| be14.clevohek02r.midwest.rr.com - 0 | 923 | 923 | 11 | 29 | 244 | 12 |
| be25.clevohek01r.midwest.rr.com - 0 | 923 | 923 | 11 | 28 | 247 | 23 |
| so-7-1-0.ar0.dca10.tbone.rr.com - 0 | 923 | 923 | 19 | 36 | 247 | 28 |
|bu-ether11.asbnva1611w-bcr00.tbone.rr.com - 0 | 923 | 923 | 20 | 37 | 247 | 28 |
| 72.14.208.14 - 0 | 923 | 923 | 19 | 33 | 246 | 24 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| 142.250.232.78 - 0 | 923 | 923 | 19 | 33 | 247 | 25 |
| 108.170.246.3 - 0 | 923 | 923 | 19 | 33 | 247 | 20 |
| 209.85.244.167 - 0 | 923 | 923 | 19 | 34 | 247 | 26 |
| 142.250.209.77 - 0 | 923 | 923 | 20 | 35 | 247 | 25 |
| 142.250.215.205 - 0 | 923 | 923 | 125 | 142 | 337 | 245 |
| 172.253.79.160 - 7 | 736 | 687 | 132 | 148 | 307 | 142 |
| 142.250.228.15 - 0 | 923 | 923 | 132 | 151 | 343 | 246 |
| 142.250.38.33 - 0 | 923 | 923 | 132 | 149 | 341 | 178 |
| 216.239.59.80 - 0 | 923 | 923 | 132 | 149 | 347 | 247 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 187 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderThe most noticeable factor is when there is a major leap from 15th hub to the 16th hub. In your report, the average latency jumps from 35 milliseconds all the way to 142.
Considering this and the fact your connection route is having to travel through quite a few hubs, I suspect the connection route to your geographically closest game server is blocked and you are being rerouted to a far more distant server. When you ran the WinMTR test there should be a three letter + one number code next to the IP address when looking at the In-Game Netgraph. If this connection problem is remaining persistent, can you please report what that location code is and where you live specifically (your city, state/providence, country will suffice).
In addition to what WyomingMyst mentioned, I did what to call out this:
The worst latency recorded on the 2nd “hop” which would be right within your internet provider’s network, was 241ms. While the average latency looks fine, at 23ms, those spikes in latency could be causing the match making to accept putting you on a server outside of your closest region.
Posting the server name displayed in brackets would be helpful.
The WinMTR was definitely run to a Google server, but I can’t tell which one from the test alone.
If you can run another WinMTR and use the IP address for the Central US server, we can compare the tests. Central US would be: 24.105.62.129
Hey, I’m experiencing this problems again and they’re on and off and really inconvenient especially since I spend most of my time playing ranked. My code is ORD1 and I live in Cleveland. I really hope this information helps.
If you’re connecting to ORD1, then you can use the info the staff provided on your test. There is intermittent high ping early in the ISP route near your home.