overwatch latency traceroutes northwest arkansas

Question

I'd like to point out the latency issue in hopes that it can be improved. Currently experiencing a "high" 70ms ping while playing Overwatch (newest blizzard game.)&nbsp; This is the "normal" ping as long as the game has been out. I do not have packet loss, and the ping is very stable. I do not have a throughput concern. I'm not trying to solve an&nbsp; issue on my end.
Blizzard provides a traceroute tool which can be found here. http://us-looking-glass.battle.net/&nbsp;&nbsp; (select overwatch in the dropdown)
The test generates a traceroute (and more tests) from two different blizzard servers.&nbsp; I'll post the lower pinging result.
From 24.105.12.6 (Blizzard/Overwatch) to Me in Fayetteville, AR
&nbsp;1&nbsp; 24.105.12.6 (24.105.12.6) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.769 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.057 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.068 ms &nbsp;2&nbsp; 24.105.30.158 (24.105.30.158) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.059 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.064 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.063 ms &nbsp;3&nbsp; 37.244.0.100 (37.244.0.100) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.680 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.689 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.697 ms &nbsp;4&nbsp; 37.244.0.32 (37.244.0.32) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.063 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.064 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.023 ms&nbsp; (BLIZZARD) &nbsp;5&nbsp; 70.191.61.9 (70.191.61.9)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.049 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.050 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.051 ms&nbsp;&nbsp; (COX?) &nbsp;6&nbsp; kscydsrj02-ae3.0.rd.ks.cox.net (68.1.1.197)&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 49.178 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 49.316 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 49.314 ms &nbsp;7&nbsp; kscydsrj02-ae0.rd.ks.cox.net (70.183.71.93)&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 60.260 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 59.898 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 59.897 ms &nbsp;8&nbsp; wsip-70-182-122-51.ks.ks.cox.net (70.182.122.51)&nbsp;61.465 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 61.530 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 61.574 ms &nbsp;9&nbsp; 70.183.68.95 (70.183.68.95)&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 60.780 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 60.791 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 60.791 ms 10&nbsp; ip68-111-117-XX.fv.ks.cox.net (68.111.117.XX)&nbsp; &nbsp; 68.483 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 71.767 ms&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 71.749 ms&nbsp; (ME, I turned on ping requests)
From 68.111.117.XX (Me/Fayetteville,AR) to 24.105.12.6 (Blizzard/Overwatch) 1&nbsp;&nbsp;&nbsp; &lt;1 ms&nbsp;&nbsp;&nbsp; &lt;1 ms&nbsp;&nbsp;&nbsp; &lt;1 ms&nbsp; router.dlink.com [192.168.0.1] 2&nbsp;&nbsp;&nbsp;&nbsp; 7 ms&nbsp;&nbsp;&nbsp;&nbsp; 6 ms&nbsp;&nbsp;&nbsp;&nbsp; 8 ms&nbsp; 70.183.68.94 3&nbsp;&nbsp;&nbsp;&nbsp; 9 ms&nbsp;&nbsp;&nbsp;&nbsp; 9 ms&nbsp;&nbsp;&nbsp; 10 ms&nbsp; wsip-70-182-122-50.ks.ks.cox.net [70.182.122.50] 4&nbsp;&nbsp;&nbsp; 19 ms&nbsp;&nbsp;&nbsp; 19 ms&nbsp;&nbsp;&nbsp; 20 ms&nbsp; 70.183.71.92 5&nbsp;&nbsp;&nbsp; 66 ms&nbsp;&nbsp;&nbsp; 67 ms&nbsp;&nbsp;&nbsp; 66 ms&nbsp; langbprj01-ae1.rd.la.cox.net [68.1.1.13] 6&nbsp;&nbsp;&nbsp; 71 ms&nbsp;&nbsp;&nbsp; 68 ms&nbsp;&nbsp;&nbsp; 68 ms&nbsp; 70.191.61.10 (COX) 7&nbsp;&nbsp;&nbsp; 68 ms&nbsp;&nbsp;&nbsp; 68 ms&nbsp;&nbsp;&nbsp; 69 ms&nbsp; 37.244.0.50&nbsp; (BLIZZARD) 8&nbsp;&nbsp;&nbsp; 70 ms&nbsp;&nbsp;&nbsp; 69 ms&nbsp;&nbsp;&nbsp; 69 ms&nbsp; 37.244.0.101 9&nbsp;&nbsp;&nbsp; 67 ms&nbsp;&nbsp;&nbsp; 69 ms&nbsp;&nbsp;&nbsp; 68 ms&nbsp; 24.105.30.151 10&nbsp; 69 ms&nbsp;&nbsp;&nbsp; 69 ms&nbsp;&nbsp;&nbsp; 68 ms&nbsp; 24.105.12.6
Obviously, first, these two routes do not match, but I do know that does not automatically mean there is an issue. I want to point at hops 4,5,6 in the top route and 5,6,7 in the bottom route. The server 70.191.61.9 belongs to Cox (I assume.) The connection between that server and a blizzard server (37.244.0.32) is very good.&nbsp; The connection between 70.191.61.9 (Cox?) and kscydsrj02-ae3.0.rd.ks.cox.net (68.1.1.197) shows where the latency starts.
Similarly, in the bottom traceroute, the apparent latency increase does not occur between the Cox Server (70.191.61.9) and the Blizzard server (37.244.0.50) but between the two cox servers.
Is there something obviously wrong? Is there anything that Cox and/or Blizzard can do to improve this path? Thank you.

tecknowhelp · Answer

This is the 3rd issue I have heard about Blizzards games in ARK on Cox. This is the best data I have seen showing the problem. I would suggest mirroring this thread over on DSLReports and see if you can get a engineer's attention. I would be curious what "&nbsp;langbprj01-ae1" is. I have seen it in other threads causing a problem. Could just be a common name in Cox's naming structure, but might be a hint.&nbsp;
PS. If the problem is outside control, you can try to work around it with a VPN. &nbsp;Some manufactures like Asus offer "WTFast" which is VPN client/server that not only allows you a possible better route, but lets you be a possible better route for someone else.&nbsp;

Forum Discussion

overwatch latency traceroutes northwest arkansas

1 Reply

Related Content

Gigablast/Fiber/Traceroute

Trouble in Northwest Arkansas? Very slow downstream, upstream is normal. Multiple friends having same issue

Overwatch pathping issue

Sending Traceroute

Outage in Northwest Arkansas

Recent Discussions

Welcome to the Archives

Gigablast

Beeping Noise

mic/status led on contour 2 remote

Internet connectivity frustrations