Recent Discussions
COX Rated WORST - No surprise there.
Consumer Reports released the results of their survey of telecommunication services. No surprise that COX is in the WORST category no matter whether you look at the "Phne TV Internet Bundles", "Internet Providers", "TV Services" categories. In the "Value" category COX is always the lowest score, and in "Customer Service", the second lowest score possible. Where "reliability" was a rating factor, COX scored the median or "average" value. Same with "speed". Why can a company with record (and increasing) profits sustain such growth with mediocre to poor services? UNREGULATED GOVERNMENT GRANTED MONOPOLIES! As in CA where COX hip-pocket politicians in the state legislature approved a carve up of the state into monopoly zones for telecom services among COX, COMCAST and XFINITY. This allowed COX for the longest time to keep its hip-pocket county commisioners from issuing construction permits to Verizon (local landline phone provider) to update their copper line to fiber which caused Verizon to abandon their services in my area to Frontier, a Chinese company that, because of Chinese law, has to make all communications on its networks available to Chinese military and industrial "intelligence" services without any type of legal review or check and balance. Why the Chinese interest in this area? It is fairly dense with high-tech companies with leading edge tech in medical, aerospace, military and civilian telecom, power generation and distribution technologies, the very areas Chinese spying has been penetrating and stealing for decades. FINALLY (probably due to anti-American Trumpists in the telecom regulating agencies from Fed to state level) Frontier was able to break the COX stranglehold on the permitting process and has just started to upgrade the local copper network to fiber, and in limited neighborhoods, offer high-speed internet via fiber. COX current response in an advertising campaign specifically calling out Frontier on speed based on their historical DSL service in order to be sure no one notices that they are transitioning to Fiber. In addition COX falsely claims a 99%+ up-time/reliability that I have not experienced EVER in Cox internet service, and in their TV service since the early 2000's. To bleed as much money out of existing customers before they discover there may be a more reliable and cost-effective option, COX has increased its customer abuse tactics. For example, charging for streaming services that are only available with a DVR-enable Cox receiver, while they KNOW you are only provisioned with (and charged for) non-DVR capable receiver (and stating when, called on the fact that their Web site says YOUR receiver IS capable of receiving the streaming service - i.e. HBOMax - that you need to upgrade to the DVR capable box at an addition $10 - 15 per month in order to use the service you are being billed for!). Another example: Initially signed up for the lowest internet speed package (at the time 100 mbps) when Verizon disabled my DSL by wiring in a new office complex between my home office and the switch so that the wire run to my house put me outside the DSL capable distance for their copper network. Subsequently I got (and saved) emails from COX telling me how I was getting a "free speed upgrade" to my existing internet service. Of course, these never appeared - at least not according to Ookla Speed Test. What did appear over time was a doubling then tripling of the "Ping" time over my DSL service which I believe is COX's interception of internet/website requests for purposes of privacy violating profiling and corporate throttling "for fun and profit" from data miners and corporations that want "priority" access to COX users. Then to rub salt into thw wounds, COX eliminated the 100 and 150 Mbps tiers, automatically "upgraded" those users to 250 mbps with an overall 40%+ fee increase, BUT NEVER UPGRADED THE ACTUAL SPEED OF THE CONNECTION!!! When contacted, they tried to tell my wife (take advantage of an ignorant woman, they thought - except she shares the same software engineering creds as I have) that in order to get these new speeds we would have to upgrade our equipment to COX "panoramic" (mesh) WiFi, which is total BS especially for a home with one computer wired to the router, and one light-use tablet connected to the internet VERY SPORADICALLY throughout any given day. (No social media accounts, little to no looking at videos, mostly email, some shopping, and some info research for non-digital hobbies.) When challenged, the excuse became, "well your modem is too old - you need to upgrade it". I've been using my own Netgear DOCSIS 3.0 modem since the beginning with COX, and the only problem is their frequent outages that sometimes the own up to as "maintenance" and other times as "outage in your area" always with the same predicted fix time of 6:00 am the next day. Despite knowing this was total BS on COX's part, I went to their web site and found a modem they claimed was DOCSIS 3.1 and compatible with their service. I purchased the modem from BestBuy, but when following the modem manufacturer's instructions for COX activation via COX web site, it failed (waited on activation to complete for several hours and gave up). I then called COX tech support number listed for Internet service activation, provided the tech with the MAC etc. and while waiting for the activation which he could not do, he tried to set up a "service call" by a tech with a replacement modem since the one I had could not be activated (despite all status indicators being normal). I told him that the modem was purchased from BestBuy and then he told me "UNLESS THE MODEM IS SUPPLIED BY COX IT WILL NOT WORK WITH COX INTERNET SERVICE". So, once again COX web site falsely advertises available services for specific hardware models! AND THEY GET AWAY WITH IT BECAUSE THEY ARE AN UNREGULATED MONOPOLY TELECOM PROVIDER!! AND THE KNOWINGLY CONTINUE TO MAKE FALSE CLAIMS AND "SERVICE ADJUSTMENTS" SOLELY TO INCREASE PROFITS WITHOUT IMPROVEMENTS TO QUALITY, QUANTITY OF SERVICE OR "CUSTOMER CARE". That's why, when talking to anyone about my telecom services I say, "COX - say it out loud - that's what you have to deal with - a bunch of....!
3 Months of Multiple Daily Instances of Modem Self-Restarting
I am at a loss here. For the past 2-3 months, I've been having issues with my Panoramic Wifi modem issued by Cox, model CGM4331COM. At least 2-3 times per day, it will restart itself. This has been an everyday occurrence since the issue started. Starts off with losing internet connection to all devices, then the modem will blink yellow, then blink green, then back to solid white. It only takes about 5 minutes to come back online, but the constant daily interruption has become very irritating. Tonight it did something new, which prompted me to create this post; we lost connection and the light turned solid red until I unplugged the power and plugged it back in. We've had at least 5 techs come out to inspect outdoor lines, indoor lines, connection strength, ingress, the works. In the order in which steps have been taken to resolve the issue: A filter was installed on the outdoor connection. We had a pretty badly squirrel-chewed line that was replaced at the pole. There was an outdoor connection leading into our attic that was totally corroded that was replaced. The last tech that came mentioned that he removed a splitter in our attic so that we are directly wired from modem to pole now. In between all of this, we have been advised to replace the modem, and we did (twice). I have tried the online and telephone help options several times. A couple of times, it has restarted itself while I was on the phone or chat with the agent, and their only advice was to restart it? We have had the modem plugged into both a surge protector and directly into an outlet, and it still restarts itself periodically. We have tried plugging it into a different outlet with the same results. It has restarted itself whether it is physically connected to any devices via ethernet or not. All connections are tight and secure. I am not sure how to insert data into a table on here and make it legible, but I will occasionally look at the connection status screen under CM Error Codewords. Unerrored Codewords usually sit in the 50-100 million range. Correctable Codewords sit in the ~100k+ range. Uncorrectable Codewords will sit in the high 10-20k range. If need be, I can try to get better data from that section. Before this gets to be a novel, I'll leave it at this. I believe I have covered most of what has been attempted during the long troubleshooting process, but the last agent I spoke to on the phone happened to mention that none of the previous techs have been documenting their findings, so everyone that helps me at this point will just have to trust that we have tried seemingly everything with no results.
Cox 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.
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?
Cox install contractors
I've had cox Internet before about 4 years ago, recently had it reinstalled. The coax line from the outisde box ran to front of the house the the coax jack going into the house to hookup into the modem. Since then I've changed where my computer is located and where I put the modem. Now I want the coax jack to run to the back of my house to a back room. Do that I don't have to run coax through the attic. I have a brick home. The original instal had no masonry drill bit to go through brick. Rescheduled another contractor and had a note put on the ticket that I have a brick home. That contractor didn't bring a masonry bit. He goes to buy one then tells me two hardware stores didn't have them. Third contractor showed up. Not only did they NOT have a masonry bit. But they didn't have drill. Who goes to a job without a drill when your job will most likely have you using a drill. Cox has a serious problem with their contractors.
Internet outages wreaks havoc on VPN connections
This is a follow-up post as it seems my original post is locked for updates. I often loose my connection which only lasts for several minutes up to an hour or so. I am working from home using VPN and a couple minute outage will result in the VPN terminating. I opened a ticket with COX and they replaced my coax running from the house to the the tap outside and stated they also replaced a component in the tap. However, I still experience outages. I am posting my modem logs in hopes that someone can review and provide a recommendation as to the root of the problem? Thanks Status The statuses listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem. Top of Form Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked 256QAM 29 903.00 MHz -2.80 dBmV 37.36 dB 385069 1794108 2 Locked 256QAM 9 783.00 MHz -0.50 dBmV 37.64 dB 146898 44701 3 Locked 256QAM 10 789.00 MHz -0.90 dBmV 37.36 dB 147052 41571 4 Locked 256QAM 11 795.00 MHz -1.40 dBmV 37.36 dB 145868 39576 5 Locked 256QAM 12 801.00 MHz -2.60 dBmV 37.64 dB 146245 37172 6 Locked 256QAM 13 807.00 MHz -3.80 dBmV 37.36 dB 143888 29705 7 Locked 256QAM 14 813.00 MHz -3.70 dBmV 37.36 dB 140054 26351 8 Locked 256QAM 15 819.00 MHz -4.00 dBmV 37.36 dB 136900 24781 9 Locked 256QAM 16 825.00 MHz -4.70 dBmV 36.39 dB 133912 23104 10 Locked 256QAM 17 831.00 MHz -4.60 dBmV 36.61 dB 131146 21034 11 Locked 256QAM 18 837.00 MHz -3.80 dBmV 37.36 dB 124720 18624 12 Locked 256QAM 19 843.00 MHz -3.90 dBmV 37.64 dB 121785 16964 13 Locked 256QAM 20 849.00 MHz -4.70 dBmV 36.61 dB 118409 16159 14 Locked 256QAM 21 855.00 MHz -3.80 dBmV 37.36 dB 113816 15485 15 Locked 256QAM 22 861.00 MHz -3.60 dBmV 37.36 dB 111314 14057 16 Locked 256QAM 23 867.00 MHz -4.40 dBmV 36.61 dB 106349 13993 17 Locked 256QAM 24 873.00 MHz -4.60 dBmV 36.39 dB 112914 71318 18 Locked 256QAM 25 879.00 MHz -4.10 dBmV 36.61 dB 178590 342506 19 Locked 256QAM 26 885.00 MHz -4.00 dBmV 36.61 dB 516537 2095976 20 Locked 256QAM 27 891.00 MHz -4.30 dBmV 36.39 dB 126750 122243 21 Locked 256QAM 28 897.00 MHz -3.40 dBmV 37.64 dB 93058 18920 22 Locked 256QAM 30 909.00 MHz -3.20 dBmV 37.36 dB 590716 3136217 23 Locked 256QAM 31 915.00 MHz -2.60 dBmV 37.36 dB 1095897 5620291 24 Locked 256QAM 32 921.00 MHz -2.00 dBmV 38.61 dB 2889497 17273329 25 Locked 256QAM 33 927.00 MHz -2.30 dBmV 37.90 dB 108056 482915 26 Locked 256QAM 34 933.00 MHz -2.30 dBmV 37.60 dB 76276 25344 27 Locked 256QAM 35 939.00 MHz -1.90 dBmV 37.60 dB 73798 25054 28 Locked 256QAM 36 945.00 MHz -1.80 dBmV 37.90 dB 70185 19172 29 Locked 256QAM 37 951.00 MHz -2.10 dBmV 37.30 dB 68195 21809 30 Locked 256QAM 38 957.00 MHz -2.40 dBmV 36.40 dB 71177 23922 31 Locked 256QAM 39 963.00 MHz -1.50 dBmV 36.90 dB 63878 21093 32 Locked 256QAM 40 969.00 MHz -0.80 dBmV 36.90 dB 62724 19128 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 3 5120 kSym/s 30.30 MHz 37.25 dBmV 2 Locked ATDMA 4 5120 kSym/s 36.70 MHz 38.75 dBmV 3 Locked ATDMA 2 5120 kSym/s 23.90 MHz 35.75 dBmV 4 Locked ATDMA 1 5120 kSym/s 17.40 MHz 36.25 dBmV Event Log The table below contains the log of events that the SB6190 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur. Top of Form Time Priority Description Wed May 03 05:31:38 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:38:19 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:41:50 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:44:58 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:52:01 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:52:58 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:57:06 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 06:23:54 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 06:27:40 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 07:47:07 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 07:52:13 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 07:57:18 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:02:24 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:32:57 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:40:37 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:48:13 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:51:32 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 09:18:47 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 09:22:59 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 11:10:47 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Looking for a good modem
Hello, I am looking for a good modem for the Ultimate Plan. I thought I would get theARRIS / SurfboardSB6190but then saw something about the issue with the Puma 6 chipset. I wanted a modem that had 32x 8 channels but can't seem to find one that will work with the Ultimate Plan and not have a Puma 6 Chipset. Any modem recommendations? Is 32x8 channels better than 24x8 channels will it make that much of a difference? Please help me choose the right modem for the Ultimate Plan.
Technicolor CGM4981 and Orbi RB20 and satellites...
For the life of me I cannot figure out how to get into the Technicolor CGM4981 router to change the SSID and maybe put this thing into "Bridged" mode to allow me to use my Orbi mesh system. Either that or turn the 3 satellites into AP's. Anyone have the default login info for this router? Tried admin / admin with no luck and got locked out for a few more minutes. An SSID change to reflect my previous SSID would prevent me from having to change all of my connected devices wifi connections, and I have a ton. I would prefer to use the Orbi RB20 router and have the CGM4981 as a modem only. If not possible then at least allow me to hardwire my Orbi satellites and use those as "extenders". Any thoughts?
How to get Netgate gateway to act as home router
I am using a SBG580 wireless cable modem gateway to connect to the Cox network. I recently purchased a Netgear 2100 gateway and an Asus wifi 6 AP. I want to disable the gateway/router functions from the SBG6580 and have the Netgate 2100 do those functions. I should be able to accomplish this if I set the SBG6580 to act as a bridge device and Cox registers a MAC address for public IP assignment. I have setup the SBG6580 in the following way to do this: Changed "Primary Network Only Mode" from "routed" to "bridged". The docs say when it is set to bridged it "Disables the network address and port translation settings on the gateway." This is the only setting I have on the device to change routing/NATP functions on the WAN side. Disabled DHCP Disabled WiFi On the Netgate I set the WAN port to request DHCP addressing, and also I have set the MAC address to the HFC MAC address of the SBG6580, the same MAC address that Cox has registered to allow my device to operate on their network. When I boot up the devices, the Netgate doesn't get assigned an IP address. Additionally theSBG6580 still requests a public DHCP address and gets one assigned to it. Is this because when I first connected the device to the Cox network I gave them the HFC MAC, the SBG6580 boots up, Cox sees that MAC and assigns the IP? I have tried to release the DHCP lease, then reboot the Netgate to see if it will get assigned a DHCP address, but that does not work even though the SBG6580 does release the IP. I have tried to get the native MAC address of the Netgate registered so that it can request a public IP address. I have called and live chatted with customer service several times so far to tell them I have a new device on my network that I would like registered so that it can get assigned at public IP address, but they have not been of any help so far. When I ask to speak to the next tier of customer service, they attempt to upsell me to "preferred customer service" package at additional cost, or they try to upsell me Cox Panoramic WiFi gateways. Has anyone reading this ever successfully setup a home network that simply uses the cable modem as modem only with a router on their home network. This is not a crazy setup at all, but Cox seems to want to prevent this from happening so they can sell me equpiment I guess? How can I explain to customer service what I want to do because none of them seem to have any comprehension that a cable modem does not need to be the wireless gateway. Any help would be appreciated greatly!
