Insanely high (200-600) ping all the time. Help with traceroute/pathping/WinMTR?

Technical Support
1

I’ve been having really high ping in Overwatch lately. Minimum 200, but it regularly spikes up to ~600 also. I’ve done the traceroute, pathping, and WinMTR tests already but not really sure how to interpret the results. I think it’s clear that there’s something wrong though. Can anyone help me out? Any info would be much appreciated. Results are below.

I’m from the Philippines and my ISP is PLDT btw.

TRACERT

Tracing route to ec2-3-0-146-4.ap-southeast-1.compute.amazonaws. com [3.0.146.4]
over a maximum of 30 hops:

1 3 ms 2 ms 1 ms Linksys18129 [192.168.1.1]
2 11 ms 3 ms 3 ms 112.211.32.1.pldt. net [112.211.32.1]
3 3 ms 2 ms 2 ms 122.2.203.2.static.pldt. net [122.2.203.2]
4 43 ms 4 ms 4 ms 210.213.130.1.static.pldt. net [210.213.130.1]
5 47 ms 47 ms 47 ms 210.213.130.37.static.pldt. net [210.213.130.37]
6 53 ms 48 ms 50 ms 16509.sgw.equinix. com [27.111.228.87]
7 * * * Request timed out.
8 * * * Request timed out.
9 49 ms 49 ms 49 ms 52.93.10.33
10 48 ms 48 ms 48 ms 52.93.11.63
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

PATHPING

Tracing route to ec2-3-0-146-4.ap-southeast-1.compute.amazonaws. com [3.0.146.4]
over a maximum of 30 hops:
0 Mig-PC [192.168.1.138]
1 Linksys18129 [192.168.1.1]
2 112.211.32.1.pldt. net [112.211.32.1]
3 122.2.203.2.static.pldt. net [122.2.203.2]
4 210.213.130.1.static.pldt. net [210.213.130.1]
5 210.213.130.37.static.pldt. net [210.213.130.37]
6 16509.sgw.equinix. com [27.111.228.87]
7 * * *
Computing statistics for 150 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mig-PC [192.168.1.138]
0/ 100 = 0% |
1 32ms 1/ 100 = 1% 1/ 100 = 1% Linksys18129 [192.168.1.1]
0/ 100 = 0% |
2 43ms 0/ 100 = 0% 0/ 100 = 0% 112.211.32.1.pldt. net [112.211.32.1]
0/ 100 = 0% |
3 50ms 0/ 100 = 0% 0/ 100 = 0% 122.2.203.2.static.pldt. net [122.2.203.2]
0/ 100 = 0% |
4 37ms 0/ 100 = 0% 0/ 100 = 0% 210.213.130.1.static.pldt. net [210.213.130.1]
0/ 100 = 0% |
5 80ms 0/ 100 = 0% 0/ 100 = 0% 210.213.130.37.static.pldt. net [210.213.130.37]
0/ 100 = 0% |
6 90ms 0/ 100 = 0% 0/ 100 = 0% 16509.sgw.equinix. com [27.111.228.87]

Trace complete.

WINMTR

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| Linksys18129 - 1 | 501 | 500 | 1 | 29 | 1666 | 1 |

| 112.211.32.1.pldt. net - 1 | 501 | 500 | 2 | 32 | 1666 | 3 |

| 122.2.203.6.static.pldt. net - 0 | 498 | 498 | 2 | 57 | 2729 | 122 |

| 210.213.130.13.static.pldt. net - 0 | 499 | 499 | 2 | 54 | 2729 | 104 |

| 210.213.130.37.static.pldt. net - 1 | 487 | 483 | 47 | 74 | 2829 | 47 |

| 16509.sgw.equinix. com - 1 | 496 | 495 | 47 | 90 | 2842 | 129 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| 52.93.10.3 - 1 | 492 | 490 | 48 | 92 | 2745 | 133 |

| 52.93.11.19 - 1 | 487 | 483 | 47 | 76 | 2828 | 51 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| 203.83.223.190 - 1 | 496 | 495 | 184 | 223 | 2388 | 185 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |

|____________|||||||

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

2

Hey msv,

It looks like the WinMTR test recorded a 1666ms latency spike to your router as well as 1% packet loss. Are you using a wifi connection to the router? If so you might want to try switching to wired if that’s possible.

Which server does it show you connecting to when you’re in a match seeing the high latency? If you press Ctrl+Shift+N to bring up the network graph you’ll see the server name in brackets and the IP address.

4

I cant have a wired cable at the moment so wireless is all I can use but the thing is that I was playing a comp game and I had just loaded into the game and it said “failed to join server” as a result I could not join and I lost sr without even getting to enter the game so I am mad that this happened. I will fix the wifi eventually but I was wondering if it were to be possible to go back to the Sr I had before the game. If it is not possible that is fine I was just curios

5

Yes to WiFi but unfortunately a wired connection isn’t possible. My PC is just too far to run a wired connection. I’m usually in PSE1 but I’ve also had a few LAX1 games.

Based on the results, does it look like it’s mostly a router issue?

6

msv,

It looks like it could be a router issue. If wifi is your only option you might want to try switching between the 2.4ghz and 5ghz wifi bands to test both of them, one may work better than the other as far as stability while gaming.

Sword,

We don’t have the ability to restore SR I’m afraid. However the “failed to join server” can be the result of the connection being unstable as well. You may also want to try swapping to the other wifi band (if your router supports both 2.4ghz and 5ghz) to see if the issue goes away when switching.