jkr

High ping playing Heroes of the Storm (Shaw Routing Issue?)

Discussion created by jkr on Nov 11, 2016
Latest reply on Jan 5, 2017 by corbin

Over the past week I've experienced consistently high latency/ping when playing Heroes of the Storm. Previously my ping remained under 50ms. Now it sits consistently at ~150ms in game.

 

There appears to be a routing problem between my location (Vancouver, BC) and Blizzard's west coast servers. I ran a Traceroute, Pathping, and MTR analysis, and they all point to a possible routing problem. See reports below.

 

Since the recommended West coast test IP address supplied by Blizzard for verifying routing problems for a range of Blizzard's games all point to the same address (24.105.30.129), I'm assuming this may be affecting other Blizzard games as well, for many Shaw customers.

Blizzard Support - Pathping test IP Addresses

North America (Americas)24.105.30.129 (US West)
24.105.62.129 (US Central)
Australia (Americas)103.4.114.233
Singapore (Americas)202.9.67.59
Brazil (Americas)54.207.104.145
Europe185.60.112.157
185.60.112.158
Korea (Asia)182.162.116.1
Taiwan (Asia)203.69.111.4

Other Shaw users are also experiencing routing problems with Blizzard games. Example:

andersonmarcel - High ping playing overwatch 

 

TRACEROUTE (Blizzard West - 24.105.30.129):

tracert 24.105.30.129

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 7 ms 10.67.128.1
3 9 ms 9 ms 10 ms rc1st-tge0-9-0-18-1.vc.shawcable.net [64.59.147.149]
4 9 ms 8 ms 10 ms rc1bb-tge0-5-0-20.vc.shawcable.net [66.163.74.82]
5 15 ms 12 ms 14 ms rc1wt-be90.wa.shawcable.net [66.163.76.66]
6 38 ms 31 ms 32 ms rc3sj-be60.cl.shawcable.net [66.163.75.90]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * eqix-ix-sv1.blizzard.com [206.223.116.55] reports: Destination net unreachable.

Trace complete.

 

PATHPING (Blizzard West - 24.105.30.129)

pathping 24.105.30.129

Tracing route to 24.105.30.129 over a maximum of 30 hops

0 JER-PC [192.168.0.10]
1 192.168.0.1
2 10.67.128.1
3 rc1st-tge0-9-0-18-1.vc.shawcable.net [64.59.147.149]
4 rc1bb-tge0-5-0-20.vc.shawcable.net [66.163.74.82]
5 rc1wt-be90.wa.shawcable.net [66.163.76.66]
6 rc3sj-be60.cl.shawcable.net [66.163.75.90]
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JER-PC [192.168.0.10]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.67.128.1
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% rc1st-tge0-9-0-18-1.vc.shawcable.net [64.59.147.149]
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% rc1bb-tge0-5-0-20.vc.shawcable.net [66.163.74.82]
0/ 100 = 0% |
5 18ms 0/ 100 = 0% 0/ 100 = 0% rc1wt-be90.wa.shawcable.net [66.163.76.66]
0/ 100 = 0% |
6 41ms 0/ 100 = 0% 0/ 100 = 0% rc3sj-be60.cl.shawcable.net [66.163.75.90]

Trace complete.

 

MTR (Blizzard West - 24.105.30.129)

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 56 | 56 | 0 | 0 | 0 | 0 |
| 10.67.128.1 - 0 | 56 | 56 | 6 | 7 | 15 | 7 |
| rc1st-tge0-9-0-18-1.vc.shawcable.net - 0 | 56 | 56 | 7 | 9 | 32 | 8 |
| rc1bb-tge0-5-0-20.vc.shawcable.net - 0 | 56 | 56 | 7 | 9 | 33 | 10 |
| rc1wt-be90.wa.shawcable.net - 0 | 56 | 56 | 11 | 12 | 17 | 12 |
| rc3sj-be60.cl.shawcable.net - 0 | 56 | 56 | 30 | 34 | 40 | 38 |
| Destination network unreachable. - 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 11 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|

 

 

Please Note: The route does not make it to any of Blizzard's servers. Blizzard's servers have the following suffixes: attens.net, att.net, alter.net, telia.net. Routing tests to other Blizzard servers are successful. For example:

 

Blizzard Brazil (54.207.104.145) - Successfully routes to telia.net

tracert 54.207.104.145

