said by nss_tech:Oh really? I find that hard to believe you have any email address for someone that far up the food chain. Not even the tech support people nor their managers have any way to contact anyone dealing with routing. There won't be any changes unless a rather large percentage of users start complaining, loudly. Or at the very least, something that drastically effects the connection performance (peering not local) and a few extra milliseconds in latency won't even register as an issue.
Below is a direct quote of a reply from the peering folks at Telus:
TELUS is looking at what can be done to improve the latency from Alberta to the Riot game servers. We are reaching out to Riot Games to see if we can setup a direct peering relationship in Seattle, but this will take 3 weeks to complete once agreement to peer is in place.
For western canada, TELUS exchanges most of our Internet traffic in Seattle and Chicago so we have diverse Internet exchange points. We also implement some peering connections in Palo Alto and LA. I understand that latency is very important to gamers and reaching the west coast game servers via Chicago is not optimal. Improving latency is very difficult to engineer from a BGP perspective. BGP is not based upon geography and BGP routes don't indicate their origin location. TELUS will see the same BGP routes presented in both Seattle and Chicago with no way to easily select the optimal path. There are almost 500,000 IPV4 BGP routes now and it is not possible to micro-engineer the optimal path for each BGP route. In addition, BGP is completely asymmetric with TELUS only having visibility and control over our BGP exit routes. Without traceroutes, we have no idea how Internap or Riot Games servers are routing their return traffic to TELUS. Both companies have extensive peering connections and its unlikely their return path is the same as the TELUS forward path.
Given the BGP complications, the most straightforward solution is to peer directly with Riot Games and we will proceed with that.
******.
-----Original Message-----
From: darhole [mailto:*****@telus.net]
Sent: March 2, 2014 03:45 PM
To: PEERING
Subject: Slow routing to west coast - Riot League of Legends specifically
Hello,
For the past (at least) month, I have noticed some very odd routing and latency to the west coast.
I play League of Legends regularly, and their servers are all west coast, primarily in California.
When I switched from my Shaw service last March, I was pinging between 60-70ms to the Riot servers. For the past few months, this ping is averaging 105-115. I ran some traceroutes and noticed something extremely bizarre: all traffic to riot is being routed from Edmonton to Chicago as follows:
Edmonton AB > Chicago > Illinois > Colorado > Seattle > Oregon > California
I had a Telus subscriber near Vancouver run the same traceroutes to the IP ranges Riot uses, and his traffic was being run from Vancouver to Seattle and skipping the whole Chicago step. As such, the ping was 50ms to California.
Interestingly, I take a proper route to Valve's servers located in the same general area. I believe they peer differently with Telus however.
I'm having a hard time believing this is a BGP issue, as I can't see why Chicago would ever win out over a hop in BC internally that was shorter and faster.
I have done every bit of troubleshooting possible on my end. Latest firmware, factory resets, three different devices, wired connections (different cables). The connection is stable, just too high of a ping to compete in a live online game.
I have had my profile adjusted a few times to try and save a few ms that way, nothing has been beneficial.
I can handle 70ms, 105 is too high of a delay to compete in this game.
I love Telus, I love your technical support, the service is great. However, in my limited free time I like to play this game, and unfortunately it is a deal breaker if I cannot do so.
If nothing can be done, I will have to look at switching back to Shaw, as much as it pains me to do so. I am really hoping this is fixable!
Thanks,
********
Account #*******
E-mailing the right people does help. BOOM!