ContributionsMost RecentMost LikesSolutionsIntermittent Internet after recent work by Cox in the neighborhood. Let me start this by saying that my at least two other neighbors in my neighborhood started seeing the same intermittent issues with Internet performance starting a day when Cox service technicians were in the neighborhood re-wiring and replacing equipment on at least one street corner near our home..... After two years of basically NO issues, we started seeing daily performance issues after Cox was in the neighborhood working on connections. I would reset the modem and performance would return for a bit, but I consistently would see significant numbers of uncorrectable errors on three downstream channels in my modem status pages. I contacted Cox and got a bit of a run-around from support since they could "see nothing wrong" but they did point out that my modem was an older DOCSIS 3.0 modem and I might consider upgrading. I passed on their offer and decided to go to Best Buy and get a new Netgear CM1200. It's a bit overkill but with 32 channels and 8 years newer tech, I figured it would help.... Well, I am seeing exactly the same three channels showing significant uncorrectable counts, MDD message timeouts and I did see some T3 timeouts as well earlier.... What can I tell the support people at Cox to get them to actually have someone dig into the recent work and even look at the screen captures I have from the modems showing these specific problematic channel/frequencies to see what common hardware/cabling there most likely is causing this? Here's a picture from the older modem: https://1drv.ms/u/s!AjViE9pQFMtwoieQsVyX0VtelESs And here's a picture (showing the same channels with issues after a relatively short time): https://1drv.ms/u/s!AjViE9pQFMtwoijZPxz_-ARnyfVH Thanks for any advice or suggestions... -- mike SolvedRe: Missing Downstream and Upstream channels -- performance hit and temporary loss of service I have had all 4 downstream and all 4 upstream channels since Saturday morning (1:42am). My modem has run clean (no new messages in the log) for more than 24 hours. Given that my wife was told by Cox that there was an outage in our area when she initially called about this on Thursday, I am going to 'assume' that this problem was related to that outage and I am going to mark this posting "answered" even though I really don't know what happened to clear this temporary problem. Additionally, thanks ChrisL for responding !! Your professional support is extremely appreciated Re: Missing Downstream and Upstream channels -- performance hit and temporary loss of service A service visit is still scheduled for Monday. In any case, are you able to see timing on those errors ? And when you say "upstream" I gather you mean from CM --> CMTS (my perspective) or is that from your end ? I have seen no record of timeouts (T3 or otherwise) and I have purposefully left the modem alone since the log on the modem continues to be clean with nothing in the log since 1:42am. I was thinking about power cycling one more time later this afternoon though since I'm not always comfortable when things "magically recover" on the remote end. Do you recommend that as reasonable or just better to wait for a service visit ? As an aside .... service here looks GREAT so far today from both a performance and reliability perspective so whatever was leading me to only have single channel connections and regular timeouts (this all starting abruptly on Thursday after months of VERY stable service) seems to have been corrected. I just wish I knew what might have fixed this ...... UPDATE: rebooted my modem at 12:50 CST just to get a clean start on this end too. Everything came back (4 upstream and 4 downstream channels with good levels) immediately and I'll check the logs here tonight. Re: Missing Downstream and Upstream channels -- performance hit and temporary loss of service Chris -- Thanks for checking ... It does look like things are good as of about 1:42am CST this morning after a reset due to T4 timeout and another due to MDD timeout. Here's what it looks like now Downstream Bonding Channel Value Channel ID 32 29 30 31 Frequency 813000000 Hz 795000000 Hz 801000000 Hz 807000000 Hz Signal to Noise Ratio 38 dB 38 dB 37 dB 38 dB Downstream Modulation QAM256 QAM256 QAM256 QAM256 Power Level The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading -2 dBmV 1 dBmV -1 dBmV 0 dBmV Upstream Bonding Channel Value Channel ID 1 2 3 4 Frequency 19900000 Hz 23700000 Hz 28700000 Hz 35300000 Hz Ranging Service ID 73 73 73 73 Symbol Rate 2.560 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec Power Level 44 dBmV 48 dBmV 49 dBmV 46 dBmV Upstream Modulation [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM Ranging Status Success Success Success Success Signal Stats (Codewords) Bonding Channel Value Channel ID 32 29 30 31 Total Unerrored Codewords 1391821283 1391821582 1391821408 1391821378 Total Correctable Codewords 10 0 0 17 Total Uncorrectable Codewords 1743 1378 1554 1647 Missing Downstream and Upstream channels -- performance hit and temporary loss of service After months of very reliable Internet service, we again are struggling with outages that started yesterday while I was out of town. I returned today to see that no matter what I do with the cable modem on my end (power cycle, reset to factory defaults, etc...) it only acquires a SINGLE downstream channel and a SINGLE upstream channel. Then, when I periodically receive DCC from COX (seen in the log of the cable modem), the DCC aborts/fails and I temporarily lose service. This has happened a few times this evening alone even while I was on the phone with Cox technical support. I placed a service call and, of course, the only thing they offer is to come out to the home and validate that the wiring isn't the problem. Of course, given the SIGNALS ARE FINE for the channel that I do have, this seems pretty ridiculous but it is what it is. I also requested they report this as an outage but they continued to say "I will pass that along to my supervisor" which is a nice way of saying "I'm scheduling a tech and that's it..." As an example, here is how my Upstream channels looked back in October (the last time I took a screen shot) and this pretty much what I would normally see when things have been working. Unfortunately, I don't have an old capture of the Downstream channel info .... GOOD: Upstream Bonding Channel Value Channel ID 2 3 4 Frequency 23700000 Hz 28700000 Hz 35300000 Hz Ranging Service ID 113 113 113 Symbol Rate 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec Power Level 45 dBmV 46 dBmV 43 dBmV Upstream Modulation [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM Ranging Status Success Success Success ... and here is what I have today ... any ideas what I can tell the phone support team to get them to help fix this this configuration error instead of just saying they will send a tech into my home ? I'm missing TWO Upstream Channels (I normally see three with this service) and (I think) THREE Downstream channels since there are normally four if I remember right.... Downstream Bonding Channel Value Channel ID 30 Frequency 801000000 Hz Signal to Noise Ratio 37 dB Downstream Modulation QAM256 Power Level The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading 0 dBmV Upstream Bonding Channel Value Channel ID 2 Frequency 23700000 Hz Ranging Service ID 7519 Symbol Rate 2.560 Msym/sec Power Level 48 dBmV Upstream Modulation [3] 16QAM [3] 64QAM Ranging Status Success SolvedRe: Constant Upload Problems in Rogers AR chanmiro ... I am taking your advice from the dslreports forum and posting here. Interestingly enough, just after I posted there this afternoon I saw the same two upstream frequencies were in "aborted" status on my modem and, sure enough, shortly thereafter (at 15:54 CDT) my modem rebooted due to T4 timeout. So I decided that was a good time to leave the home for a bit .. and what do you know, there was a Cox truck on the main street and the tech there had been dispatched for an "outage" ..... I did not get to talk with him much, but he seemed frustrated with what he indicated was some intermittent issue that he had on the scope in the car (he pointed to it but I was not sure what I was looking at). Honestly, I may not bee in the same area as you are in Rogers being here in Bentonville, but who knows ..... I just rebooted my modem to get a good clean signal so I could post here and this is what my upstream channels look like when things are good. Upstream Bonding Channel Value Channel ID 2 3 4 Frequency 23700000 Hz 28700000 Hz 35300000 Hz Ranging Service ID 113 113 113 Symbol Rate 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec Power Level 45 dBmV 46 dBmV 43 dBmV Upstream Modulation [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM Ranging Status Success Success Success When bad .. the power levels are about the same, but the modulation shifts to "[ 6 ] 16QAM" and the ranging status often ends up "Aborted" particularly for the 287 and 353 frequencies... As an aside .. this really started here in October after at least a year of no issues at all . and I too noticed this happens about every other day or so ... but sometimes daily. When daily, I notice it more between midnight and 6am. Today, however, was particularly bad with issues every few hours from about 6am on to 4pm. We'll see if the tech in the truck was able to find anything. Oh, I have a service call scheduled for Tuesday next week but considering how these problems only seem to come up every few years and they are always outside the home, I'm not hopeful that will be worth Cox (or my) time...... Update: 7pm and at least the 4th reboot due to T4 timeout today alone. There may have been more since I'm not always watching the log as it wraps. I guess I could call tech support again but instead I will wait for the tech to visit on Tuesday. It sure looks like whatever the Cox tech was working a pole or two over from my home was not fixed (or more likely, trouble not found) :(