Please take a look at ping in Florida!

Everyday at any time ,i have 80-90 ping. 80 ping cannot support me to play overwatch.It’s realy bad that I’m playing against people who pretty much all get to enjoy latency near single digits,Hope you can fix it!

TRACEROUTE:
traceroute to 96.75.88.242 (96.75.88.242), 15 hops max, 60 byte packets
1 10.57.68.13 (10.57.68.13) 0.292 ms 0.271 ms 0.267 ms
2 37.244.23.2 (37.244.23.2) 0.611 ms 0.642 ms 0.744 ms
3 24.105.62.150 (24.105.62.150) 1.082 ms 1.099 ms 2.394 ms
4 137.221.66.10 (137.221.66.10) 2.586 ms 2.611 ms 2.682 ms
5 137.221.69.66 (137.221.69.66) 2.568 ms 2.572 ms 2.573 ms
6 137.221.69.32 (137.221.69.32) 2.380 ms 2.437 ms 2.372 ms
7 te-0-11-0-0-3-pe01.350ecermak.il.ibone.comcast.net (50.242.151.153) 2.346 ms 1.690 ms 1.676 ms
8 be-10563-cr02.350ecermak.il.ibone.comcast.net (68.86.82.157) 4.195 ms 3.445 ms 5.521 ms
9 be-10506-cr01.chicago.il.ibone.comcast.net (68.86.86.230) 4.923 ms 4.932 ms 4.916 ms
10 be-10614-cr02.56marietta.ga.ibone.comcast.net (68.86.84.142) 30.520 ms 29.383 ms 29.354 ms
11 be-7922-ar01.pompanobeach.fl.pompano.comcast.net (68.86.90.186) 45.424 ms 45.228 ms 45.210 ms
12 68.87.162.38 (68.87.162.38) 46.093 ms 46.421 ms 46.381 ms
13 68.85.219.210 (68.85.219.210) 47.262 ms 47.377 ms 47.354 ms
14 te-5-1-0-cbr02.verobeach.fl.pompano.comcast.net (68.86.160.34) 47.147 ms 47.136 ms 47.130 ms
15 * * *

30/03/2018 17:47:51 UTC

TRACEROUTE:
traceroute to 96.75.88.242 (96.75.88.242), 15 hops max, 60 byte packets
1 10.56.70.56 (10.56.70.56) 0.320 ms 0.298 ms 0.295 ms
2 37.244.22.3 (37.244.22.3) 0.981 ms 0.987 ms 0.985 ms
3 24.105.30.162 (24.105.30.162) 2.879 ms 2.881 ms 2.882 ms
4 137.221.66.6 (137.221.66.6) 2.858 ms 2.866 ms 2.867 ms
5 137.221.68.68 (137.221.68.68) 2.857 ms 2.857 ms 2.857 ms
6 137.221.68.32 (137.221.68.32) 2.838 ms 1.407 ms 1.373 ms
7 te-0-4-0-10-pe02.600wseventh.ca.ibone.comcast.net (50.242.151.165) 1.535 ms 1.476 ms 1.552 ms
8 be-11587-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17) 3.691 ms 3.732 ms 3.735 ms
9 be-11524-cr02.dallas.tx.ibone.comcast.net (68.86.87.174) 33.879 ms 33.887 ms 33.886 ms
10 be-11424-cr02.56marietta.ga.ibone.comcast.net (68.86.85.21) 65.790 ms 65.815 ms 65.296 ms
11 be-7922-ar01.pompanobeach.fl.pompano.comcast.net (68.86.90.186) 81.449 ms 81.589 ms 81.570 ms
12 68.87.162.38 (68.87.162.38) 82.264 ms 82.208 ms 82.177 ms
13 68.85.219.210 (68.85.219.210) 83.087 ms 83.117 ms 83.100 ms
14 GE-0-2-ubr02.davie.fl.pompano.comcast.net (68.86.160.34) 83.092 ms 83.128 ms 83.112 ms
15 * * *

30/03/2018 17:47:51 UTC

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

— 96.75.88.242 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

30/03/2018 17:47:51 UTC

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

— 96.75.88.242 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

30/03/2018 17:47:51 UTC

VERY IMPORTANT, please note that Overwatch no longer measure connection speed in ping rate, but in a combined Ping and RTT value now called Latency. So if you remember playing with 60-65 ping and you are now seeing 80 latency, then this is normal for you. Please see this post for details:

These troubleshooting steps may help with any problems that your equipment has, so be sure to check that first:

However, if you have gone through all basic and advanced troubleshooting steps and nothing is turning up helpful, you may need to investigate to see if there is a problem between you and the game server. I see that you posted what appears to be a Looking Glass test, however a connection test such as a WinMTR test can be more helpful to measure latency issues:

WinMTR instructions:

  1. Download WinMTR from http://winmtr.net/download-winmtr/ (Console players need a Windows Desktop Computer connected to the same network as their console to do this.)
  2. Unzip the WinMTR.zip file to the Desktop.
  3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
  4. Run the WinMTR.exe
  5. 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.
    Network Graph
    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
  6. Once you notice the connection issue while playing, play for about 6 more minutes, minimize the game and click on “Stop”.
  7. Click on “Copy text to clipboard”, then return to this forum thread.
  8. Type two sets of four squiggly lines and then paste the contents of the WinMTR test between: ~~~~ Paste WinMTR Test Results Here ~~~~

80 Ping is not bad. It’s still practically instant. I usually get around 60-90 Ping, and anything below 85 is practically instant and lower ping doesn’t really matter. 90+ Is when movement starts to become weird and gameplay is affected