Recent Discussions
overwatch latency traceroutes northwest arkansas
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.) 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 issue on my end. Blizzard provides a traceroute tool which can be found here. http://us-looking-glass.battle.net/ (select overwatch in the dropdown) The test generates a traceroute (and more tests) from two different blizzard servers. I'll post the lower pinging result. From 24.105.12.6 (Blizzard/Overwatch) to Me in Fayetteville, AR 1 24.105.12.6 (24.105.12.6) 0.769 ms 2.057 ms 2.068 ms 2 24.105.30.158 (24.105.30.158) 2.059 ms 2.064 ms 2.063 ms 3 37.244.0.100 (37.244.0.100) 3.680 ms 3.689 ms 3.697 ms 4 37.244.0.32 (37.244.0.32) 2.063 ms 2.064 ms 3.023 ms (BLIZZARD) 5 70.191.61.9 (70.191.61.9) 2.049 ms 2.050 ms 2.051 ms (COX?) 6 kscydsrj02-ae3.0.rd.ks.cox.net (68.1.1.197) 49.178 ms 49.316 ms 49.314 ms 7 kscydsrj02-ae0.rd.ks.cox.net (70.183.71.93) 60.260 ms 59.898 ms 59.897 ms 8 wsip-70-182-122-51.ks.ks.cox.net (70.182.122.51)61.465 ms 61.530 ms 61.574 ms 9 70.183.68.95 (70.183.68.95) 60.780 ms 60.791 ms 60.791 ms 10 ip68-111-117-XX.fv.ks.cox.net (68.111.117.XX) 68.483 ms 71.767 ms 71.749 ms (ME, I turned on ping requests) From 68.111.117.XX (Me/Fayetteville,AR) to 24.105.12.6 (Blizzard/Overwatch) 1 <1 ms <1 ms <1 ms router.dlink.com [192.168.0.1] 2 7 ms 6 ms 8 ms 70.183.68.94 3 9 ms 9 ms 10 ms wsip-70-182-122-50.ks.ks.cox.net [70.182.122.50] 4 19 ms 19 ms 20 ms 70.183.71.92 5 66 ms 67 ms 66 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13] 6 71 ms 68 ms 68 ms 70.191.61.10 (COX) 7 68 ms 68 ms 69 ms 37.244.0.50 (BLIZZARD) 8 70 ms 69 ms 69 ms 37.244.0.101 9 67 ms 69 ms 68 ms 24.105.30.151 10 69 ms 69 ms 68 ms 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. 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.
