Forum Discussion
Routing issue to Denver
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 or...
Nighthawk
Community Power User
Community Power UserCan 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’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?
TELUS_SupportOfficial Support Team
Yes, getting in touch with our Tech Support team would be your best bet. Let us know if you'd like more info with how to connect with them!
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.
- Nighthawk
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.
