The last week my internet has been turtle slow. I have a Netgear R6300v2 router. On a normal day with no issues, my download speeds are around 95-101 mbps. My upload speeds on a good day are between 20-25mbps. This last week has really tried my patience, though.
Using speedtest.net, my current download speed is 3.65 mbps and my upload speed is 4.80 mbps. That's the highest I have seen it in days. In the last week, I have been lucky if my download speed goes above 2 mbps. In a first world perspective, I am dying. It's a struggle to stream Netflix and load webpages. For the money I am paying a month, I can't keep dealing with this.
My modem is the Technicolor TC8305C.
Downstream: http://i61.tinypic.com/10hrm09.jpg
Upstream: http://i57.tinypic.com/15ck484.
This is what I found in my modem's system log for today:
Sun Jul 13 14:32:28 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:30:02 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:26:55 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:23:26 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:21:26 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:21:13 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:20:35 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:18:47 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:18:27 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:11:17 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:10:42 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:07:43 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 14:07:39 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:59:28 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:58:14 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:58:06 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:58:05 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:54:58 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:52:35 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:51:43 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:48:47 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:48:23 2014 Warning (5) MDD message timeout;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:48:23 2014 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0; Sun Jul 13 13:48:15 2014 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:32:c8:e0:50:4b;CMTS-MAC=00:01:5c:3b:50:47;CM-QOS=1.1;CM-VER=3.0;
For the time frame, I just did today and there are four pages of those logs.
I downloaded ShaperProbe and these are the results:
Shaper Detection Module.
Connected to server 72.26.217.87.
Estimating capacity:
Upstream: 333 Kbps.
Downstream: 150272 Kbps.
The measurement will last for about 15.0 minutes.
Please wait.
Checking for traffic shapers:
Upstream: No shaper detected.
Median received rate: 336 Kbps.
Downstream: Measurement aborted due to high packet loss rate.
For more information, visit: http://www.cc.gatech.edu/~partha/diffprobe logout [Process completed]
Any help, comments, advice, anything would be appreciated.