Tracing route to ec2-54-207-104-145.sa-east-1.compute.amazonaws.com [54.207.104.145]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 8 ms 10.67.128.1
3 9 ms 9 ms 10 ms rc1bb-tge0-9-0-18-1.vc.shawcable.net [64.59.147.145]
4 11 ms 11 ms 11 ms rc1wt-be90.wa.shawcable.net [66.163.76.66]
5 11 ms 11 ms 11 ms sea-b1-link.telia.net [62.115.12.69]
6 55 ms 58 ms 55 ms chi-b21-link.telia.net [62.115.116.141]
7 116 ms 76 ms 77 ms nyk-bb1-link.telia.net [62.115.140.66]
8 78 ms 81 ms 77 ms nyk-b5-link.telia.net [213.155.130.247]
9 76 ms 76 ms 77 ms 80.239.132.214
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 220 ms 223 ms * 54.240.244.196
14 * * * Request timed out.
15 215 ms 217 ms 221 ms 54.240.244.224
16 * 215 ms 217 ms 54.240.244.233
17 190 ms 215 ms 189 ms 177.72.240.193
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.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

Blizzard Korea (182.162.116.1) - Successfully routes to telia.net

tracert 182.162.116.1

Tracing route to 182.162.116.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 8 ms 10.67.128.1
3 10 ms 10 ms 9 ms rc1st-tge0-9-0-18-1.vc.shawcable.net [64.59.147.149]
4 8 ms 9 ms 18 ms rc1bb-tge0-5-0-19.vc.shawcable.net [66.163.72.254]
5 14 ms 12 ms 24 ms rc1wt-be90.wa.shawcable.net [66.163.76.66]
6 13 ms 13 ms 16 ms sea-b1-link.telia.net [62.115.12.69]
7 13 ms 13 ms 14 ms tata-ic-150693-sea-b1.c.telia.net [213.248.73.94]
8 44 ms 42 ms 42 ms if-ae-14-2.tcore1.PDI-Palo-Alto.as6453.net [64.86.123.22]
9 47 ms 45 ms 49 ms if-ae-3-2.tcore1.LVW-Los-Angeles.as6453.net [66.198.127.26]
10 47 ms 45 ms 45 ms if-ae-2-2.tcore2.LVW-Los-Angeles.as6453.net [66.110.59.2]
11 46 ms 44 ms 43 ms if-ae-6-20.tcore1.EQL-Los-Angeles.as6453.net [64.86.252.66]
12 45 ms 45 ms 45 ms 206.82.129.194
13 43 ms 43 ms 44 ms 1.213.145.25
14 188 ms 204 ms 189 ms 61.42.201.105
15 187 ms 187 ms 187 ms 61.43.235.210
16 187 ms 187 ms 188 ms 1.213.105.245
17 211 ms 186 ms 187 ms 211.233.95.58
18 188 ms 188 ms 190 ms 211.172.248.70
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.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

Blizzard Europe #1 (185.60.112.157) - Successfully routes to telia.net

tracert 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 7 ms 10.67.128.1
3 10 ms 8 ms 11 ms rc1st-tge0-9-0-18-1.vc.shawcable.net [64.59.147.149]
4 8 ms 7 ms 9 ms rc1bb-tge0-5-0-20.vc.shawcable.net [66.163.74.82]
5 11 ms 11 ms 11 ms rc1wt-be90.wa.shawcable.net [66.163.76.66]
6 13 ms 11 ms 11 ms sea-b1-link.telia.net [62.115.9.81]
7 54 ms 56 ms 55 ms chi-b21-link.telia.net [62.115.117.49]
8 76 ms 77 ms 77 ms nyk-bb1-link.telia.net [62.115.116.32]
9 147 ms 148 ms 150 ms ldn-bb3-link.telia.net [213.248.65.89]
10 147 ms 147 ms 147 ms ldn-b3-link.telia.net [80.91.247.25]
11 * * * Request timed out.
12 * * * Request timed out.
13 blizzard-ic-316507-slou-b1.c.telia.net [62.115.145.217] reports: Destination net unreachable.

Trace complete.

 

Blizzard Europe #2 (185.60.112.158) - Successfully routes to telia.net

tracert 185.60.112.158

