This has been an ongoing problem for over 2 years since I moved into this house. Download speeds remain constant while upload speeds crash multiple times per day, down from 30 Mbps to less than 1 Mbps. I've had multiple techs in the home with no resolution, it gets elevated to plant/line technicians who clean up interference in the upstream and the problem goes away for a few weeks/months and then it comes back as always.
I've eliminated just about every variable I can think of in my home. It was built in Oct 2014, so barely 2 years old. Never had TV installed, only internet, so no splitters and the drop line from the street to the home is relatively new. PC is wired through the router, but wiring directly into the modem doesn't change anything. Using cat6 ethernet cables, a Netgear CM600 modem and R7000 router. Problem was identical when I used a SB6190 modem as well.
With me being home more the last week around holidays I've been able to monitor my connection very closely. I can be gaming online and notice the second the issue happens that causes my upload speeds to crash. I can predict within a few minutes when some error messages will appear in the modem logs. I've been getting an increasing amount of T3 and T4 errors, and considering my previous history in combination with the errors, the only logical explanation is interference/noise in the upstream channels.
When visiting family I can check their modem logs and only see a handful of errors for months at a time.... I've been getting 10-15 a day. Today has been a bad one with nearly my entire log page filled with errors only from today. Here's a snapshot of what my modem levels and logs look like:
Downstream Bonded Channels |
Channel |
Lock Status |
Modulation |
Channel ID |
Frequency |
Power |
SNR |
Correctables |
Uncorrectables |
1 |
Locked |
QAM256 |
53 |
837000000 Hz |
-1.5 dBmV |
39.4 dB |
2481 |
356 |
2 |
Locked |
QAM256 |
49 |
813000000 Hz |
-1.5 dBmV |
39.2 dB |
297 |
0 |
3 |
Locked |
QAM256 |
50 |
819000000 Hz |
-1.3 dBmV |
39.1 dB |
369 |
0 |
4 |
Locked |
QAM256 |
51 |
825000000 Hz |
-1.3 dBmV |
39.3 dB |
367 |
0 |
5 |
Locked |
QAM256 |
52 |
831000000 Hz |
-1.4 dBmV |
39.3 dB |
383 |
0 |
6 |
Locked |
QAM256 |
54 |
843000000 Hz |
-2.1 dBmV |
39.2 dB |
649 |
0 |
7 |
Locked |
QAM256 |
55 |
849000000 Hz |
-2.6 dBmV |
39.2 dB |
1027 |
527 |
8 |
Locked |
QAM256 |
56 |
855000000 Hz |
-2.9 dBmV |
38.4 dB |
4700 |
3246 |
9 |
Locked |
QAM256 |
57 |
861000000 Hz |
-3.1 dBmV |
38.7 dB |
14919 |
14612 |
10 |
Locked |
QAM256 |
58 |
867000000 Hz |
-3.4 dBmV |
38.6 dB |
20655 |
12687 |
11 |
Locked |
QAM256 |
59 |
873000000 Hz |
-3.2 dBmV |
38.5 dB |
5384 |
4136 |
12 |
Locked |
QAM256 |
60 |
879000000 Hz |
-3.3 dBmV |
38.2 dB |
20054 |
27968 |
13 |
Locked |
QAM256 |
61 |
885000000 Hz |
-3.2 dBmV |
38.2 dB |
33081 |
11519 |
14 |
Locked |
QAM256 |
62 |
891000000 Hz |
-3.5 dBmV |
38.0 dB |
1973 |
0 |
15 |
Locked |
QAM256 |
63 |
897000000 Hz |
-3.4 dBmV |
38.1 dB |
3264 |
2634 |
16 |
Locked |
QAM256 |
64 |
903000000 Hz |
-3.4 dBmV |
37.9 dB |
1501 |
460 |
17 |
Locked |
QAM256 |
65 |
909000000 Hz |
-3.2 dBmV |
38.3 dB |
0 |
0 |
18 |
Locked |
QAM256 |
66 |
915000000 Hz |
-2.6 dBmV |
38.6 dB |
0 |
0 |
19 |
Locked |
QAM256 |
67 |
921000000 Hz |
-2.2 dBmV |
38.6 dB |
0 |
0 |
20 |
Locked |
QAM256 |
68 |
927000000 Hz |
-1.7 dBmV |
38.5 dB |
0 |
0 |
21 |
Locked |
QAM256 |
69 |
933000000 Hz |
-1.4 dBmV |
38.6 dB |
0 |
0 |
22 |
Locked |
QAM256 |
70 |
939000000 Hz |
-1.0 dBmV |
39.0 dB |
0 |
0 |
23 |
Locked |
QAM256 |
71 |
945000000 Hz |
-1.5 dBmV |
38.6 dB |
0 |
0 |
24 |
Locked |
QAM256 |
72 |
951000000 Hz |
-1.9 dBmV |
38.3 dB |
0 |
0 |
|
|
Upstream Bonded Channels |
Channel |
Lock Status |
US Channel Type |
Channel ID |
Symbol Rate |
Frequency |
Power |
1 |
Locked |
ATDMA |
3 |
5120 Ksym/sec |
28202000 Hz |
41.3 dBmV |
2 |
Locked |
TDMA and ATDMA |
1 |
2560 Ksym/sec |
20202000 Hz |
40.3 dBmV |
3 |
Locked |
TDMA and ATDMA |
2 |
2560 Ksym/sec |
23402000 Hz |
41.3 dBmV |
4 |
Locked |
ATDMA |
4 |
5120 Ksym/sec |
35102000 Hz |
42.8 dBmV |
|
|
|
Time |
Priority |
Description |
2016-12-28, 16:06:36 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 16:06:32 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 16:06:30 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 16:06:29 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 16:06:28 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 16:06:21 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 16:06:18 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 16:03:42 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 15:40:23 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 15:40:22 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 15:40:21 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 15:40:19 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 15:40:11 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 15:40:06 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 15:39:48 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:16:42 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:16:37 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:16:36 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:16:35 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:16:34 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:16:31 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:15:47 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:15:40 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:15:39 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:15:38 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:56 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:53 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:51 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:30 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:26 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:18 |
Warning (5) |
MDD message timeout;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:13 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:12 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:10 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:14:08 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 12:13:58 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 10:45:46 |
Error (4) |
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-28, 06:08:27 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
2016-12-27, 22:45:49 |
Notice (6) |
TLV-11 - unrecognized OID;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established |
Warning (5) |
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=2c:30:33:87:b7:80;CMTS-MAC=e4:d3:f1:80:93:8a;CM-QOS=1.0;CM-VER=3.0; |
|
Notice how the correctable/uncorrectable errors build up to a certain frequency and then just stop altogether? I'd bet money that whatever interference is causing the upstream problems is also causing those problems. Whenever I notice the problems starting to occur, I can go do a speed test at Cox, testmy.net, dslreports, speedtest.net... it doesn't matter. I will get 300 Mbps down and less than 1 Mbps up. My most recent test at Cox is 317 down and .79 up. This will happen only a few times a week and then accelerate, right now it probably happens 3-4 times a day and lasts 30 minutes to an hour each time.
I'm tired of calling support on the phone, them telling me the modem levels look appropriate, resetting the modem remotely and then saying it should be fixed. I'm not an idiot, I know when it's working and when it's not. I also know that power cycling the modem doesn't work, it won't fix the cause of the problem when is interference somewhere on the line before it gets to my house.
I know this has been resolved at least 3 times in the past by a plant technician, George. He usually emails me when he's done to let me know what he did and to ask me if the problem has subsided. I don't know if he creates a work number each time he works on it or not if an employee here is looking up my account. I'm getting to the end of my patience though with how this keeps getting a band aid and never permanently resolved. I'm also tired of having go through the whole song and dance of calling phone support, having a tech in the home tell me exactly what I already know and having to take a day off work before it is finally referred to someone who can actually address the problem. Then it's a whole other issue if they actually resolve the problem.... clearly they haven't found a fix yet but instead keep employing temporary measures.
The reason I post all this is I'm hoping someone at Cox can help me skip the procedure of checking levels in home that I have to take off work for them to say they can't find anything wrong. The last 3 guys haven't found anything wrong and only one of them even had the decency to refer it to a line technician, the other 2 just said it looked good and that they fixed it (they did nothing). The errors in the modem log and all the pattern of correctable/uncorrectable errors in the downstream make it pretty obvious what's going on and that nothing can be done in the house to fix it. I'm spent a lot of time and money on my end to find a resolution to this, I just wish Cox would make the same effort. Otherwise, what's the point of paying for the Ultimate tier connection when i'm getting the connectivity of the most basic tier.