I have Charter 3MB connection with no bad issues for the passed 2 years.
Now @ 9 PM for the passed 3 days my connection slows to a crawl for example at 7pm I run speed test and i get 1.5MB/s and at 9:30PM I get 40kb/s this has been happening for a while now and the signal seems to die around 2 AM and I get no connection until about 9 AM the next day. I have called charter each day and jumped thru all there hoops still with no fix in place yet.
Has any one else had a similar problem? Is there anything I can do to fix it?
they are sending me a QCR batch file but I have not recvied it as of yet if any one knows a place where I can down load a QCR batch file please let me know I just want my internet to work 9PM is Prime surfing time for me
You could perform a traceroute during normal times to see what the issue is.
If you can isolate the latency to a hop on thier network, you can send them the info and make them investigate it.
Eg: Trace when everything is fine.
funk@ubuntu:~$ traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 64.233.187.99
traceroute to google.com (64.233.187.99), 30 hops max, 38 byte packets
1 cpe-066-026-000-000.nc.res.rr.com (66.26.000.000) 1.579 ms 1.569 ms 1.611 ms
2 10.47.160.1 (10.47.160.1) 8.220 ms 8.022 ms 6.661 ms
3 pos1-0.rlghnck-rtr1.nc.rr.com (24.25.1.113) 8.956 ms 8.174 ms 7.995 ms
4 srp4-0.rlghnca-rtr2.nc.rr.com (24.25.2.146) 8.817 ms 13.090 ms 9.592 ms
5 pos14-0.rlghncrdc-rtr2.nc.rr.com (24.25.0.9) 10.288 ms 8.988 ms 7.757 ms
6 son1-0-1.chrlncsa-rtr6.carolina.rr.com (24.93.64.81) 15.776 ms 15.707 ms 13.872 ms
7 pop1-cha-P2-0.atdn.net (66.185.138.77) 15.169 ms 19.602 ms 15.839 ms
8 bb1-cha-P3-0.atdn.net (66.185.138.64) 17.118 ms 13.775 ms 14.121 ms
9 bb1-atm-P6-0.atdn.net (66.185.152.182) 19.321 ms 20.242 ms 20.166 ms
10 pop2-atm-P0-3.atdn.net (66.185.138.41) 19.973 ms 19.713 ms 20.606 ms
11 Google.atdn.net (66.185.147.218) 29.619 ms 29.772 ms 30.200 ms
12 72.14.236.173 (72.14.236.173) 31.361 ms 31.255 ms 72.14.236.175 (72.14.236.175) 30.077 ms
13 216.239.49.222 (216.239.49.222) 34.048 ms 216.239.49.226 (216.239.49.226) 32.441 ms 34.112 ms
14 64.233.187.99 (64.233.187.99) 31.417 ms 29.799 ms 30.200 ms
You'll notice that my last Road Runner hop is #6
6 son1-0-1.chrlncsa-rtr6.carolina.rr.com (24.93.64.81) 15.776 ms 15.707 ms 13.872 ms
I'm getting less than 20ms delay to this connection. That is good, RR is doing their job. After that I'm hitting atdn (backbone internet).
Notice that I don't see any real slow down all the way to google.
Now, if you ran the same ping while the issue is happening and were getting high latency or timeouts anywhere on the first 6 hops (in my scenario), you could tell your provider that the slow down is on their network.
Eg: Trace when issues happening
funk@ubuntu:~$ traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 64.233.187.99
traceroute to google.com (64.233.187.99), 30 hops max, 38 byte packets
1 cpe-066-026-000-000.nc.res.rr.com (66.26.000.000) 1.579 ms 1.569 ms 1.611 ms
2 10.47.160.1 (10.47.160.1) 8.220 ms 8.022 ms 6.661 ms
3 pos1-0.rlghnck-rtr1.nc.rr.com (24.25.1.113) 8.956 ms 8.174 ms 7.995 ms
4 srp4-0.rlghnca-rtr2.nc.rr.com (24.25.2.146) 108.817 ms 113.090 ms 119.592 ms
5 pos14-0.rlghncrdc-rtr2.nc.rr.com (24.25.0.9) 201.288 ms 218.988 ms 1117.757 ms
6 son1-0-1.chrlncsa-rtr6.carolina.rr.com (24.93.64.81) 315.776 ms 315.707 ms
You can see that the trace host 3 is still less than 10 ms but then it jumps to 100+ to router #4. That would be bad as you wouldn't even be off their network and would be getting latency.
Be advised that the command to trace in windows is tracert and not "traceroute".
BTW, it's never their fault! Unless you have some kind of proof. Also, if you have solid proof, you need to speak to a manager and request that the info be sent to thier teir 2 support. You'll never get anywhere working with their first level engineers. You may need to skip tier 2 and go to teir 3 as well.
You may want to try this and post the results back here. We can help out if the issue is still happening.
Simply run adaware, spybot, ZoneAlarm, HijackThis, AVG, update windows daily, have a router, don't open e-mail, turn off action scripting, don't use P2P networks, don't violate EULAs, and wear a condom to get Windows secured.
