So still waiting on an answer from shaw. Them forkers be slow. I should be getting 25/2.5. got an update to my ticket today tek still has no answer from shaw.
C:\Users\I5>ping www.google.ca -n 50
Pinging www.google.ca [74.125.196.94] with 32 bytes of data: Reply from 74.125.196.94: bytes=32 time=118ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=112ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=111ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=114ms TTL=30 Reply from 74.125.196.94: bytes=32 time=111ms TTL=30 Reply from 74.125.196.94: bytes=32 time=111ms TTL=30 Reply from 74.125.196.94: bytes=32 time=114ms TTL=30 Reply from 74.125.196.94: bytes=32 time=114ms TTL=30 Reply from 74.125.196.94: bytes=32 time=110ms TTL=30 Reply from 74.125.196.94: bytes=32 time=117ms TTL=30 Reply from 74.125.196.94: bytes=32 time=123ms TTL=30 Reply from 74.125.196.94: bytes=32 time=117ms TTL=30 Reply from 74.125.196.94: bytes=32 time=113ms TTL=30 Reply from 74.125.196.94: bytes=32 time=114ms TTL=30 Reply from 74.125.196.94: bytes=32 time=131ms TTL=30 Reply from 74.125.196.94: bytes=32 time=114ms TTL=30 Reply from 74.125.196.94: bytes=32 time=116ms TTL=30 Reply from 74.125.196.94: bytes=32 time=112ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=113ms TTL=30 Reply from 74.125.196.94: bytes=32 time=111ms TTL=30 Reply from 74.125.196.94: bytes=32 time=118ms TTL=30 Reply from 74.125.196.94: bytes=32 time=114ms TTL=30 Reply from 74.125.196.94: bytes=32 time=129ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=123ms TTL=30 Reply from 74.125.196.94: bytes=32 time=110ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=113ms TTL=30 Reply from 74.125.196.94: bytes=32 time=114ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=121ms TTL=30 Reply from 74.125.196.94: bytes=32 time=116ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=116ms TTL=30 Reply from 74.125.196.94: bytes=32 time=113ms TTL=30 Reply from 74.125.196.94: bytes=32 time=116ms TTL=30 Reply from 74.125.196.94: bytes=32 time=112ms TTL=30 Reply from 74.125.196.94: bytes=32 time=121ms TTL=30 Reply from 74.125.196.94: bytes=32 time=115ms TTL=30 Reply from 74.125.196.94: bytes=32 time=111ms TTL=30 Reply from 74.125.196.94: bytes=32 time=116ms TTL=30 Reply from 74.125.196.94: bytes=32 time=119ms TTL=30 Reply from 74.125.196.94: bytes=32 time=112ms TTL=30 Reply from 74.125.196.94: bytes=32 time=114ms TTL=30 Reply from 74.125.196.94: bytes=32 time=124ms TTL=30
Ping statistics for 74.125.196.94: Packets: Sent = 50, Received = 50, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 110ms, Maximum = 131ms, Average = 115ms
This is getting to be BS. weeks waiting on an install then this and my speeds have not worked right from the start. oh well it is what it is I guess.
ok done that made a post. called in today and shaw again just said everything is ok on their end. I know the shaw installer tested the single when he was here and said it was fine only thing lift is maybe it's the modem?
Seems if I want to risk it being that I send it in I may get hit with a $25 restocking fee.