AnsweredAssumed Answered

Bad Routing to Midwest and East Coast Servers

Question asked by osials on Nov 25, 2017
Latest reply on May 1, 2018 by xtess3ractx

Hello,

 

When gaming, I've noticed poor latency to game servers in the Midwest and East regions. This has rendered gaming unplayable. It appears that the Winnipeg hop is incorrectly configured. Shaw's Winnipeg hop is causing all traffic to go to Calgary, Vancouver, and all the way back to the Midwest or East regions. Little did I know this was going to occur when switching over from TbayTel. Although unstable at times due to DSL's inherent flaws, my connection to game servers in these regions was fine. The reason why I switched was to get faster internet speeds and not to render gaming unplayable. Please investigate the routing table at the Winnipeg hop, and if there doesn't seem to be a problem with the routing table, then there must be a physical issue there at the CMTS. There has got to be a way for Winnipeg to pass traffic across the border the same way that Vancouver does. Below is a tracert example of where my game traffic was being directed. The issue begins at hops 3, 4, and 5. Thank you for your time.

 

Iowa Server

Tracing route to 52.165.155.89 over a maximum of 30 hops

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 * * * Request timed out.
3 36 ms 18 ms 15 ms rc2nr-tge0-1-0-5-1.wp.shawcable.net [64.59.179.149]
4 38 ms 42 ms 35 ms rc3no-be110-1.cg.shawcable.net [66.163.76.57]
5 53 ms 48 ms 45 ms rc1st-be11-1.vc.shawcable.net [66.163.72.70]
6 48 ms 49 ms 46 ms 104.44.12.96
7 75 ms 68 ms 65 ms ae5-0.wst-96cbe-1b.ntwk.msn.net [104.44.225.218]
8 91 ms 88 ms 85 ms be-72-0.ibr02.stb.ntwk.msn.net [104.44.8.70]
9 92 ms 89 ms 84 ms be-6-0.ibr01.cnr03.mwh01.ntwk.msn.net [104.44.4.102]
10 90 ms 88 ms 84 ms be-7-0.ibr01.cnr04.cys04.ntwk.msn.net [104.44.4.123]
11 85 ms 89 ms 85 ms be-2-0.ibr01.cnr01.cys04.ntwk.msn.net [104.44.4.187]
12 93 ms 89 ms 86 ms be-6-0.ibr01.den07.ntwk.msn.net [104.44.4.113]
13 94 ms 85 ms 84 ms be-1-0.ibr02.den07.ntwk.msn.net [104.44.4.59]
14 90 ms 89 ms 85 ms be-5-0.ibr01.cnr03.dsm05.ntwk.msn.net [104.44.4.96]
15 86 ms 84 ms 83 ms ae103-0.icr02.dsm05.ntwk.msn.net [104.44.10.109]
16 * * * Request timed out.

Trace complete.

 

Virginia Server

Tracing route to 69.174.216.49 over a maximum of 30 hops

1 1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 * * * Request timed out.
3 24 ms 19 ms 16 ms rc2nr-tge0-1-0-5-1.wp.shawcable.net [64.59.179.149]
4 43 ms 39 ms 33 ms rc3no-be110-1.cg.shawcable.net [66.163.76.57]
5 49 ms 55 ms 46 ms rc1st-be11-1.vc.shawcable.net [66.163.72.70]
6 57 ms 48 ms 48 ms rx0wh-limelight.vc.shawcable.net [66.163.68.170]
7 49 ms 49 ms 45 ms lag1.fr4.yxx1.llnw.net [69.164.28.9]
8 81 ms 75 ms 77 ms 68.142.88.185
9 95 ms 79 ms 78 ms lag26.fr4.lga.llnw.net [68.142.88.149]
10 93 ms 93 ms 88 ms lag29.fr4.iad.llnw.net [68.142.88.134]
11 105 ms 106 ms 98 ms sony.ge4-12.fr4.iad.llnw.net [69.28.156.214]
12 105 ms 109 ms 98 ms 69.174.216.49

Trace complete.

Outcomes