Hi, I'm experiencing network problems to this IP: 84.17.63.29 Apparently, all my traffic towards that IP is experiencing network problems. I ask you to please investigate and adjust routing in order to have good networking to that destination network. This is an example that shows the routing issue I'm referring to: |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.254 - 0 | 310 | 310 | 0 | 0 | 15 | 0 | | 100.82.195.1 - 0 | 310 | 310 | 1 | 2 | 18 | 2 | | GTD-DRUM-R2.bb.telus.com - 0 | 310 | 310 | 4 | 5 | 31 | 6 | | telus-sea.cdn77.com - 0 | 310 | 310 | 4 | 5 | 23 | 6 | | vl1116.lax-cs2-core-1.cdn77.com - 0 | 310 | 310 | 64 | 65 | 82 | 65 | | Request timed out. - 100 | 62 | 0 | 0 | 0 | 0 | 0 | | Request timed out. - 100 | 62 | 0 | 0 | 0 | 0 | 0 | | hosted-by.hiperz.com - 0 | 310 | 310 | 73 | 74 | 89 | 74 | |________________________________________________|______|______|______|______|______|______| WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider) Thank you, best regards

Can you be more specific as to what the problem is? The MTR you posted does show that you are able to connect to that IP and there does not appear to be any packet loss and latency doesn't appear to be that bad for having the connection routed through Los Angeles. Which game is it for?What is the problem you are experiencing?Are there any error messages that appear?Are you using ethernet or wifi?What platform are you using? PC? Console?Any other information you can provide?Have you reached out to support from the game company?

It is a third party CS2/Faceit server hosted by Hyperz. The issue is that my ping to their Denver servers used to be ~30ms, now it is over 90ms. After troubleshooting with their engineers, they told me to reach out to Telus as there is clearly a routing issue. If I do a SpeedTest ping test to Denver, it is the expected ~30ms.

I am not an expert, but based on the tracelog my ping to LAX is way higher than it should be, and might be the cause of the way higher ping to Denver. My SpeedTest ping to LA is around 30ms, compared to the 65ms average in that tracelog.

I tested from both a Telus connection and a Shaw connection and the latency to the original IP you posted, using MTR and traceroute. The result is identical between the both of them for both wired and wireless connections. (Telus: 68ms average, Shaw: 69ms average.) Both use different paths through cdn77.com's network. Telus routes through Seattle/LA and Shaw routes through Chicago. Based on that alone, the issue won't simply be the routing that one ISP uses. For Canadians, Denver is also a bad location for a game server as there is no direct way to connect to a server there. It's always routing through one of a small number of primary US gateway servers. Chicago and Seattle are by far the most common two you'll see. The latency to Denver will be higher in general from that alone. Game servers usually have variable latency as well. The more users that connect, the more it's impacted. For some games, even some mods will impact latency. Some games will have higher latency than others also. A few are also directly impacted by latency of other users if the game employs a peer to peer style of multi-player. Others are impacted if you're using a console instead of a PC. I have never, ever seen latency to/through LA, or California in general, show up with anything close ~30ms. Historically, anything connecting through LA, or California in general, is going to have higher latency regardless of the peering. Been that way for decades, and not just for Telus either. If you want very low latency, look for a server in either Seattle or Chicago. Chicago for me has had extremely low latency depending on the game.

