Downstream channels won't all lock
In the last month I've had the problem where downstream channels 2-10 (out of 16) won't lock. Nothing has changed in the inside wiring and I made sure everything was still connected tight. No storms or anything else to mess up the wire from the pole. I've noticed the locked channels are all around 381 MHz, while the channels that don't lock are around 800 MHz. The modem is a Motorola 7550. Re-setting/unplugging the modem doesn't help. I used the Customer Service chat and they re-set the modem and said it looked fine on their end. Any ideas why it would suddenly be doing this?92Views0likes3Comments
Getting "US profile assignment change" constantly causing random disconnects.
I'm not sure what else to do at this point. Sorry about long rambling post. Location: South San Diego Install setup: Straight drop from the pole to the property and a grounding block. From there, about 10ft run straight into the modem. No splitters. For the past couple of months (maybe longer), I had been losing my internet connection intermittently, it could last anywhere from 15 seconds to a minute or two. During the day, it's enough to kick me off my work's VPN, in the evening, it's enough to kick me out of any online gaming sessions. It appears to be worse in the evening. Over time, it's gotten worse and worse with the back and forth with Cox CS which proceeded to always blame my Modem (Netgear CM1100) AND somehow router (Asus RT-AC68U) because their "test signal" looks PERFECT. Which isn't the issue, Signals have looked good with minimal to no packet loss. It's the QUALITY of service that is the issue. I got fed up and bought a new modem (Arris S33) AND a new router (RT-AX86U Pro) because I did not want to give Cox an "excuse" and voila, what do you know, same problem. I changed out to a new RG6 cable to the grounding block, even bought a new 3ghz grounding block myself. NOTHING. Then, after spending several hundred dollars, did Cox finally agree to send a tech out. The tech dropped NEW line from the pole, redid the wiring etc etc, all new wires and he noticed that there was "noise" in the line. Ingress so he called it and while we were chatting, it went back to normal, perfect and he said would you look at that, all good. While I was explaining to him the numbers went back to showing a noise. He was plugged straight into the grounding block outside so could not have been my lines/property. So the tech placed a ticket to have looked at. Supposedly the ingress was coming from a house on our street, the following day Cox left a notice on my door that they located the issue and resolved it. Well guess what, I'm getting EVEN MOREUS profile assignment change in my logs, and intermittent drops of service. So I called and spoke to tier 2, who again, for whatever reason, scheduled another tech visit. The tech came and I told him that a tech had come prior and already changed all the lines. He did his tests and said that the signal everything looks good, no packet loss or anything, but he also got some error on the Up Stream and sent it to his manager. He told me they are going to monitor the line, however they do that and see what is going on. The problem just seems to be getting worse and worse. I've gone from a few profile changes a day to pretty much every 30 minutes to an hour. I'm at a loss. The real problem is my WORK. I cannot and should not have to worry about if my VPN is going to disconnect any minute now. It won't disconnect at every change of profile but will 3-4 times during work day and more so at night. So I'm reaching out here to see if anyone has experienced this and what the solution was? I don't even know why I'm bothering as they laid down fiber on our street recently and I have access to fiber service from another company but we have been with COX for almost 18 years so I want to give them a chance. Ideas? Downstream Bonded Channels Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables 21 Locked QAM256 855000000 Hz 5 dBmV 43 dB 0 0 5 Locked QAM256 759000000 Hz 6 dBmV 43 dB 0 0 13 Locked QAM256 807000000 Hz 5 dBmV 44 dB 0 0 18 Locked QAM256 837000000 Hz 5 dBmV 44 dB 0 0 19 Locked QAM256 843000000 Hz 5 dBmV 44 dB 0 0 20 Locked QAM256 849000000 Hz 5 dBmV 44 dB 0 0 22 Locked QAM256 861000000 Hz 4 dBmV 43 dB 0 0 23 Locked QAM256 867000000 Hz 4 dBmV 43 dB 0 0 24 Locked QAM256 873000000 Hz 4 dBmV 43 dB 0 0 25 Locked QAM256 117000000 Hz 0 dBmV 41 dB 0 0 26 Locked QAM256 123000000 Hz 0 dBmV 41 dB 0 0 27 Locked QAM256 129000000 Hz 0 dBmV 41 dB 0 0 28 Locked QAM256 135000000 Hz 0 dBmV 41 dB 0 0 29 Locked QAM256 141000000 Hz 0 dBmV 41 dB 0 0 30 Locked QAM256 147000000 Hz 0 dBmV 41 dB 0 0 31 Locked QAM256 153000000 Hz 0 dBmV 41 dB 0 0 32 Locked QAM256 159000000 Hz 0 dBmV 41 dB 0 0 33 Locked QAM256 165000000 Hz 0 dBmV 41 dB 0 0 34 Locked QAM256 171000000 Hz 0 dBmV 41 dB 0 0 35 Locked QAM256 177000000 Hz 0 dBmV 41 dB 0 0 36 Locked QAM256 183000000 Hz 0 dBmV 41 dB 0 0 37 Locked QAM256 189000000 Hz 0 dBmV 41 dB 0 0 38 Locked QAM256 195000000 Hz 0 dBmV 41 dB 0 0 39 Locked QAM256 201000000 Hz 0 dBmV 42 dB 0 0 40 Locked QAM256 207000000 Hz 1 dBmV 41 dB 0 0 41 Locked QAM256 213000000 Hz 1 dBmV 42 dB 0 0 42 Locked QAM256 219000000 Hz 1 dBmV 42 dB 0 0 43 Locked QAM256 225000000 Hz 0 dBmV 42 dB 0 0 44 Locked QAM256 231000000 Hz 0 dBmV 42 dB 0 0 46 Locked QAM256 243000000 Hz 0 dBmV 41 dB 0 0 47 Locked QAM256 249000000 Hz 0 dBmV 42 dB 0 0 48 Locked QAM256 255000000 Hz 1 dBmV 42 dB 0 0 159 Locked OFDM PLC 300000000 Hz 2 dBmV 43 dB 447192759 0 160 Locked OFDM PLC 918000000 Hz 6 dBmV 43 dB 72860026 0 Upstream Bonded Channels Channel ID Lock Status US Channel Type Frequency Width Power 1 Locked SC-QAM 17600000 Hz 6400000 36.8 dBmV 2 Locked SC-QAM 24000000 Hz 6400000 36.8 dBmV 3 Locked SC-QAM 30400000 Hz 6400000 36.8 dBmV 4 Locked SC-QAM 36800000 Hz 6400000 36.8 dBmV 6 Locked OFDMA 36800000 Hz 44000000 31.5 dBmV Here's a snippet from last night to this morning (now) of most recent event, I reboot router daily (in hopes it won't drop connection today) so logs get deleted but you get the idea, just same thing throughout. 22/8/2023 01:29:44 6 US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 01:30:21 6 US profile assignment change. US Chan ID: 8; Previous Profile: 12 13; New Profile: 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 02:26:03 6 US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 9 13.;CM-MAC=;CMTS-MAC;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 04:19:18 6 US profile assignment change. US Chan ID: 8; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=:b1;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 04:26:13 6 US profile assignment change. US Chan ID: 8; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 06:20:12 6 US profile assignment change. US Chan ID: 8; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 06:26:21 6 US profile assignment change. US Chan ID: 8; Previous Profile: 10 13; New Profile: 9 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 08:21:27 6 US profile assignment change. US Chan ID: 8; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 08:23:01 6 US profile assignment change. US Chan ID: 8; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 08:24:39 6 US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=;CMTS-MAC=c;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 08:26:36 6 US profile assignment change. US Chan ID: 8; Previous Profile: 12 13; New Profile: 9 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 08:29:26 6 US profile assignment change. US Chan ID: 8; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 08:30:04 6 US profile assignment change. US Chan ID: 8; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 08:31:57 6 US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 09:26:39 6 US profile assignment change. US Chan ID: 8; Previous Profile: 12 13; New Profile: 9 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 09:41:14 6 US profile assignment change. US Chan ID: 8; Previous Profile: 9 13; New Profile: 10 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 09:49:34 6 US profile assignment change. US Chan ID: 8; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=1;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 09:50:10 6 US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; 22/8/2023 09:52:55 6 US profile assignment change. US Chan ID: 8; Previous Profile: 12 13; New Profile: 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; 22/8/2023 10:26:48 6 US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 9 13.;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;3.8KViews1like21Comments
Only receiving 28Mbps and paying for gigablast. other neighbors report the same thing.
Can anyone explain why I only get a fraction of what I pay for? my last speed test was 16Mbps, and at best I get 28mbps. I pay for 1000Mbps, and I fully understand that one device will never actually get those speeds (several people are using the internet), but I am not even getting a twentieth of what I am paying for. I called the support line, and the guy wanted to restart my router and modem (of course), and then tried to have me get a tech to come look at it (for about 100$ of course). I vehemently declined that offer, I know my equipment is good, I paid for excellent brands, and both the modem and the router support +1000Mbps speeds. I told customer service they needed to have someone come check the main line in my neighborhood as my neighbor (and several others) all shared the same experience with me, we are getting hardly any internet. They supposedly created a ticket for a tech to come to inspect the box outside and gave me the ticket number, but I have not received any news on that front yet. @COX - please resolve our situation. -Sincerely, Paying CustomersSolved598Views0likes6Comments
On a Roku, how do I stream Cox channels I pay for
I have Cox digital and a Roku. I have managed to get some of the Discovery and History channels to stream on my Roku..Not live tv.. Yet other channels will not stream. Such as Boomerang cartoon channel, CBS live, ABC live, etc., that I pay for, through Cox. How do I get these channels to link to my Roku through my Cox account without having to pay additional fees for the channel? Is there a way to stream ALL Cox channels on the Roku? Is there a Cox Contour app for Roku? Thanks in advance for any, useful, help.30KViews0likes4CommentsOutage again
Outage again in the ending an intense gaming session. Everything earned is lost. Called and got the usual bs and automated hang up. Called again to cancel service and move to ATT. Was given $28 credit but I warned them that if it happens again this week I am gone. Would you stay with a power provider that blacked out your house once or twice a week?207Views0likes1Comment
Macon GA- 31204 Cox Internet outage Any info Timeline? ETA
Does anyone in the area of 31204 (or surrounding zip codes) Macon, GA have ZERO internet service due to an “outage”? My service has been off for over a week now and I get nowhere with the chat or the phone reps. They regurgitate a script (ad nauseam) and ask if there’s anything else they can assist me with. Yes, please cancel my service and let me go elsewhere that actually can get their act together long enough for me to receive the service I’m paying for. If you’re in the area, and your internet is down, please reply with any info or timeline that you may have heard.148Views0likes2Comments
T3 Timeouts - Followup
Posting here because I wanted to follow up on my post from a couple months ago - T3 Timeouts. Wanted to update the community on my experience and what I had to do to get the issue resolved. My issue was that I was seeing intermittent (but crippling) packet loss on a daily basis. Going through normal Cox support channels, I had at least 6 different techs comeout to work on the problem. Some couldn't see the problem (if the packet loss wasn't happening when they were testing, most techs would just leave and charge us a fee for the visit without doing anything) and some would just change lines without doing any testing and call the problem fixed. Eventually, a tech came out and saw the problem. He created an ESR ticket to deal with the issue and gave me the ticket number to keep tabs on the problem. That's where the previous post ended. About a week later, I checked in with Cox support about the ticket. The ticket had been closed and some work apparently had been done in my neighborhood, but I wasn't seeing any improvement. I had two more techs come out to the house, neither of whom were able to identify and fix the issue. I was very hopeful when the original ESR ticket was created, but after it was closed I was basically starting back at square one to get Cox to acknowledge and fix the problem. At this point, I decided it was time to file an informal complaint with the FCC. I was contacted by Cox in I believe less than 24 hours after I filed the informal complaint. I was connected with the executive escalations team, and a tech was out the next day. There were at least 5 more tech visits after this one, but at least now there was a ticket being kept open until the issue was fixed and I wasn't starting from scratch each visit. Eventually, I was given the plant supervisor's cell number to text whenever I was seeing the packet loss so he could send someone out to check the neighborhood for interference. I was seeing multiple bucket trucks in my area over the past week and a half - from my conversations with the techs, I was told that there were a lot of locations near me where they identified some interference/ingress and had fixed the problem. Unfortunately for me, these fixes still weren't resolving my packet loss issue (hopefully the nail salon down the street is enjoying a very stable connection now). Last Friday, the escalations team let me know that the issueshould finally be resolved. Despite that, the issue became so severe over the weekend thatmy modem would completely disconnect from the internet multiple times and all of my real time applications became essentially unusable. This morning, I texted the plant supervisor letting him know that my issue was getting worse. I think they may have already had some indication that there was an issue, because there was someone out checking the pole in front of my house in less than 5 minutes of the text. Shortly after, the plant supervisor responded saying they'd identified interference on some of the lines, and that the tech had resolved it. For the first time in several months, Iam seeing 0% packet lossconsistently and my jitteris finally looking stable. I am cautiously optimistic that my problem has been dealt with. Beyond getting extremely lucky, I don't know how this would've been fixed without filing an informal FCC complaint. Even with the help of the higher tier support, it was difficult to track down and fix the problem. It blows my mind a little that the problem seems to have been right out in front of my house at the pole and yet they were combing the entire neighborhood for the issue, but I realize tracking down ingress is sort of like finding a needle in a haystack. It was also illuminating to speak to the techs and hear about how pitiful the state of their infrastructure is at the moment. I live in the Gulf South, and there are apparentlyinnumerableproblems from hurricane damage that Cox has not been able to address for years. So to sum it up, there's no way I would've reached a resolution without filing an informal FCC complaint. At least in my area, there are tons of problems that the company is very sluggishly dealing with. Had I not made some noise, it could've been years before they fixed it (assuming they'd ever fix it at all). The plant supervisor basically said they've been seeing the intermittent packet loss for long time, but since no one was complaining about it, they weren't committing resources to fixing it. Hopefully,it's resolved for good and I can finally stop stressing about it.172Views2likes1CommentCox internet connection dropping consistently for the past few weeks
For the past few weeks since about mid July 2023, I've been getting dropped connections with my Cox internet (Gigablast 1000/35). I have a Motorola MB8611 Modem. I've read on Reddit that this modem has some bad firmware issues with other ISP's like Verizon XFinity, Comcast and Spectrum. my firmware on my MB8611 is: 8611-19.2.18 Here's my connection readout from the modem currently: Downstream Bonded Channels Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected 1 Locked QAM256 21 903.0 13.5 34.3 63568059 63686436 2 Locked QAM256 1 783.0 15.8 37.1 57006963 82479391 3 Locked QAM256 2 789.0 15.6 25.6 59484388 90351874 4 Locked QAM256 3 795.0 15.5 35.0 70007424 131215075 5 Locked QAM256 4 801.0 15.9 33.2 69447058 170415738 6 Locked QAM256 5 807.0 15.4 29.0 73268394 167643519 7 Locked QAM256 6 813.0 15.1 29.5 80697322 196236563 8 Locked QAM256 7 819.0 15.3 38.0 76475029 188987292 9 Locked QAM256 8 825.0 15.1 27.6 78697692 197739769 10 Locked QAM256 9 831.0 15.3 27.0 70124865 189206657 11 Locked QAM256 10 837.0 15.5 37.5 65046211 148840756 12 Locked QAM256 11 843.0 14.8 29.9 76168827 191516262 13 Locked QAM256 12 849.0 13.5 36.4 82982527 208408779 14 Locked QAM256 13 855.0 13.1 32.6 83170367 203446266 15 Locked QAM256 14 861.0 12.8 33.7 76194117 190829882 16 Locked QAM256 15 867.0 12.0 30.4 79906743 189468417 17 Locked QAM256 16 873.0 11.5 36.4 105763908 245848926 18 Locked QAM256 17 879.0 11.7 28.8 86142491 201576364 19 Locked QAM256 18 885.0 12.0 35.3 79977188 176029101 20 Locked QAM256 19 891.0 11.5 30.2 74702643 143132606 21 Locked QAM256 20 897.0 12.3 32.8 73843867 90912105 22 Locked QAM256 22 909.0 14.2 37.5 58848659 54601544 23 Locked QAM256 23 915.0 14.7 34.5 57210607 46515683 24 Locked QAM256 24 921.0 14.9 32.3 52228510 39945613 25 Locked QAM256 25 927.0 13.6 37.8 43542521 15595497 26 Locked QAM256 26 933.0 12.7 37.2 121873291 131103453 27 Locked QAM256 27 939.0 11.6 29.3 131240897 179339479 28 Locked QAM256 28 945.0 10.9 29.4 132665363 274532822 29 Locked QAM256 29 951.0 9.7 31.0 134482030 262734463 30 Locked QAM256 30 957.0 8.7 30.5 140847215 272847223 31 Locked QAM256 31 963.0 8.6 28.4 154937215 365349411 32 Locked QAM256 32 969.0 9.1 27.5 136145106 300353912 33 Locked OFDM PLC 159 300.0 15.9 35.1 -1831194459 46499114 Upstream Bonded Channels Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV) 1 Locked SC-QAM 1 5120 17.7 48.3 2 Locked SC-QAM 2 5120 24.1 48.3 3 Locked SC-QAM 3 5120 30.5 48.8 4 Locked SC-QAM 4 5120 36.9 48.8 5 Locked SC-QAM 6 2560 12.9 49.5 I know the SNR and Pwr downstream is high, and the uncorrectables are ridiculously high too. I checked with some other people about these readings. Event Log Time Priority Description 03:36:59 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:37:05 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:37:11 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:37:14 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 28 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:37:18 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:37:33 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:37:36 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:37:37 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:37:47 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:37:55 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:37:59 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:38:55 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:38:59 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:39:13 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:39:15 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 3 5 6 11 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:39:25 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:39:34 Fri Aug 18 2023 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:39:53 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:39:54 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM- 03:40:02 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:40:27 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:40:32 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:40:37 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:40:37 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:40:40 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1 03:40:48 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:40:58 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:41:01 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;C 03:41:09 Fri Aug 18 2023 Warning (5) MDD message timeout;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:41:10 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 14 15 17 18 19 20 28 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-VER=3.1; 03:41:11 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1;CM-V 03:41:18 Fri Aug 18 2023 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:92:6d:77;CMTS-MAC=00:87:31:90:bb:20;CM-QOS=1.1; These Type 1 and 4 Codes are constant throughout the day or night, even after rebooting the modem and checking that the coax connections are snug from the wall plate to the modem. Back in June I had a Arris S33 v2 that would constantly reboot all the time, but the signal strength and Hz's levels were good, checked it on cloudflare's Data checker for a speedtest and everything was great, no packet loss, very low jitter and was getting the overprovisioned 1200Mpbs downstream when I direct connected it to my 2.5Gbps Ethernet nic on my PC. I had to ditch that S33 Modem though because of constant rebooting it was doing. The questions I see alot is to check if a splitter is giving noise at the line coming into my home, but like I say just a month or more ago I wasn't having these problems. Are there any Cox's tech's here that can help me figure out if this a modem software issue or is this a Cox external issue from the pole to my home. It's really driving me crazy. Also is any of this due to the mid-split coming to Phoenix,AZ (where I live) I heard on dslreports.com that Cox is rolling out 100mpbs upstream to Gigablast customers. So yeah I have alot of questions and issues here, and I need some tech help to sort this out.1KViews0likes8CommentsNo internet for 5 days or the connection goes in and out
No one seems to be able to assist. I have tried through the web and the app with resets. I went and bought and picked up new things including their modem, talked to 10 different agents who use the same troubleshooting and telling me to do the same steps I’ve already done. Telling me everything looks fine on their end. What’s funny but not funny about that is, I then received a text from them separately saying there’s an outage in my area. Next was: Cox: Thanks for signing up to receive outage text updates. We're working on it, and expect you to be reconnected by 05:01AM. We'll continue to send updates as they're available. Next was: Cox: The outage in your area is resolved. We'll continue to closely monitor our network. Please let us know if your services are working. Reply "YES" if your service is up and running. Reply "NO" or "Unsure" if you're still having an issue. I say no. Then:We're sorry to see you're having trouble connecting. Please visit https://cox.com/smarthelp to troubleshoot the issue and get back up and running. Then:Cox: Your reset was unsuccessful. Try unplugging the power & plugging it back in. This can take up to 10 min. Then:Cox: It's been 3 days since the outage in your area was resolved, and we're checking to make sure your service is still running smoothly. Reply "YES" if you can connect without issues. Reply "NO" or "Unsure" if you’re still having trouble. I say NO again. Then: We're sorry to see you're having trouble connecting. Please visit https://cox.com/smarthelp to troubleshoot the issue and get back up and running. Now I’m highly annoyed because all these days have passed. I decide to txt AGENT for the 10th and final time. Same troubleshooting steps I already told them I’m tired of doing. Cox: Verify the Coax Cable is Connected into the Cable Port on the Box. Verify Coax Cable is connected to the wall outlet. Ensure all connections between the wall and the equipment are not loose or damaged. Me:I’ve reset, unplugged, plugged back, reset again, unscrewed cords, screwed them back in.It can’t be the modem, router, coax cords, Ethernet cords, power cords, nothing. I got all new stuff yesterday and a new modem from cox 3 days ago.My WiFi worked for 45 minutes today and then gone.I’ve troubleshoot everything, check cords, got a new modem, new router, etc.I’ve been without internet for 5 days.I’ve talked to ten agents.Then I was told there’s an outage in my area AFTER being told there wasn’t Then I’m told-Thank you so much for this confirmation, there are no outages reported in your area at this moment, in this case please allow me to reboot your device in order to clean up your line for any cache or excess of data and check the status of your modem, if the steps we follow don't fix the issue we will schedule a tech visit. 😑 did it, still nope. Next was:Thank you so much for following these steps with me today. I know how important it is for you to get everything working again, it seems like a tech visit needs to be done in order to sort this out for you, the visit would have a $75 potential charge (if the cause of the issue is Cox's responsibility charge won't be applied) I’m like at this point, y’all should’ve came out to the residents affected that are still having troubles because why would they lie 😑😑😑 Anybody else encounter this mess?1KViews1like6Comments
Downstream channels won't all lock
In the last month I've had the problem where downstream channels 2-10 (out of 16) won't lock. Nothing has changed in the inside wiring and I made sure everything was still connected tight. No storms or anything else to mess up the wire from the pole. I've noticed the locked channels are all around 381 MHz, while the channels that don't lock are around 800 MHz. The modem is a Motorola 7550. Re-setting/unplugging the modem doesn't help. I used the Customer Service chat and they re-set the modem and said it looked fine on their end. Any ideas why it would suddenly be doing this?No internet for 5 days or the connection goes in and out
No one seems to be able to assist. I have tried through the web and the app with resets. I went and bought and picked up new things including their modem, talked to 10 different agents who use the same troubleshooting and telling me to do the same steps I’ve already done. Telling me everything looks fine on their end. What’s funny but not funny about that is, I then received a text from them separately saying there’s an outage in my area. Next was: Cox: Thanks for signing up to receive outage text updates. We're working on it, and expect you to be reconnected by 05:01AM. We'll continue to send updates as they're available. Next was: Cox: The outage in your area is resolved. We'll continue to closely monitor our network. Please let us know if your services are working. Reply "YES" if your service is up and running. Reply "NO" or "Unsure" if you're still having an issue. I say no. Then:We're sorry to see you're having trouble connecting. Please visit https://cox.com/smarthelp to troubleshoot the issue and get back up and running. Then:Cox: Your reset was unsuccessful. Try unplugging the power & plugging it back in. This can take up to 10 min. Then:Cox: It's been 3 days since the outage in your area was resolved, and we're checking to make sure your service is still running smoothly. Reply "YES" if you can connect without issues. Reply "NO" or "Unsure" if you’re still having trouble. I say NO again. Then: We're sorry to see you're having trouble connecting. Please visit https://cox.com/smarthelp to troubleshoot the issue and get back up and running. Now I’m highly annoyed because all these days have passed. I decide to txt AGENT for the 10th and final time. Same troubleshooting steps I already told them I’m tired of doing. Cox: Verify the Coax Cable is Connected into the Cable Port on the Box. Verify Coax Cable is connected to the wall outlet. Ensure all connections between the wall and the equipment are not loose or damaged. Me:I’ve reset, unplugged, plugged back, reset again, unscrewed cords, screwed them back in.It can’t be the modem, router, coax cords, Ethernet cords, power cords, nothing. I got all new stuff yesterday and a new modem from cox 3 days ago.My WiFi worked for 45 minutes today and then gone.I’ve troubleshoot everything, check cords, got a new modem, new router, etc.I’ve been without internet for 5 days.I’ve talked to ten agents.Then I was told there’s an outage in my area AFTER being told there wasn’t Then I’m told-Thank you so much for this confirmation, there are no outages reported in your area at this moment, in this case please allow me to reboot your device in order to clean up your line for any cache or excess of data and check the status of your modem, if the steps we follow don't fix the issue we will schedule a tech visit. 😑 did it, still nope. Next was:Thank you so much for following these steps with me today. I know how important it is for you to get everything working again, it seems like a tech visit needs to be done in order to sort this out for you, the visit would have a $75 potential charge (if the cause of the issue is Cox's responsibility charge won't be applied) I’m like at this point, y’all should’ve came out to the residents affected that are still having troubles because why would they lie 😑😑😑 Anybody else encounter this mess?
