How do you fix high ping?


#1

My ping has been really high lately usually between 200 - 400 sometimes higher, normally it is between 50 - 80. I did everything websites recommended except re-download Overwatch. I was about to do that but decided I’d post my data from the Battle net Looking Glass to see if anybody knew any other fix.

TRACEROUTE:
traceroute to 142.183.242.35 (142.183.242.35), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.366 ms 0.389 ms 0.400 ms
2 24.105.18.131 (24.105.18.131) 0.714 ms 0.861 ms 0.885 ms
3 137.221.105.12 (137.221.105.12) 0.694 ms 0.843 ms 0.993 ms
4 137.221.66.16 (137.221.66.16) 1.090 ms 1.117 ms 1.115 ms
5 137.221.83.66 (137.221.83.66) 30.367 ms 30.387 ms 30.402 ms
6 137.221.65.68 (137.221.65.68) 183.102 ms 181.545 ms 181.530 ms
7 137.221.65.1 (137.221.65.1) 30.160 ms 30.186 ms 30.031 ms
8 137.221.65.7 (137.221.65.7) 30.274 ms 30.292 ms 30.238 ms
9 137.221.65.116 (137.221.65.116) 30.079 ms 30.050 ms 30.051 ms
10 137.221.65.41 (137.221.65.41) 30.137 ms 30.328 ms 30.330 ms
11 137.221.73.32 (137.221.73.32) 30.474 ms 30.113 ms 30.114 ms
12 bx4-seattle_ae9.net.bell.ca (184.150.180.232) 29.639 ms 29.777 ms 29.776 ms
13 * * *
14 * * *
15 * * *

17/07/2019 00:26:06 UTC

TRACEROUTE:
traceroute to 142.183.242.35 (142.183.242.35), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.367 ms 0.365 ms 0.366 ms
2 24.105.18.131 (24.105.18.131) 1.108 ms 1.113 ms 1.114 ms
3 137.221.105.12 (137.221.105.12) 1.056 ms 1.072 ms 1.075 ms
4 137.221.66.16 (137.221.66.16) 37.185 ms 37.205 ms 37.207 ms
5 137.221.83.66 (137.221.83.66) 30.402 ms 30.419 ms 30.422 ms
6 137.221.65.68 (137.221.65.68) 138.771 ms 137.587 ms 137.563 ms
7 137.221.65.1 (137.221.65.1) 30.358 ms 30.383 ms 30.464 ms
8 137.221.65.7 (137.221.65.7) 30.166 ms 30.170 ms 30.154 ms
9 137.221.65.116 (137.221.65.116) 32.515 ms 39.418 ms 39.391 ms
10 137.221.65.41 (137.221.65.41) 30.026 ms 38.244 ms 38.116 ms
11 137.221.73.32 (137.221.73.32) 38.107 ms 38.033 ms 37.946 ms
12 bx4-seattle_ae9.net.bell.ca (184.150.180.232) 37.865 ms 35.102 ms 32.148 ms
13 * * *
14 * * *
15 * * *

17/07/2019 00:26:06 UTC

PING:
PING 142.183.242.35 (142.183.242.35) 56(84) bytes of data.

— 142.183.242.35 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

17/07/2019 00:26:06 UTC

PING:
PING 142.183.242.35 (142.183.242.35) 56(84) bytes of data.

— 142.183.242.35 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

17/07/2019 00:26:06 UTC

MTR:
Start: Wed Jul 17 00:26:06 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 1.5 0.3
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.5 1.0 0.0
3.|-- 137.221.105.12 0.0% 10 0.5 0.6 0.5 1.1 0.0
4.|-- 137.221.66.16 0.0% 10 1.2 8.7 0.9 76.7 23.9
5.|-- 137.221.83.66 0.0% 10 30.1 33.0 30.1 51.4 6.8
6.|-- 137.221.65.68 0.0% 10 236.4 110.6 30.1 236.4 84.4
7.|-- 137.221.65.1 0.0% 10 792.9 144.1 30.0 792.9 242.4
8.|-- 137.221.65.7 0.0% 10 30.2 30.1 30.1 30.3 0.0
9.|-- 137.221.65.116 0.0% 10 30.2 30.4 30.0 32.6 0.6
10.|-- 137.221.65.41 0.0% 10 30.1 30.1 30.0 30.3 0.0
11.|-- 137.221.73.32 0.0% 10 30.5 30.9 30.2 35.6 1.6
12.|-- bx4-seattle_ae9.net.bell.ca 0.0% 10 29.8 30.1 29.7 33.4 0.9
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17.|-- 204.101.5.158 0.0% 10 67.3 67.7 67.3 70.8 1.0
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