Tracing route to 185.60.112.158 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 8 ms 8 ms 10.67.128.1
3 9 ms 7 ms 8 ms rc1bb-tge0-9-0-18-1.vc.shawcable.net [64.59.147.145]
4 14 ms 12 ms 12 ms rc1wt-be90.wa.shawcable.net [66.163.76.66]
5 10 ms 12 ms 11 ms sea-b1-link.telia.net [62.115.9.85]
6 56 ms 58 ms 54 ms chi-b21-link.telia.net [62.115.117.49]
7 76 ms 78 ms 83 ms nyk-bb2-link.telia.net [62.115.137.58]
8 145 ms 164 ms 146 ms ldn-bb2-link.telia.net [62.115.135.107]
9 148 ms 146 ms 148 ms ldn-b3-link.telia.net [80.91.251.237]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * blizzard-ic-316507-slou-b1.c.telia.net [62.115.145.217] reports: Destination net unreachable.

Trace complete.

 

However, there appear to be routing issues to Blizzard's Central US server. We see no routing to telia.net or another blizzard server suffix:

tracert 24.105.62.129

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 8 ms 7 ms 10.67.128.1
3 9 ms 9 ms 8 ms rc1bb-tge0-9-0-18-1.vc.shawcable.net [64.59.147.145]
4 11 ms 13 ms 11 ms rc1wt-be90.wa.shawcable.net [66.163.76.66]
5 31 ms 31 ms 31 ms rc3sj-be60.cl.shawcable.net [66.163.75.90]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * eqix-ix-sv1.blizzard.com [206.223.116.55] reports: Destination net unreachable.

Trace complete.

 

 

 

Other routing samples for comparison:

Google

tracert www.google.com

Tracing route to www.google.com [24.244.19.180]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 10.67.128.1
3 9 ms 10 ms 9 ms rc1st-tge0-9-0-18-1.vc.shawcable.net [64.59.147.149]
4 8 ms 8 ms 8 ms 24.244.19.180

Trace complete.

 

Dota 2, Valve, West coast, Seattle, WA

tracert eat.valve.net

Tracing route to eat.valve.net [192.69.96.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 9 ms 6 ms 10.67.128.1
3 8 ms 7 ms 8 ms rc1bb-tge0-9-0-18-1.vc.shawcable.net [64.59.147.145]
4 8 ms 9 ms 8 ms rc1st-tge0-5-0-12.vc.shawcable.net [66.163.72.217]
5 14 ms 14 ms 15 ms rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
6 14 ms 16 ms 14 ms rx0wt-valve-corporation.wa.shawcable.net [66.163.68.74]
7 * * * Request timed out.
8 * * * Request timed out.
9 18 ms 19 ms 19 ms eat.valve.net [192.69.96.1]

Trace complete.

 

Star Wars: The Old Republic, West coast server test address

tracert 159.153.68.252

Tracing route to 159.153.68.252 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 7 ms 10.67.128.1
3 9 ms 8 ms 9 ms rc1bb-tge0-9-0-18-1.vc.shawcable.net [64.59.147.145]
4 12 ms 11 ms 11 ms rc1wt-be90.wa.shawcable.net [66.163.76.66]
5 35 ms 31 ms 31 ms rc3sj-be60.cl.shawcable.net [66.163.75.90]
6 31 ms 32 ms 33 ms mpr1.sjc7.us [206.223.116.86]
7 37 ms 32 ms 31 ms ae16.cr1.sjc2.us.zip.zayo.com [64.125.31.12]
8 77 ms 73 ms 65 ms ae12.er1.sjc2.us.zip.zayo.com [64.125.25.22]
9 31 ms 33 ms 31 ms 209.66.92.106.t00673-04.above.net [209.66.92.106]
10 84 ms 83 ms 85 ms 159.153.68.53
11 34 ms 32 ms 31 ms 159.153.68.252

 

 

 

Additional Notes:

  • Power-cycling the router has no effect. 
  • Same results when running these tests from my laptop and through a trace route app on my iPhone.

 

Question/Request:

  • Can you please look into the routing table on rc1wt-be90.wa.shawcable.net [66.163.76.66]?
    • In successful cases where the route is able to connect to a Blizzard telia.net server, rc1wt-be90.wa.shawcable.net [66.163.76.66] routes to Seattle, sea-b1-link.telia.net [62.115.9.85].
    • However, in the unsuccessful cases, rc1wt-be90.wa.shawcable.net [66.163.76.66] instead routes to rc3sj-be60.cl.shawcable.net [66.163.75.90], and does not go on to connect to a Blizzard server.
    • Should this really be routing to rc3sj-be60.cl.shawcable.net? Isn't rc3sj-be60.cl.shawcable.net out east?

 

I'm looking forward to your response.

 

Best regards,

Jeremy

Outcomes