hi, can someone help me. i installed Pingplotter and WinMTR but i dont know how to use them. i’ve started getting Lag spikes Aug 11th. it’s super annoying. i wanna play Ow without lag again. im Canadian if that matters, idk.
I’m also getting really random lag spikes since around early August, and it’s gotten worse with the new patch. This has never happened before.
5 Likes
Someone actually just walked me through this:
Download WinMTR and then login to OW
Start a match (not practice range, I recommend arcade so you don’t get a leaver penalty if something happens), and then press CTRL+Shift+N, and up towards the top left, look for an IP address.
Once you get the IP, open WinMTR, punch in the IP, and start running a test. Then just finish your match while the test runs in the background.
Then you can post the results here and will likely be pointed in the right direction. Just be sure to open your own thread as I’ve marked this one as solved.
server is ord 1 and then beside it has a bunch of letters and numbers, like i mean a bunch!
i typed it in and the program said it can’t do it.
Okay I know exactly what you’re talking about, that same thing actually happened to me the 2nd or 3rd time I tried to login and look at the IP.
Maybe someone from support will see this and can help you make the IP appear again?
You could also try just restarting your PC and then logging back into OW and checking again. I’m sorry as I really don’t know what makes it change from an IP to all those random letters and numbers. I think it might be something with the way windows OS converts IP’s to those random strings.
1 Like
If you’re using IPv6, it will be an IPv6 address, which WinMTR does not support. You would need to use PingPlotter.
1 Like
Is there a way to make it the easier one? The shorter one?
Typing all the letters and numbers, takes alot of time, i feel like id get kicked for inactivity xD
Take a screenshot of it and run pingplotter it after your match ends.
I typed the whole thing in pingplotter and it tells me, Invalid trace target.
-Couldnt resolve hostname
- socket error #11001 “hostNotFound”
-make sure you entered a vaild hostname or IP.
This is what i typed.
[Ord1] 3c42390a1f7d0002: 00d78294b1f110f9 - 88e305b85a5f8a6d254081317f1e22f6716d0f2221aa70a8af8dcabd7a2c3646
I typed this while in a Custom game.
1 Like
It looks like the IPs are no longer listed in the netgraph, but I’m not sure if it’s intentional or what the situation is. For the time being, I don’t believe the IPs are available for running external tests.
1 Like
same here, netgraph showing gibberish characters instead of IP. thought it was IPv6 at first but it’s too weird looking to be one
1 Like
Dang that’s annoying…
I managed to get ahold of my ISP and explained the issue and on which node it’s occuring. They said they’d open a ticket and would start investigating and would get back to me in 24hrs, but that was 4 days ago 
I mean I wouldn’t go so far as to say the game is unplayable for me at this point, but it is definitely a struggle and frustrating enough that it just makes me hop over to other shooters that I know aren’t lagging like this.
1 Like
Same. I started playing other FPS games cause of these ping spikes. I wanna play Overwatch again without walking off the map cause of lag.
Yep, been having this happen more and more commonly… Wanted to talk to my isp but it seems I cant check anymore. Im just tired of the slip and slide style gameplay again and again…
1 Like
i ping tested while playing Overwatch. i hope this helps.
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| homeportal - 0 | 1563  |
1563 | 0 | 0 | 2 | 1 |
| No response from host - 100 | 316 | 0 | 0 | 0 | 0 | 0 |
142.165.120.97 - 53  |
509 | 242 | 36 | 37 | 41 | 37 |
| 142.165.60.42 - 29 |
744 | 535 | 35 | 35 | 40 | 35 |
| eqix-ix-ch1.blizzard.com - 1 | 1560 | 1559 | 56 | 60 | 131 | 57 |
| ae2-br02-eqch2.as57976.net - 1 | 1488 | 1487 | 62 | 391 | 4280 | 368 |
| et-0-0-1-pe02-evch1.as57976.net - 1 | 1560 | 1559 | 56 | 57 | 93 | 58 |
| 137.221.67.65 - 1 | 1560 | 1559 | 57 | 58 | 61 | 59 |
| 24.105.62.129 - 1 | 1560 | 1559 | 57 | 58 | 65 | 58 |
I see this was run for 26mins. Usually it’s best to run for 5mins or until you experience the issue. If you don’t experience it in the 5 minutes, restart the test.
Three packets were lost in the ISP network. We can verify this information from the data because your computer sent 1563 packets out, but only 1560 made the trip to the first Equinix Blizzard peering node (eqix-ix-ch1.blizzard.com). The packets were lost somewhere on those first two IPs, which belong to your ISP. Unfortunately, the nodes are obscuring their response times, so we can’t tell which specific node is responsible.
So i should redo the test? I’ll do it tomorrow after work.
Also, what are nodes?
What should i do?
Show the data to your ISP. Tell them you’re having packet loss in their network.
Don’t need more tests.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.