Use to get 30ping and now whenever I start my game i get 130+ ping. I got lower ping playing on EU servers. I play on NA servers and i’d have to restart my games a few time to get 30 ping but now i can’t get 30 ping at all. Firewall has private and public for all my overwatch tabs.
Here’s my Looking Glass below. just remove the space between .com
imgur.c om/a/7AfsX8l
imgur.c om/a/7FS4I2I
Hey McCrêê,
Thank you for the looking glass tests! It helps confirm the issue we have been seeing. We are aware of an increase latency for some players. It is being investigated at the moment.
Currently, there are no workarounds or ETA on the issue that we have found. However, I’ll try and update this thread on any further news or updates on the issue 
I live in ohio, I connect to ORD1 which is Chicago IL, literally 4 hours driving distance. I use to have bad startups where i would get this 130 ping but i’d restart once or twice and get my usual 30 ping.
But now I always get 130 ping after leaving the game for 2 months because it made me think about someone I use to/and still do care about everytime I played it. It’s seriously not helping me knowing that I get less ping on EU.
I’ve uninstalled reinstalled, scanned files repaired, got new IP address, flushed DNS, restarted computer, tried logging into every other server, deleted blizzard entertainment cache and emptied recycled bin.
That’s mostly everything else I can tell you about it.
Please let me know if there’s any person I can talk to or just keep me up to date.
I’ll be checking almost every hour.
The same has been happening to me. Averaged 60-70ms, sometimes up to 80ms before. Now I get at least 150-200ms in the training range, which steadily increases to 1000ms+, sometimes up to 2000ms+.
TRACEROUTE:
traceroute to 71.62.102.150 (71.62.102.150), 15 hops max, 60 byte packets
1 10.56.100.81 (10.56.100.81) 0.801 ms 0.772 ms 0.768 ms
2 37.244.22.131 (37.244.22.131) 2.183 ms 2.193 ms 2.194 ms
3 24.105.30.158 (24.105.30.158) 2.184 ms 2.186 ms 2.186 ms
4 137.221.66.4 (137.221.66.4) 2.195 ms 2.204 ms 2.420 ms
5 137.221.68.72 (137.221.68.72) 2.179 ms 2.179 ms 2.178 ms
6 137.221.68.34 (137.221.68.34) 2.168 ms 2.904 ms 2.892 ms
7 te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcast.net (23.30.206.153) 2.869 ms 2.052 ms 2.032 ms
8 be-11545-cr02.losangeles.ca.ibone.comcast.net (68.86.84.233) 3.687 ms 3.690 ms 2.867 ms
9 be-11524-cr02.dallas.tx.ibone.comcast.net (68.86.87.174) 41.433 ms 41.451 ms 41.461 ms
10 be-11424-cr02.56marietta.ga.ibone.comcast.net (68.86.85.21) 64.270 ms 64.284 ms 65.504 ms
11 ae-4-ar02.staplesmllrd.va.richmond.comcast.net (68.86.94.30) 76.633 ms 76.593 ms 76.584 ms
12 te-1-2-ur01.mechanicsvll.va.richmond.comcast.net (68.86.125.14) 68.711 ms 68.550 ms 68.536 ms
13 te-7-1-acr01.leesburg.va.richmond.comcast.net (96.108.130.206) 68.701 ms 68.569 ms 68.593 ms
14 c-71-62-102-150.hsd1.va.comcast.net (71.62.102.150) 79.291 ms 77.223 ms 82.035 ms
TRACEROUTE:
traceroute to 71.62.102.150 (71.62.102.150), 15 hops max, 60 byte packets
1 10.57.100.13 (10.57.100.13) 0.441 ms 0.428 ms 0.426 ms
2 37.244.23.130 (37.244.23.130) 0.491 ms 0.496 ms 0.624 ms
3 24.105.62.146 (24.105.62.146) 1.304 ms 1.312 ms 1.374 ms
4 137.221.66.8 (137.221.66.8) 2.042 ms 2.090 ms 2.146 ms
5 137.221.69.70 (137.221.69.70) 1.973 ms 1.986 ms 1.986 ms
6 137.221.69.34 (137.221.69.34) 1.305 ms 1.260 ms 1.247 ms
7 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 1.729 ms 1.791 ms 1.782 ms
8 be-10563-cr02.350ecermak.il.ibone.comcast.net (68.86.82.157) 2.761 ms 2.211 ms 2.190 ms
9 be-10506-cr01.chicago.il.ibone.comcast.net (68.86.86.230) 3.533 ms 3.542 ms 3.541 ms
10 be-10614-cr02.56marietta.ga.ibone.comcast.net (68.86.84.142) 27.869 ms 27.894 ms 29.361 ms
11 ae-4-ar02.staplesmllrd.va.richmond.comcast.net (68.86.94.30) 39.789 ms 39.758 ms 39.736 ms
12 te-1-2-ur01.mechanicsvll.va.richmond.comcast.net (68.86.125.14) 31.666 ms 31.667 ms 31.652 ms
13 te-7-1-acr01.leesburg.va.richmond.comcast.net (96.108.130.206) 31.219 ms 31.213 ms 31.248 ms
14 c-71-62-102-150.hsd1.va.comcast.net (71.62.102.150) 43.523 ms 42.416 ms 42.395 ms
PING:
PING 71.62.102.150 (71.62.102.150) 56(84) bytes of data.
64 bytes from 71.62.102.150: icmp_seq=1 ttl=50 time=79.0 ms
64 bytes from 71.62.102.150: icmp_seq=2 ttl=50 time=77.9 ms
64 bytes from 71.62.102.150: icmp_seq=3 ttl=50 time=77.9 ms
64 bytes from 71.62.102.150: icmp_seq=4 ttl=50 time=77.7 ms
— 71.62.102.150 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 77.728/78.152/79.050/0.625 ms
PING:
PING 71.62.102.150 (71.62.102.150) 56(84) bytes of data.
64 bytes from 71.62.102.150: icmp_seq=2 ttl=52 time=42.6 ms
— 71.62.102.150 ping statistics —
4 packets transmitted, 1 received, 75% packet loss, time 3001ms
rtt min/avg/max/mdev = 42.676/42.676/42.676/0.000 ms
MTR:
Start: Wed May 23 23:54:37 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.56.100.81 0.0% 10 0.4 0.4 0.2 1.2 0.0
2.|-- 37.244.22.131 0.0% 10 0.4 0.6 0.4 1.1 0.0
3.|-- 24.105.30.158 0.0% 10 1.0 1.1 0.8 2.7 0.3
4.|-- 137.221.66.4 0.0% 10 1.8 1.6 1.4 2.2 0.0
5.|-- 137.221.68.72 0.0% 10 12.1 2.4 1.3 12.1 3.4
6.|-- 137.221.68.34 0.0% 10 1.4 1.3 1.1 2.0 0.0
7.|-- te-0-10-0-1-4-pe01.600wseventh.ca.ibone.comcast.net 0.0% 10 5.3 1.8 1.1 5.3 1.2
8.|-- be-11545-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 2.3 2.9 1.8 3.8 0.5
9.|-- be-11524-cr02.dallas.tx.ibone.comcast.net 0.0% 10 34.5 34.0 33.1 35.0 0.3
10.|-- be-11424-cr02.56marietta.ga.ibone.comcast.net 0.0% 10 63.3 64.3 63.3 65.5 0.3
11.|-- ae-4-ar02.staplesmllrd.va.richmond.comcast.net 0.0% 10 76.5 82.1 76.3 129.3 16.6
12.|-- te-1-2-ur01.mechanicsvll.va.richmond.comcast.net 0.0% 10 68.6 68.5 68.4 68.7 0.0
13.|-- te-7-1-acr01.leesburg.va.richmond.comcast.net 0.0% 10 68.6 68.6 68.4 69.1 0.0
14.|-- c-71-62-102-150.hsd1.va.comcast.net 0.0% 10 78.6 77.5 76.9 78.6 0.3
MTR:
Start: Wed May 23 23:54:37 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.57.100.13 0.0% 10 0.3 0.3 0.3 0.7 0.0
2.|-- 37.244.23.130 0.0% 10 0.5 0.6 0.5 0.8 0.0
3.|-- 24.105.62.146 0.0% 10 1.3 1.5 1.2 2.2 0.0
4.|-- 137.221.66.8 0.0% 10 2.0 2.2 1.9 2.8 0.0
5.|-- 137.221.69.70 0.0% 10 2.2 3.3 1.8 15.0 4.0
6.|-- 137.221.69.34 0.0% 10 1.6 1.4 1.1 1.9 0.0
7.|-- te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.8 1.9 1.6 2.4 0.0
8.|-- be-10563-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 3.7 3.4 2.5 4.2 0.0
9.|-- be-10506-cr01.chicago.il.ibone.comcast.net 0.0% 10 3.7 3.2 2.4 3.8 0.0
10.|-- be-10614-cr02.56marietta.ga.ibone.comcast.net 0.0% 10 28.4 28.1 27.4 29.2 0.0
11.|-- ae-4-ar02.staplesmllrd.va.richmond.comcast.net 0.0% 10 39.8 39.8 39.6 40.7 0.0
12.|-- te-1-2-ur01.mechanicsvll.va.richmond.comcast.net 0.0% 10 32.1 31.9 31.7 32.6 0.0
13.|-- te-7-1-acr01.leesburg.va.richmond.comcast.net 0.0% 10 31.5 31.5 31.2 32.2 0.0
14.|-- c-71-62-102-150.hsd1.va.comcast.net 0.0% 10 40.4 41.1 40.4 41.9 0.3
Hey there, just stopping by. There hasn’t been any further updates so far, but I’ll continue to keep an eye on this thread.
@Skrimiche, the looking glass tests were normal and seem to respond to the 60-70ms. This is a different issue from OP’s. Likely a local network or connection route/packet loss is causing the high ms, with it increasing to the thousands, it does sound like it may be the local network.
Please start a new thread or reach out to our Technical Support by opening a case. - Including a WinMTR test, Network Graph (CTRL+SHIFT+N in-game) screenshot, and a MSINFO will help diagnose the issue 