Ping to Blizzard servers has doubled

[clockwise]

Thanks for the update mjducharme‌! Those are great results!

[machnee]

I'm now getting a respectable min 25ms, avg 46ms. 

Host	Best	Avg	Worst
50.72.96.1	7	25	224
rc3sc-be105-1.wp.shawcable.net	9	25	218
rc4ec-be25-1.il.shawcable.net	25	42	250
eqix-ix-ch1.blizzard.com	25	44	240
ae1-br02-eqch2.as57976.net	25	48	253
be2-pe02-eqch2.as57976.net	26	45	244
chi-eqch2-ia-bons-04.as57976.net	26	47	248
24.105.62.129	25	46	238

[mjducharme]

Your "worst" numbers look universally high - are you connected via wireless? There may be interference causing latency on your wireless.

[sesopenko]

I'm in Calgary and for about a year I've been getting 70ms to blizzard when playing Overwatch.  I've tried with & without the router and different computers (desktop & gaming laptop) and I'm getting similar results.  Here's my traceroute to the active game server.  It looks like Shaw's taking 50ms to communicate with the first server from blizzard (66.163.68.66 to 137.221.73.33) which is pretty high.

tracert 24.105.10.66

Tracing route to 24.105.10.66 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router [192.168.10.1]
2 9 ms 9 ms 12 ms 70.77.96.1
3 13 ms 13 ms 17 ms rc3so-be117-1.cg.shawcable.net [64.59.134.169]
4 33 ms 34 ms 34 ms rc1wt-be82.wa.shawcable.net [66.163.76.9]
5 28 ms 29 ms 32 ms rc6wt-tge0-10-0-10.wa.shawcable.net [66.163.68.66]
6 76 ms 76 ms 77 ms ae1-br01-eqse2.as57976.net [137.221.73.33]
7 51 ms 51 ms 51 ms xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
8 87 ms 77 ms 100 ms xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.

A pathping shows that I'm also getting what looks like 1% packet loss within the shaw network (rc1wt-be82.wa.shawcable.net [66.163.76.9] 😞

Tracing route to 24.105.10.66 over a maximum of 30 hops

0 DESKTOP-15C5197 [192.168.10.109]
1 router [192.168.10.1]
2 70.77.96.1
3 rc3so-be117-1.cg.shawcable.net [64.59.134.169]
4 rc1wt-be82.wa.shawcable.net [66.163.76.9]
5 rc6wt-tge0-10-0-10.wa.shawcable.net [66.163.68.66]
6 ae1-br01-eqse2.as57976.net [137.221.73.33]
7 xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
8 xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-15C5197 [192.168.10.109]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% router [192.168.10.1]
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 70.77.96.1
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% rc3so-be117-1.cg.shawcable.net [64.59.134.169]
0/ 100 = 0% |
4 32ms 1/ 100 = 1% 1/ 100 = 1% rc1wt-be82.wa.shawcable.net [66.163.76.9]
0/ 100 = 0% |
5 33ms 1/ 100 = 1% 1/ 100 = 1% rc6wt-tge0-10-0-10.wa.shawcable.net [66.163.68.66]
0/ 100 = 0% |
6 29ms 1/ 100 = 1% 1/ 100 = 1% ae1-br01-eqse2.as57976.net [137.221.73.33]
0/ 100 = 0% |
7 51ms 1/ 100 = 1% 1/ 100 = 1% xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
0/ 100 = 0% |
8 83ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]

Trace complete.

[#5]

Numbers look good again on tracert as well as in game. Thanks for your help

[mjducharme]

The game server address you provided doesn’t respond to pings. Are you sure you got it correct?

The latency you saw from the first hop to the Seattle first hop wasn’t real bc it disappeared from the next hop, which would not be lower latency from the last.

The packet loss is also not a concern because it appears to be fake packet loss from ICMP rate limiting. 

I wonder if there may simply be a typo in the game server ip?  I would be surprised if their game server is set to block all pings and I cannot ping it at the ip you were trying and I see you can’t either. 

[#7]

Hello.

I am having the same issue.  I was wondering if you could fix my route?  I realize I am not directly a Shaw customer, but was hoping you would be able to help all the same.  The issues occur with or without router, and with a different modem.

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 7 ms 8 ms 7 ms 70.74.128.1
2 8 ms 8 ms 8 ms 198-48-128-129.cpe.pppoe.ca [198.48.128.129]
3 8 ms 8 ms 9 ms 66.163.70.130
4 14 ms 14 ms 14 ms xe-0-1-1-1832-bdr01-cgr.teksavvy.com [76.10.191.137]
5 13 ms 14 ms 13 ms ae6-152.cr0-sjc2.ip4.gtt.net [69.174.3.41]
6 32 ms 31 ms 32 ms xe-0-0-2.cr2-sea2.ip4.gtt.net [89.149.181.153]
7 33 ms 32 ms 31 ms ip4.gtt.net [69.174.5.10]
8 56 ms 56 ms 56 ms ae1-br01-eqse2.as57976.net [137.221.73.33]
9 57 ms 56 ms 56 ms xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
10 56 ms 56 ms 57 ms xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
11 56 ms 56 ms 56 ms be2-pe02-eqla1.as57976.net [137.221.68.73]
12 56 ms 58 ms 56 ms 24.105.30.129