This problem has been ongoing for over a year. Sometimes it's good, sometimes bad, mostly OK, but when bad strikes, it really strikes.
My download speeds range between 1.63 Mbps up to highest in three years was 28.47 Mbps
My uploads 0.25 Mbps to highest of 0.91 a long way from the "up to 2.5 Mbps..."
Modem is a Motorola SP 5120
I understand "up to" means anywhere from no connection up to 25 Mbps. However.... my "up to" is usually not even close.
Avoiding the generic cut & paste stuff, I already have dealt with:
- history, computer,
- location and modem/router/computer reboots (yes - in the right order).
The problem can be duplicated.
Pinging shaw.ca [126.96.36.199] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out. and on and on and ....
The usual result from tracert:
Tracing route to shaw.ca [188.8.131.52]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.0.1
2 11 ms 11 ms 12 ms 184.108.40.206
3 16 ms 14 ms 16 ms tl21fv.ok.shawcable.net [220.127.116.11]
4 27 ms 31 ms 31 ms 18.104.22.168
5 23 ms 24 ms 23 ms rd1so-ge1-0-0.cg.shawcable.net [22.214.171.124]
6 22 ms 23 ms 24 ms 126.96.36.199 <----- this was in line 5 yesterday
7 * * * Request timed out.
8 * ^C and on and on and on...
It was suggested I switch to and use Google's DNS. I'm too young to give the other half of my soul to the devil!
Shaw Kelowna's stats Nov 18, 2010 - May 19, 2013: 24.36/3.2
I hope that when I click 'submit' that it doesn't time out.
Connections are hit and miss with timeouts. Downloads - sure, anything under 35k seems to make it. A plain txt file at 258 K timed out 3 times before it finally made it. FTP 0.4 up and down. But that is sometimes, not constant. Speed is not speed,
This has been tested on 3 computers. One XP, one Vista 32/ and again 64, and Win 7. No change.
The tests have been done several times a day for the last few weeks. Results are the same.
I've spoken with a super tech (tell the head of HR he should have the rest of the week off with pay) We did a few things, and at the time most sites timed out, but when they no longer did, we assumed it was fixed, but the problem persists.