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?2.6KViews2likes8CommentsPacket loss due to upstream channels dropping
I've been getting outages due to the upstream dropping out on my internet connection for more than 6 months now. Downloads, watching streams, podcasts, hearing and seeing people on voice/video calls and are fine if they've already started. Uploads drop, voice/video calls break up for listeners, website requests take forever, games get disconnected. Modem upstream during packet loss: Bottom row with red question marks is packet loss. Other rows are just hops which sometimes don't respond (`mtr one.one.one.one`): I can't even get a screenshot without packet loss over the past few hours. I've rebooted my modem. I have a new cable and connectors from the box outside directly to my modem 2 times over. I've upgraded my modem 2 times and now have one of the best (MG8702) if not the best one supported by Cox. I've had several techs out to troubleshoot the issue. Some of them have replaced the same cable or connector as previous techs have done. One tech actually worked on something up the street, which improved the connection dropping a little. Another of the techs said there wasn't really anything they could do to fix it and that the lines are over-saturated because everyone is working from home now. If this is actually a problem, it sounds like a case to expand infrastructure rather than telling me it's all used up. I've confirmed with the techs that have visited that there's an issue with the upstream signals somewhere between the box at the utility pole and further up the chain. It doesn't seem like this issue will every be fixed. I've burned a lot of my time (days and days), burned money upgrading hardware that was fine, talking with customer support, and waiting for techs. I've been having to use my phone as a mobile hot-spot to ensure a consistent connection for voice and video calls. If this keeps up I think I'm just going to stop wasting money on useless internet and dump Cox and switch to a mobile hot-spot, since I end doing that anyway.Solved7.8KViews0likes31Comments
Keep getting connected to a terrible at capacity node. Please show that Cox is doing something before I file a FCC report.
For the past couple months, my internet in the downtown New Orleans area has been terrible. A full day outage every couple weeks and days of low speed/insane ping jitters. I'm working from home and have to remote in for work, and the internet has been so unreliable that I have to sometimes use my mobile data hotspot for work. Playing online videogames is impossible with insane ping jitters. I've called customer service but nothing got resolved. No, you cannot use the previous hurricane as an excuse. My internet was fine for couple months after the hurricane. You probably did some node rerouting and my area kept getting the bottom end of the stick. I'm posting my complain here so we have something in writing for the public to see and I'm hoping to get a resolution before I make a FCC report. What's the node capacity in my area? Does Cox have a plan to do a node split? Or I'm wrong and it's a different issue? Am I getting credit/discount for a subpar service? I've been recording ping data with PingPlotter, here's one for example: https://imgur.com/a/1SpLR5H Thanks for reading and I'm looking forward to hearing your response.2.2KViews0likes5Comments
Inconsistent Internet During Gaming
Hello. I'm constantly getting dropped from games and my internet feels unstable. Sometimes my internet drops all together. I'm done multiple equipment reboots and checked firmware on my router and modem. Modem is NETGEAR CM1000. I have this "SYNC Timing Synchronization failure" plus some other issues in my modem logs. Any thoughts? Thanks. Time Priority Description 2021-11-14, 17:39:09 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-14, 17:27:31 Notice (6) CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: z; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-14, 17:27:23 Warning (5) Unicast DSID PSN startup error 2021-11-14, 17:26:59 Warning (5) Dynamic Range Window violation 2021-11-14, 17:26:59 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-14, 17:26:59 Warning (5) Dynamic Range Window violation 2021-11-14, 17:26:59 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-14, 17:26:59 Warning (5) Dynamic Range Window violation 2021-11-14, 17:26:59 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-14, 17:26:55 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-14, 17:26:50 Notice (6) TLV-11 - unrecognized OID;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-14, 17:26:49 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2021-11-10, 18:05:15 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-10, 18:05:15 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-11-10, 18:02:27 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 22:56:31 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 22:55:59 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 22:55:47 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 22:55:37 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 22:55:35 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 22:53:27 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 22:53:20 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 05:13:11 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 05:12:42 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 05:12:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 05:12:15 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 05:12:14 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 05:10:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 05:10:06 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-09-07, 05:09:58 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-08-28, 23:08:15 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2021-08-21, 14:08:13 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-08-21, 12:05:06 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2021-08-21, 12:05:02 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-08-21, 12:04:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; 2021-08-21, 12:04:42 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:d2:94:ff:00:48;CMTS-MAC=00:27:90:0d:98:ee;CM-QOS=1.1;CM-VER=3.1; Frequency start Value This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. Starting Frequency 381000000 <tabindex=-1>Startup Procedure Procedure Status Comment Acquire Downstream Channel 903000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv4 only <tabindex=-1>Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 21 903000000 Hz -0.8 dBmV 40.6 dB 303388718 3 0 2 Locked QAM256 1 783000000 Hz -1.1 dBmV 40.8 dB 335350004 0 0 3 Locked QAM256 2 789000000 Hz -1.2 dBmV 40.8 dB 335353952 0 0 4 Locked QAM256 3 795000000 Hz -1.2 dBmV 40.7 dB 335357953 0 0 5 Locked QAM256 4 801000000 Hz -1.1 dBmV 40.7 dB 335360365 0 0 6 Locked QAM256 5 807000000 Hz -1.1 dBmV 40.9 dB 335364637 0 0 7 Locked QAM256 6 813000000 Hz -0.9 dBmV 40.8 dB 335368814 0 0 8 Locked QAM256 7 819000000 Hz -1.2 dBmV 40.7 dB 335372677 0 0 9 Locked QAM256 8 825000000 Hz -1.2 dBmV 40.7 dB 335376917 0 0 10 Locked QAM256 9 831000000 Hz -1.0 dBmV 40.9 dB 335381687 0 0 11 Locked QAM256 10 837000000 Hz -0.9 dBmV 40.7 dB 335385640 0 0 12 Locked QAM256 11 843000000 Hz -0.9 dBmV 40.7 dB 335388861 0 0 13 Locked QAM256 12 849000000 Hz -1.2 dBmV 40.6 dB 335392413 0 0 14 Locked QAM256 13 855000000 Hz -0.9 dBmV 40.7 dB 335396111 2 0 15 Locked QAM256 14 861000000 Hz -0.8 dBmV 40.7 dB 335400080 1 0 16 Locked QAM256 15 867000000 Hz -1.1 dBmV 40.4 dB 335403795 3 0 17 Locked QAM256 16 873000000 Hz -0.9 dBmV 40.6 dB 335408251 1 0 18 Locked QAM256 17 879000000 Hz -0.6 dBmV 40.6 dB 302609709 2 0 19 Locked QAM256 18 885000000 Hz -0.8 dBmV 40.5 dB 302616199 2 0 20 Locked QAM256 19 891000000 Hz -0.9 dBmV 40.4 dB 302624330 2 0 21 Locked QAM256 20 897000000 Hz -0.7 dBmV 40.5 dB 302631132 1 0 22 Locked QAM256 22 909000000 Hz -0.8 dBmV 40.6 dB 302638528 1 0 23 Locked QAM256 23 915000000 Hz -0.6 dBmV 40.5 dB 302646366 4 0 24 Locked QAM256 24 921000000 Hz -0.4 dBmV 40.6 dB 302653933 2 0 25 Locked QAM256 25 927000000 Hz -0.5 dBmV 40.5 dB 302661114 2 0 26 Locked QAM256 26 933000000 Hz -0.7 dBmV 40.6 dB 302668719 1 0 27 Locked QAM256 27 939000000 Hz -0.7 dBmV 40.6 dB 302676047 5 0 28 Locked QAM256 28 945000000 Hz -0.7 dBmV 40.6 dB 302683704 1 0 29 Locked QAM256 29 951000000 Hz -1.1 dBmV 40.4 dB 302691030 1 0 30 Locked QAM256 30 957000000 Hz -1.4 dBmV 40.3 dB 302696571 0 0 31 Locked QAM256 31 963000000 Hz -1.9 dBmV 40.2 dB 302697317 2 0 32 Locked QAM256 32 969000000 Hz -1.6 dBmV 40.5 dB 302698599 0 0582Views0likes0Comments
Cautionary tale before taking a free DOCSIS 3.1 modem upgrade
I work in IT and my client called because Cox sent them a new Arris CM8200 cable modem. I asked if they upgraded to a higher speed plan that would require it, but they hadn't made any changes to their services with Cox. It seemed odd, but since it was provided at no charge and the modem was essentially an updated version of their current SB6183 modem we went ahead and installed it.I explained the differences between DOCSIS 3.0 and 3.1 to my client and that 3.1 is more efficient with how it uses the available spectrum on the cable lines. (QAM256 vs. QAM 4096) Now the bad part.... After upgrading, they started to notice problems with call quality on their VoIP phones. I wasn't made aware of it initially as they contacted the VoIP vendor for help. After being made aware, I ran some ping tests to see if there was any obvious problems. Sure enough, pinging the gateway on the Cox side along with Google and Cloudflare DNS showed packet loss. We contacted tech support to see what could be done about it. We were informed that the node we were using was noisy, overloaded and experiencing capacity problems. Since speed was not a factor and reliability was more important we decided we should try to switch back to the old cable modem. With the problematic and noisy node we were on, running the older, but less efficient QAM256 modemmight help alleviate their problems. After all, they hadn't experienced any problems before installing the newer modem. Also, the previous SB6183 is still a modem on the Cox business compatibility list. Cox Business Certified Gateways and Modems | Cox Business So we called tech support to swap the old modem back, but we were informed that wasn't possible. I was told upgrading to DOCSIS 3.1 was a one way street and we could not reinstall our old modem. Installing the DOCSIS 3.1 modem offered little benefit to my client, but benefited Cox by helping them avoid a costly node split. So now they are stuck with poor quality internet and have no other option other than to repeatedly call tech support and complain. After more than a dozen phone calls with no resolution I was referred to the customer retention department. This is an unacceptable situation to put a business in. So beware that Cox may send your a new modem, but make sure that you will benefit from it before installing. There is no going back once you've upgraded, even if it results in a connection of worse quality.2.9KViews0likes3Comments
coxwifi hotspot
i work in a 11 floor glass building and i always have access to cox wifi hotspot especially since there's no data or reception in the building. for about a few months now when i try to connect it always says no internet connection. How can this be fixed? i'm located at 10001 lake forest blvd in new orleans, la1.8KViews0likes9Comments
Intermittent disconnects with new service, slow speeds overall - SB8200 in Omaha area
I started service 2 weeks ago when we moved into my new house in an Omaha suburb. Previous owner had Cox (looked like a business modem, but was ~12 years old). I'm paying for 500Mb package but we rarely get that. I activated service over the phone and installed my own Arris SB8200 (bought just for Docsis 3.1 for this new package, my old modem was Docsis 3.0) directly on the main line, after removing all the splitters inside because I don't use cable TV. It activated fine, the tech I spoke to on the phone didn't see issues and a quick speed test showed speeds close enough to 500, so I connected a router I bought a year ago (Netgear Nighthawk AC2300) and updated the SSID/password and started connecting my devices to wifi. Over the next few days, we had intermittent disconnects but didn't notice them much because we were moving furniture and setting things up in the new house. When I started working from home with my laptop, I noticed severe disconnects during Zoom calls but streaming video on TV was fine (later found out it was buffering far enough ahead to continue through the outage, most of them last 3 minutes or less). Fast forward to this week, we're getting ~8 disconnects per day ranging from 2-7 minutes long, some as often as 15 minutes apart. I see 32 channels on my modem status page, plus channel 159. Channel 159 has millions of correctable errors (which I understand is not a problem) but Channel 22 has hundreds of thousands of uncorrectables per day. I'm also seeing DRW errors in my modem's log and sometimes sync errors, some of them coincide with the outages but sometimes do not. Speed tests via the router firmware have also dropped a great deal, yesterday as I investigated, speedtest.net showed download speed of 150Mbps, far lower than the 400+ I was seeing at activation time. Ping and jitter consistently test much lower than my previous service in another city, but the inconsistency caused by these disconnections has made the overall performance much worse. I have called Cox about this twice and text-messaged Support, but they throw their hands up and say it has to be my equipment because "everythinghas green checkmarksexcept OFBM status" and when I ask to be escalated to someone who can look at my logs or status with me, they try to sell me Complete Care or convince me to pay to send a tech out (who will likely throw hands in the air too and want me to pay for something that's not my fault). What else can I do? Is there a secret to getting help and resolution from Cox? I mayhave just gotten bad level 1 agents but I'm not getting the service I'm paying for. Startup Procedure Procedure Status Comment Acquire Downstream Channel 783000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables 1 Locked QAM256 783000000 Hz 8.6 dBmV 39.9 dB 0 0 2 Locked QAM256 789000000 Hz 8.3 dBmV 39.7 dB 0 0 3 Locked QAM256 795000000 Hz 8.0 dBmV 39.6 dB 0 0 4 Locked QAM256 801000000 Hz 7.7 dBmV 39.5 dB 0 0 9 Locked QAM256 831000000 Hz 6.9 dBmV 39.1 dB 0 0 10 Locked QAM256 837000000 Hz 6.7 dBmV 39.4 dB 0 0 11 Locked QAM256 843000000 Hz 6.7 dBmV 39.4 dB 0 0 12 Locked QAM256 849000000 Hz 6.6 dBmV 39.5 dB 0 0 17 Locked QAM256 879000000 Hz 4.9 dBmV 38.8 dB 0 0 18 Locked QAM256 885000000 Hz 4.5 dBmV 38.5 dB 0 0 19 Locked QAM256 891000000 Hz 4.1 dBmV 38.4 dB 0 0 20 Locked QAM256 897000000 Hz 3.9 dBmV 38.5 dB 0 0 21 Locked QAM256 903000000 Hz 3.7 dBmV 38.4 dB 0 0 22 Locked QAM256 909000000 Hz 3.7 dBmV 38.3 dB 181986 458023 25 Locked QAM256 927000000 Hz 2.9 dBmV 37.8 dB 0 0 26 Locked QAM256 933000000 Hz 2.2 dBmV 37.4 dB 2 0 27 Locked QAM256 939000000 Hz 1.6 dBmV 37.0 dB 0 0 28 Locked QAM256 945000000 Hz 1.0 dBmV 36.7 dB 1 0 29 Locked QAM256 951000000 Hz 0.6 dBmV 36.7 dB 0 0 30 Locked QAM256 957000000 Hz 0.1 dBmV 36.5 dB 1 0 33 Locked QAM256 357000000 Hz 10.2 dBmV 41.6 dB 0 0 34 Locked QAM256 363000000 Hz 10.2 dBmV 42.1 dB 0 0 35 Locked QAM256 369000000 Hz 10.1 dBmV 42.0 dB 0 0 36 Locked QAM256 375000000 Hz 10.1 dBmV 42.1 dB 0 0 37 Locked QAM256 381000000 Hz 10.2 dBmV 42.0 dB 0 0 38 Locked QAM256 387000000 Hz 10.1 dBmV 42.0 dB 0 0 41 Locked QAM256 405000000 Hz 10.7 dBmV 42.0 dB 0 0 42 Locked QAM256 411000000 Hz 10.7 dBmV 42.1 dB 0 0 43 Locked QAM256 417000000 Hz 10.7 dBmV 41.3 dB 0 0 44 Locked QAM256 423000000 Hz 11.0 dBmV 42.3 dB 0 0 45 Locked QAM256 429000000 Hz 11.1 dBmV 42.2 dB 0 0 46 Locked QAM256 435000000 Hz 11.1 dBmV 42.1 dB 0 0 159 Locked Other 300000000 Hz 13.2 dBmV 42.5 dB 435672684 0 Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 4 Locked SC-QAM Upstream 36700000 Hz 6400000 Hz 39.0 dBmV 2 1 Locked SC-QAM Upstream 17400000 Hz 6400000 Hz 38.0 dBmV 3 2 Locked SC-QAM Upstream 23900000 Hz 6400000 Hz 38.0 dBmV 4 3 Locked SC-QAM Upstream 30300000 Hz 6400000 Hz 40.0 dBmV 5 6 Locked SC-QAM Upstream 12600000 Hz 3200000 Hz 37.0 dBmV Error log: Date Time Event ID Event Level Description 08/14/2020 14:57 2436694061 5 "Dynamic Range Window violation" 08/14/2020 14:57 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 14:22 2436694061 5 "Dynamic Range Window violation" 08/14/2020 14:22 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 13:04 2436694061 5 "Dynamic Range Window violation" 08/14/2020 13:04 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 12:54 2436694061 5 "Dynamic Range Window violation" 08/14/2020 12:54 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 11:47 2436694061 5 "Dynamic Range Window violation" 08/14/2020 11:47 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 11:31 2436694061 5 "Dynamic Range Window violation" 08/14/2020 11:31 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 11:24 2436694061 5 "Dynamic Range Window violation" 08/14/2020 11:24 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 11:09 2436694061 5 "Dynamic Range Window violation" 08/14/2020 11:09 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 11:02 2436694061 5 "Dynamic Range Window violation" 08/14/2020 11:02 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 10:01 2436694061 5 "Dynamic Range Window violation" 08/14/2020 10:01 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 09:42 2436694061 5 "Dynamic Range Window violation" 08/14/2020 09:42 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 07:41 2436694061 5 "Dynamic Range Window violation" 08/14/2020 07:41 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 07:28 2436694061 5 "Dynamic Range Window violation" 08/14/2020 07:28 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 07:04 2436694061 5 "Dynamic Range Window violation" 08/14/2020 07:04 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 06:28 2436694061 5 "Dynamic Range Window violation" 08/14/2020 06:28 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 06:09 2436694061 5 "Dynamic Range Window violation" 08/14/2020 06:09 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 05:08 2436694061 5 "Dynamic Range Window violation" 08/14/2020 05:08 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 04:49 2436694061 5 "Dynamic Range Window violation" 08/14/2020 04:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 04:03 2436694061 5 "Dynamic Range Window violation" 08/14/2020 04:03 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 03:19 2436694061 5 "Dynamic Range Window violation" 08/14/2020 03:19 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 03:19 2436694061 5 "Dynamic Range Window violation" 08/14/2020 03:19 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/14/2020 02:56 2436694061 5 "Dynamic Range Window violation" 08/14/2020 02:56 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/13/2020 21:25 2436694061 5 "Dynamic Range Window violation" 08/13/2020 21:25 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/13/2020 21:13 2436694061 5 "Dynamic Range Window violation" 08/13/2020 21:13 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/13/2020 20:11 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;" 08/13/2020 20:00 74010100 6 "CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: ;; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=ec:a9:40:8e:62:c5;CMTS-MAC=84:8a:8d:32:29:5d;CM-QOS=1.1;CM-VER=3.1;"Solved1.9KViews0likes5CommentsLag Spikes & Packet Loss
Over the course of the past month I have experienced worse and worse lag spikes & packet loss most noticeably while playing games on my Xbox. They have gotten really bad where almost every single match I play online I experience rubber banding and packet burst/loss. I have tried port forwarding and that has not fixed the issue, can someone please look into this and help?? Every time I check the network settings on the Xbox it shows that I have a solid connection with 0% packet loss but every time I play online I experience the same problems! Not only that, but it seems like my internet gets throttled at times while browsing the web or streaming / downloading content on my computers! This is unacceptable and if this can't get fixed I will have to cancel my service with Cox. I am paying for 300mb and that should be more than enough for a single user like me to have uninterrupted service!4.5KViews0likes7Comments
Keep getting connected to a terrible at capacity node. Please show that Cox is doing something before I file a FCC report.
For the past couple months, my internet in the downtown New Orleans area has been terrible. A full day outage every couple weeks and days of low speed/insane ping jitters. I'm working from home and have to remote in for work, and the internet has been so unreliable that I have to sometimes use my mobile data hotspot for work. Playing online videogames is impossible with insane ping jitters. I've called customer service but nothing got resolved. No, you cannot use the previous hurricane as an excuse. My internet was fine for couple months after the hurricane. You probably did some node rerouting and my area kept getting the bottom end of the stick. I'm posting my complain here so we have something in writing for the public to see and I'm hoping to get a resolution before I make a FCC report. What's the node capacity in my area? Does Cox have a plan to do a node split? Or I'm wrong and it's a different issue? Am I getting credit/discount for a subpar service? I've been recording ping data with PingPlotter, here's one for example: https://imgur.com/a/1SpLR5H Thanks for reading and I'm looking forward to hearing your response.
