AnsweredAssumed Answered

Is there any way to improve Shaw routing and high pings?

Question asked by defunct on Sep 17, 2014
Latest reply on Sep 18, 2014 by defunct

I have the current luxury of having both Shaw and Telus in my house. I have free Telus internet for a year due to some contract with my building and the routing on Telus so much better that I'm hoping Shaw can do something about it. Games constantly freeze up for me during certain times.

 

Well, you guys can compare for yourselves. Below are traceroutes taken a few minutes apart, on the same computer. Both direct wired connections, although the Shaw one is through my Linksys router and the Telus is though a wall wire direct to their modem/router combo.

 

Hopefully something can be done about this.

 

Shaw:

C:\Windows\System32>tracert 208.94.25.45

 

Tracing route to 208.94.25.45 over a maximum of 30 hops

 

  1     6 ms     8 ms     1 ms  10.44.129.50

  2     *        *        *     Request timed out.

  3    18 ms    19 ms    13 ms  rd3bb-tge0-5-0-11-1.vc.shawcable.net [64.59.149.153]

  4    19 ms    16 ms    22 ms  rc2bb-tge0-13-0-4.vc.shawcable.net [66.163.69.81]

  5    21 ms    19 ms    29 ms  rc2wh-tge0-7-1-0.vc.shawcable.net [66.163.69.73]

  6    49 ms    56 ms    42 ms  rc4sj-pos0-7-5-0.cl.shawcable.net [66.163.77.234]

  7    41 ms    44 ms    39 ms  be-10-204-pe01.11greatoaks.ca.ibone.comcast.net [75.149.229.61]

  8    55 ms    55 ms    51 ms  pos-2-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.87.161]

  9    67 ms    67 ms    80 ms  he-2-9-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.86.102]

10   176 ms   175 ms   195 ms  he-0-9-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.87.254]

11   176 ms   179 ms   179 ms  be-15-pe02.1950stemmons.tx.ibone.comcast.net [68.86.83.114]

12   162 ms   158 ms   158 ms  66.208.216.210

13   173 ms   172 ms   176 ms  208.94.25.45

 

Trace complete.

 

Telus:

C:\Windows\System32>tracert 208.94.25.45

 

Tracing route to 208.94.25.45 over a maximum of 30 hops

 

  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2     7 ms     8 ms     6 ms  10.31.180.1

  3     9 ms     9 ms    10 ms  STTLWAWBCI01.bb.telus.com [75.154.217.106]

  4    10 ms     9 ms     9 ms  sea-brdr-02.inet.qwest.net [63.146.27.225]

  5     *        *        *     Request timed out.

  6    78 ms    78 ms    78 ms  67.133.189.94

  7    77 ms    77 ms    77 ms  border2.pc2-bbnet2.dal004.pnap.net [216.52.191.82]

  8    58 ms    58 ms    58 ms  trionwn-4.border2.dal004.pnap.net [72.5.252.70]

  9    56 ms    56 ms    57 ms  208.94.25.45

 

Trace complete.

 

 

 

Outcomes