lax.hzTracing route to core.lax.dedicated.com [167.160.91.2]over a maximum of 30 hops:1 1 ms <1 ms <1 ms 192.168.1.2542 2 ms 1 ms 1 ms 100.82.195.13 5 ms 5 ms 5 ms 154.11.15.1964 5 ms 4 ms 4 ms six.globalsecurelayer.com [206.81.81.146]5 34 ms 34 ms 34 ms e49.lax-csla2-bb1.globalsecurelayer.com [206.148.25.6]6 34 ms 34 ms 34 ms 206.148.27.2517 35 ms 34 ms 33 ms 206.148.25.878 35 ms 34 ms 35 ms 63018.gslnetworks.com [103.137.13.185]9 36 ms 39 ms 39 ms core.lax.dedicated.com [167.160.91.2]Trace complete.lax.cdn77Tracing route to 440250527.lax.cdn77.com [185.152.67.2]over a maximum of 30 hops:1 1 ms <1 ms <1 ms 192.168.1.2542 2 ms 2 ms 1 ms 100.82.195.13 5 ms 5 ms 5 ms 154.11.15.1964 6 ms 5 ms 5 ms telus-sea.cdn77.com [45.134.215.154]5 57 ms 129 ms 57 ms vl1116.lax-cs2-core-2.cdn77.com [185.229.188.226]6 * * * Request timed out.7 66 ms 65 ms 69 ms 440250527.lax.cdn77.com [185.152.67.2]Trace complete.lax.webnxTracing route to mirrors-lax.webnx.com [104.237.63.187]over a maximum of 30 hops:1 <1 ms <1 ms <1 ms 192.168.1.2542 3 ms 1 ms 1 ms 100.82.195.13 6 ms 4 ms 4 ms GTD-DRUM-R2.bb.telus.com [154.11.15.194]4 10 ms 6 ms 5 ms be-205-pe12.seattle.wa.ibone.comcast.net [173.167.57.213]5 6 ms 6 ms 5 ms be-2312-cs03.seattle.wa.ibone.comcast.net [96.110.34.137]6 6 ms 5 ms 5 ms be-1312-cr12.seattle.wa.ibone.comcast.net [96.110.47.206]7 9 ms 9 ms 9 ms be-302-cr12.portland.or.ibone.comcast.net [96.110.38.38]8 9 ms 8 ms 8 ms be-1112-cs01.portland.or.ibone.comcast.net [96.110.46.213]9 9 ms 9 ms 8 ms be-1111-cr11.portland.or.ibone.comcast.net [96.110.46.210]10 23 ms 22 ms 22 ms be-302-cr13.sunnyvale.ca.ibone.comcast.net [96.110.36.125]11 22 ms 22 ms 22 ms be-1313-cs03.sunnyvale.ca.ibone.comcast.net [96.110.46.33]12 23 ms 22 ms 22 ms be-1312-cr12.sunnyvale.ca.ibone.comcast.net [96.110.46.30]13 22 ms 22 ms 22 ms be-302-cr12.9greatoaks.ca.ibone.comcast.net [96.110.37.174]14 23 ms 22 ms 22 ms be-1312-cs03.9greatoaks.ca.ibone.comcast.net [68.86.166.157]15 23 ms 23 ms 24 ms be-1311-cr11.9greatoaks.ca.ibone.comcast.net [68.86.166.154]16 30 ms 30 ms 30 ms be-302-cr11.losangeles.ca.ibone.comcast.net [96.110.38.93]17 38 ms 40 ms 30 ms be-1211-cs02.losangeles.ca.ibone.comcast.net [96.110.45.169]18 30 ms 30 ms 30 ms be-2201-pe01.losangeles.ca.ibone.comcast.net [96.110.44.102]19 31 ms 33 ms 30 ms 50.242.149.24620 31 ms 31 ms 31 ms 100-42-215-239.static.webnx.com [100.42.215.239]21 30 ms 30 ms 30 ms mirrors-lax.webnx.com [104.237.63.187]Trace complete.lax.colocrossingTracing route to 107-175-180-6-host.colocrossing.com [107.175.180.6]over a maximum of 30 hops:1 1 ms <1 ms <1 ms 192.168.1.2542 2 ms 2 ms 1 ms 100.82.195.13 5 ms 5 ms 5 ms 154.11.15.1964 6 ms 5 ms 5 ms sea-b1-link.ip.twelve99.net [213.248.74.220]5 25 ms 25 ms 25 ms sjo-b23-link.ip.twelve99.net [62.115.132.152]6 34 ms 33 ms 34 ms lax-b23-link.ip.twelve99.net [62.115.116.41]7 34 ms 34 ms 34 ms lax-b22-link.ip.twelve99.net [62.115.143.39]8 34 ms 34 ms 34 ms hostpapa-ic-317204.ip.twelve99-cust.net [62.115.146.157]9 * * * Request timed out.10 34 ms 33 ms 33 ms 107-175-180-6-host.colocrossing.com [107.175.180.6]Trace complete. As you can see, my ping to LA is in the 30ms range, except for the cdn77 route, which is the same route that is causing the issue when I connect to the Denver server. Nighthawk - I get 32ms to LA (Valve server) and 28ms to San Jose (third party server) on CS2.

Routing issue to Denver | TELUS Neighbourhood

16 Replies

calamity1
Neighbour
7 months ago
I'm experiencing the same issues as tact and Moh. Seeing the responses to their complaints greatly prevents my decision to upgrading to a business plan.

