AnsweredAssumed Answered

Potential severe routing issues between Shaw and Riot Games 22/12/2015

Question asked by mdudzicz1 on Dec 22, 2015
Latest reply on Feb 18, 2016 by eunson

Good evening!

 

I have reached out to several representatives on live support so far, with only 1 actually saying they will escalate the matter to the engineering team, but just in case I have decided to open my own forum about it so it gets more exposure, because it's a very big deal for myself and the entire Edmonton League of Legends community who games competitively. That being said, lets get to the issue at hand!

 

While in-game, the normal ping should be around 40-45ms, but recently (today and last night) there seems to be a major issue with another server that is being routed with Riot and Shaw that is resulting in consistent 170-180ms in-game latency, which is virtually unplayable. That being said, when I troubleshooted further with tracerts to specific IP's, including Riot's Chicago server, it results in 40ms to one server (hop 7), but on hop 5 it shows a consistent 170-180ms spike. The scenario in the game itself is like this. I've played 3 games today, with 2 of them having completely fine pings (45ms), and then I queued up again for a 3rd and my ping was 180ms consistently, and I continuously remade custom matches to confirm that the game has 2 servers routing with Shaw, sometimes resulting in normal pings, and sometimes with 180ms. Pretty much a 50/50 gamble at this point, so there's really no point in playing the game at all until this is fixed (i'm a competitive high ranked player).

 

This is the tracert to Riot's Chicago server:

 

C:\Users\mdudzicz1>tracert 104.160.131.35

Tracing route to 104.160.131.35 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2     8 ms     7 ms     7 ms  mdudzicz1-PC [0.0.0.0]

  3    11 ms    11 ms    11 ms  rc3ar-tge0-14-0-14-1.ed.shawcable.net [64.59.184

.169]

  4    25 ms    25 ms    27 ms  rc1ar-ge2-0-0.ed.shawcable.net [66.163.70.33]

  5   176 ms   170 ms   178 ms  rc4ec-hge0-9-0-1.il.shawcable.net [66.163.77.202]

  6    39 ms    44 ms    39 ms  eqix-ch2.chi01.riotdirect.net [206.223.119.235]

  7    40 ms    39 ms    40 ms  104.160.131.35

Trace complete.

 

I have checked every viable solution with the help of the live support representative, and we have confirmed it is NOT my own issue as my internet is perfectly fine, firewall is fine, and everything on Shaw's end specifically outside of Edmonton is fine, so it's a guaranteed Edmonton or further area routing issue. That being said, I have confirmed with several other Edmonton league of legends players with Shaw who all have the same exact issue and ping.

 

If there is any additional troubleshooting that needs to be done, please let me know, but i'm 100% confident I have done everything in my power to ensure it's not just me, but rather a network issue on one of the party's ends. This is an extremely frustrating issue to encounter again as this isn't the first time Shaw has had severe routing issues with Riot and their new Chicago network. The faster this gets resolved, the better.

 

Thanks!

 

Mike

Outcomes