 alamarcoThe Amazing Spider-ManPremium
join:2003-06-18
Windsor, ON
 ·Cogeco Cable
| [Windsor] Speed/Latency Issues1)What, specifically, is your issue?: Slow speeds, bad ping.
a) Is there a specific time that this issue is most prevalent?: No specific time frame, happens all day.
b) How long has this issue been going on?: Issue has been happening for a while. I'd estimate months, though I don't have data throughout.
2) Do you have cable TV? If so, is there any reception degradation..what channels?: Yes I have cable TV, and no there has been no reception degradation that I know of.
3) Have you contacted customer support about this problem? If so, what did they say?: No contact with customer support. I hate long wait times and generally hate speaking over the phone so I'd prefer over the forum.
4) What troubleshooting steps have you taken to resolve this problem?:
I've turned off QOS on my router and get the same speed results. I've plugged my modem directly into my PC and get the same results. I've also recently got a new router (went from LINKSYS WRT54GSv4 to ASUS RT-N16) which is a newer, more powerful router.
I also experimented with DNS servers (switching from the default Cogeco servers) thinking it might of been the DNS servers, but I quickly found out through tests that Cogeco's DNS servers are the best in the area so I've been running on Cogeco servers again.
5) Info about you:
a) What city are you in? Windsor
b) What is your operating system?: Win7 64-bit
c) What is your home network setup?
- Cogeco modem plugged into ASUS RT-N16 router which is flashed with Tomato v1.28
- I have one PC (wired) on 24/7 which rarely sees network activity besides local activity as it acts as a print server
- I have one PC (wired) on 24/7 which acts as as a file server (this was off during the tests)
- I have one PC (wired) on 24/7 which I use for general use (this was on and was where I did the tests)
- There are a few laptops which connect wirelessly, but these are off for most of the day (also off during the tests)
- I have an XBOX 360 (wired) and PS3 (wireless) which were also off during the tests
d) If you have more than one computer, is the problem occuring on all other machines?: Issue occurs on all machines.
e) Are you running a firewall of any sort? Have you ever installed one?: Using the Win7 default firewall, no other firewall was ever installed (recently reformatted)
f) Please supply a traceroute from you to www.dslreports.com. Unedited and in text format.
tracert www.dslreports.com
Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 45 ms 21 ms 10.88.0.1
3 16 ms 22 ms 23 ms d226-4-209.home.cgocable.net [24.226.4.209]
4 22 ms 13 ms 31 ms d226-6-137.home.cgocable.net [24.226.6.137]
5 55 ms 75 ms 117 ms gw-nac.torontointernetxchange.net [206.108.34.38
]
6 38 ms 104 ms 48 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
7 111 ms 48 ms 39 ms vlan804.esd1.oct.nac.net [209.123.10.2]
8 70 ms 88 ms 72 ms www.dslreports.com [209.123.109.175]
Trace complete.
ping -n 10 www.dslreports.com
Pinging www.dslreports.com [209.123.109.175] with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=124ms TTL=57
Reply from 209.123.109.175: bytes=32 time=121ms TTL=57
Reply from 209.123.109.175: bytes=32 time=55ms TTL=57
Reply from 209.123.109.175: bytes=32 time=70ms TTL=57
Reply from 209.123.109.175: bytes=32 time=61ms TTL=57
Reply from 209.123.109.175: bytes=32 time=48ms TTL=57
Reply from 209.123.109.175: bytes=32 time=92ms TTL=57
Reply from 209.123.109.175: bytes=32 time=120ms TTL=57
Reply from 209.123.109.175: bytes=32 time=73ms TTL=57
Reply from 209.123.109.175: bytes=32 time=55ms TTL=57
Ping statistics for 209.123.109.175:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 124ms, Average = 81ms
 |
alamarcoThe Amazing Spider-ManPremium
join:2003-06-18
Windsor, ON Reviews:
·Cogeco Cable
| Todays results:
tracert www.dslreports.com
Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 31 ms 10.88.0.1
3 40 ms 35 ms 83 ms d226-4-209.home.cgocable.net [24.226.4.209]
4 14 ms 14 ms 20 ms d226-6-137.home.cgocable.net [24.226.6.137]
5 47 ms 37 ms 36 ms gw-nac.torontointernetxchange.net [206.108.34.38
]
6 44 ms 70 ms 37 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
7 76 ms 54 ms 36 ms vlan804.esd1.oct.nac.net [209.123.10.2]
8 52 ms 93 ms 96 ms www.dslreports.com [209.123.109.175]
Trace complete.
ping -n 10 www.dslreports.com
Pinging www.dslreports.com [209.123.109.175] with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=113ms TTL=57
Reply from 209.123.109.175: bytes=32 time=37ms TTL=57
Reply from 209.123.109.175: bytes=32 time=38ms TTL=57
Reply from 209.123.109.175: bytes=32 time=114ms TTL=57
Reply from 209.123.109.175: bytes=32 time=37ms TTL=57
Reply from 209.123.109.175: bytes=32 time=36ms TTL=57
Reply from 209.123.109.175: bytes=32 time=59ms TTL=57
Reply from 209.123.109.175: bytes=32 time=54ms TTL=57
Reply from 209.123.109.175: bytes=32 time=36ms TTL=57
Reply from 209.123.109.175: bytes=32 time=131ms TTL=57
Ping statistics for 209.123.109.175:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 131ms, Average = 65ms
 |
