AnsweredAssumed Answered

TERRIBLE Shaw Performance in East End Sault Ste Marie

Question asked by jstrach on Feb 25, 2014
Latest reply on Feb 26, 2014 by jstrach

Both me and a friend (in separate households in the same area of town) that appear to be on the same node in the East end of Sault Ste Marie are experiencing absolutely terrible performance from Shaw 25 internet around peak hours EVERY DAY.

 

These are extremely common and no matter how many times I call in to report the problem I get the standard troubleshooting technical support steps of

1 - Unplug, replug cable mode.

2 - Straight connection without a router.

3 - Restart computer

4 - Blame computer for the problem.

 

None of these troubleshooting steps work (obviously) and my friend that's also experiencing issues has a direct connection to the internet using the included modem router combo and is getting the EXACT same speedtest results at both speedtest.net and speedtest.shaw.ca.

 

There is absolutely nothing going on on my home network at the moment that would saturate my bandwidth.

Please advice, I'm out of ideas.

 

TRACERT ->

>tracert shaw.ca

 

Tracing route to shaw.ca [204.209.208.8]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2     *        *        *     Request timed out.

  3   376 ms   439 ms   400 ms  rd3sm-ge3-0-0-1.su.shawcable.net [24.244.10.21]

  4   435 ms   493 ms   387 ms  rd2sm-ge4-2.su.shawcable.net [66.163.66.134]

  5   373 ms   407 ms   434 ms  rc2nr-tge0-0-0-16.wp.shawcable.net [66.163.76.230]

  6   444 ms   364 ms   305 ms  rc3no-tge0-11-0-16.cg.shawcable.net [66.163.64.193]

  7   347 ms   258 ms   334 ms  24.244.50.34

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

10     *        *        *     Request timed out.

11     *        *        *     Request timed out.

12     *        *        *     Request timed out.

13     *        *        *     Request timed out.

14     *        *        *     Request timed out.

15     *        *        *     Request timed out.

 

I am attaching some screenshots showing the problem.

Screenshot 2014-02-25 21.31.02.pngScreenshot 2014-02-25 21.52.38.pngScreenshot 2014-02-25 21.27.56.png

Outcomes