Here are the original/optimal trace-routes towards denver IPs within hiperZ:

Tracing route to hosted-by.hiperz.com [84.17.63.106]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 10.31.192.1
2 5 ms 5 ms 5 ms GTD-DRUM-R2.bb.telus.com [154.11.15.194]
3 5 ms 6 ms 5 ms be-205-pe12.seattle.wa.ibone.comcast.net [173.167.57.213]
4 30 ms 30 ms 30 ms be-3412-pe12.910fifteenth.co.ibone.comcast.net [96.110.33.142]
5 33 ms 33 ms 33 ms 50.248.116.242
6 * * * Request timed out.
7 33 ms 33 ms 33 ms hosted-by.hiperz.com [84.17.63.106]

Tracing route to hosted-by.hiperz.com [84.17.63.96]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 10.31.192.1
2 * * 1 ms 173.182.212.84
3 * * * Request timed out.
4 * * * Request timed out.
5 32 ms 33 ms 33 ms 50.248.116.242
6 * * * Request timed out.
7 32 ms 33 ms 33 ms hosted-by.hiperz.com [84.17.63.96]

Today:

Tracing route to hosted-by.hiperz.com [84.17.63.96]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.31.192.1
2 1 ms <1 ms <1 ms 173.182.212.82
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 81 ms 80 ms 80 ms hosted-by.hiperz.com [84.17.63.96]

Tracing route to hosted-by.hiperz.com [84.17.63.106]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.31.192.1
2 <1 ms <1 ms <1 ms 173.182.212.82
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 81 ms 81 ms 81 ms hosted-by.hiperz.com [84.17.63.106]

Can a business plan help influence these routes or at least provide a direct line to solve routing issues?
- TELUS_Support
  Official Support Team
  6 months ago
  Not entirely sure a Business plan would do much in terms of resolving the issue. You could contact the provider of that destination URL to inquire further.
  - calamity1
    Neighbour
    6 months ago
    Starting to see what Moh means. You guys probably read what they read and seem helpful.
Moh096
Friendly Neighbour
10 months ago
I’ve already contacted TELUS Tech Support, but they were unable to resolve my issue. I need this issue escalated to someone who can investigate the routing problem. Is there another way to get this properly addressed?
Also, I know other ISPs have optimized routing when customers reported similar issues. Can you confirm if TELUS can do the same?
- TELUS_Support
  Official Support Team
  10 months ago
  If you still require assistance, send us a private message and get someone to contact you.
Moh096
Friendly Neighbour
10 months ago
.
tact
Friendly Neighbour
2 years ago
lax.hz
Tracing route to core.lax.dedicated.com [167.160.91.2]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 1 ms 1 ms 100.82.195.1
3 5 ms 5 ms 5 ms 154.11.15.196
4 5 ms 4 ms 4 ms six.globalsecurelayer.com [206.81.81.146]
5 34 ms 34 ms 34 ms e49.lax-csla2-bb1.globalsecurelayer.com [206.148.25.6]
6 34 ms 34 ms 34 ms 206.148.27.251
7 35 ms 34 ms 33 ms 206.148.25.87
8 35 ms 34 ms 35 ms 63018.gslnetworks.com [103.137.13.185]
9 36 ms 39 ms 39 ms core.lax.dedicated.com [167.160.91.2]
Trace complete.

lax.cdn77
Tracing route to 440250527.lax.cdn77.com [185.152.67.2]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 1 ms 100.82.195.1
3 5 ms 5 ms 5 ms 154.11.15.196
4 6 ms 5 ms 5 ms telus-sea.cdn77.com [45.134.215.154]
5 57 ms 129 ms 57 ms vl1116.lax-cs2-core-2.cdn77.com [185.229.188.226]
6 * * * Request timed out.
7 66 ms 65 ms 69 ms 440250527.lax.cdn77.com [185.152.67.2]
Trace complete.