17/07/2019 00:26:06 UTC

MTR:
Start: Wed Jul 17 00:26:06 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 24.105.18.3 0.0% 10 1.5 0.7 0.5 1.5 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.6 0.5 0.7 0.0
4.|-- 137.221.66.16 0.0% 10 1.0 2.4 0.9 13.1 3.8
5.|-- 137.221.83.66 0.0% 10 30.3 31.1 30.1 35.2 1.5
6.|-- 137.221.65.68 0.0% 10 87.1 66.9 30.0 184.1 48.5
7.|-- 137.221.65.1 0.0% 10 332.5 89.2 30.1 332.5 100.0
8.|-- 137.221.65.7 0.0% 10 30.3 30.4 30.1 31.2 0.0
9.|-- 137.221.65.116 0.0% 10 30.3 30.4 30.1 31.1 0.0
10.|-- 137.221.65.41 0.0% 10 30.4 31.5 29.9 42.3 3.8
11.|-- 137.221.73.32 0.0% 10 47.2 35.2 30.5 59.2 9.9
12.|-- bx4-seattle_ae9.net.bell.ca 0.0% 10 29.8 30.1 29.7 32.7 0.7
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17.|-- 204.101.5.158 0.0% 10 67.5 67.5 67.3 67.6 0.0
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

17/07/2019 00:26:06 UTC


#2

Howdy!

Seems no results are showing from the ISP network. Can you run a WinMTR to the server you are connected too when you see high ping following the steps Here! Keep the test running for a total of 10 minutes. Post the results back here for review!


#3

I think I did this right…

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

| WinMTR statistics |

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

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

| 192.168.2.1 - 0 | 1217 | 1217 | 1 | 233 | 2469 | 2421 |

| 142.183.242.36 - 0 | 1217 | 1217 | 1 | 233 | 2471 | 2418 |

| 172.25.44.237 - 0 | 1217 | 1217 | 17 | 255 | 2480 | 2412 |

| 172.25.53.21 - 0 | 1217 | 1217 | 17 | 257 | 2490 | 2405 |

| 172.25.53.114 - 0 | 1217 | 1217 | 17 | 256 | 2487 | 2419 |

| 172.25.196.146 - 1 | 1206 | 1202 | 19 | 255 | 2492 | 2408 |

| 204.101.5.157 - 0 | 1217 | 1217 | 19 | 257 | 2492 | 2402 |

| tcore4-toronto12_2-8-0-2.net.bell.ca - 0 | 1217 | 1217 | 34 | 271 | 2526 | 2413 |

|tcore4-chicagocp_hundredgige0-4-0-0.net.bell.ca - 0 | 1217 | 1217 | 33 | 271 | 2513 | 2419 |

| bx6-chicagodt_0-7-0-0.net.bell.ca - 0 | 1217 | 1217 | 33 | 268 | 2507 | 2413 |

| blizzard_bx6-chicagodt.net.bell.ca - 0 | 1217 | 1217 | 34 | 272 | 2528 | 2408 |

| ae1-br02-eqch2.as57976. net - 0 | 1217 | 1217 | 36 | 274 | 2527 | 2441 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|________________________________________________|______|______|______|______|______|______|

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


#4

Hello,
I have the same issue and plays from Central America connected to America region. Please help us.


#5

It is advised to create your own thread and share a WinMTR test result. Latency issues happen all of the time but that doesn’t mean your latency issue is automatically the same. It even seems that with the OP the latency issues start with his router with his worst latency being almost 2.5 seconds.


#6

The thing about that is my bro can be playing at the same time in the same house and be getting the 50 ping so i think its my computer or maybe a bug in OW cause i have been playing it for a few years and it just started doing thia a few months ago


#7

Your connection to the router looks really unstable. Are you on wireless? If so, try a cable connection and see if it improves. Then you’ll know it’s the wireless adapter on your PC or the router (unless your brother uses wireless with no issue, then it’s just the PC).

If you’re already wired, try a new cable. And if that fails, try a different port on the router. Finally, if none of this helps, you may need to look at replacing the NIC in your PC.