lax.webnx
Tracing route to mirrors-lax.webnx.com [104.237.63.187]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 3 ms 1 ms 1 ms 100.82.195.1
3 6 ms 4 ms 4 ms GTD-DRUM-R2.bb.telus.com [154.11.15.194]
4 10 ms 6 ms 5 ms be-205-pe12.seattle.wa.ibone.comcast.net [173.167.57.213]
5 6 ms 6 ms 5 ms be-2312-cs03.seattle.wa.ibone.comcast.net [96.110.34.137]
6 6 ms 5 ms 5 ms be-1312-cr12.seattle.wa.ibone.comcast.net [96.110.47.206]
7 9 ms 9 ms 9 ms be-302-cr12.portland.or.ibone.comcast.net [96.110.38.38]
8 9 ms 8 ms 8 ms be-1112-cs01.portland.or.ibone.comcast.net [96.110.46.213]
9 9 ms 9 ms 8 ms be-1111-cr11.portland.or.ibone.comcast.net [96.110.46.210]
10 23 ms 22 ms 22 ms be-302-cr13.sunnyvale.ca.ibone.comcast.net [96.110.36.125]
11 22 ms 22 ms 22 ms be-1313-cs03.sunnyvale.ca.ibone.comcast.net [96.110.46.33]
12 23 ms 22 ms 22 ms be-1312-cr12.sunnyvale.ca.ibone.comcast.net [96.110.46.30]
13 22 ms 22 ms 22 ms be-302-cr12.9greatoaks.ca.ibone.comcast.net [96.110.37.174]
14 23 ms 22 ms 22 ms be-1312-cs03.9greatoaks.ca.ibone.comcast.net [68.86.166.157]
15 23 ms 23 ms 24 ms be-1311-cr11.9greatoaks.ca.ibone.comcast.net [68.86.166.154]
16 30 ms 30 ms 30 ms be-302-cr11.losangeles.ca.ibone.comcast.net [96.110.38.93]
17 38 ms 40 ms 30 ms be-1211-cs02.losangeles.ca.ibone.comcast.net [96.110.45.169]
18 30 ms 30 ms 30 ms be-2201-pe01.losangeles.ca.ibone.comcast.net [96.110.44.102]
19 31 ms 33 ms 30 ms 50.242.149.246
20 31 ms 31 ms 31 ms 100-42-215-239.static.webnx.com [100.42.215.239]
21 30 ms 30 ms 30 ms mirrors-lax.webnx.com [104.237.63.187]
Trace complete.

lax.colocrossing
Tracing route to 107-175-180-6-host.colocrossing.com [107.175.180.6]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 1 ms 100.82.195.1
3 5 ms 5 ms 5 ms 154.11.15.196
4 6 ms 5 ms 5 ms sea-b1-link.ip.twelve99.net [213.248.74.220]
5 25 ms 25 ms 25 ms sjo-b23-link.ip.twelve99.net [62.115.132.152]
6 34 ms 33 ms 34 ms lax-b23-link.ip.twelve99.net [62.115.116.41]
7 34 ms 34 ms 34 ms lax-b22-link.ip.twelve99.net [62.115.143.39]
8 34 ms 34 ms 34 ms hostpapa-ic-317204.ip.twelve99-cust.net [62.115.146.157]
9 * * * Request timed out.
10 34 ms 33 ms 33 ms 107-175-180-6-host.colocrossing.com [107.175.180.6]
Trace complete.

As you can see, my ping to LA is in the 30ms range, except for the cdn77 route, which is the same route that is causing the issue when I connect to the Denver server.

Nighthawk - I get 32ms to LA (Valve server) and 28ms to San Jose (third party server) on CS2.
Nighthawk
Community Power User
2 years ago
Can you be more specific as to what the problem is? The MTR you posted does show that you are able to connect to that IP and there does not appear to be any packet loss and latency doesn't appear to be that bad for having the connection routed through Los Angeles.

Which game is it for?
What is the problem you are experiencing?
Are there any error messages that appear?
Are you using ethernet or wifi?
What platform are you using? PC? Console?
Any other information you can provide?
Have you reached out to support from the game company?
- tact
  Friendly Neighbour
  2 years ago
  It is a third party CS2/Faceit server hosted by Hyperz. The issue is that my ping to their Denver servers used to be ~30ms, now it is over 90ms. After troubleshooting with their engineers, they told me to reach out to Telus as there is clearly a routing issue. If I do a SpeedTest ping test to Denver, it is the expected ~30ms.
  - Moh096
    Friendly Neighbour
    10 months ago
    I’m experiencing the same issue on FACEIT, where the routing to certain servers like Chicago, Dallas, and Denver is causing high ping. As a workaround, I tried ExitLag, which significantly reduced my ping, but it comes at an additional cost.
    
    I’ll be contacting Telus regarding this issue as well to see if they can optimize the routing.
    
    Did Telus end up fixing your issue?