Incompetence at the highest level
For almost 2 weeks now, I have been unable to properly use my internet services. I pay for the Ultimate Bundle, mainly for heavy gaming and streaming. Recently, I have been experiencing major packet loss, choke and request time outs with my connection. When I originally called, the person over the phone told me my modem was the problem; I had an arris SB6190. He recommended I buy a netgear cm1000, which indeed I did. A few days later, the modem arrived and the problem wasn't resolved. A ticket was created for me and a technician came out on 10 / 23 (Monday). He couldn't figure out the problem, so he referred my case to maintenance. I have called almost every day since 10 / 23 (Monday) to make sure my ticket was moving in the right direction, and EVERY SINGLE PERSON told me the maintenance team is going to work on it, and that they need 3-5 days to fix this issue. I called yesterday 10 / 26 (Thursday) to ask for a status, and I was told that a supervisor would call me back within a few hours to inform me of what is going on. I never received a call back. I call again today 10 / 27 (Friday), in which the tier 2 technician tells me a maintenance ticket was never properly put in. WHAT?!?!?! Before I elaborate, let me just tell you everything I have tried. 1) New modem - 2) Bypassed router and went direct to modem - 3) bought new Ethernet cable [cat6] - 4) tried using WiFi instead - 5) tried using multiple computers, all have the same issue - 6) had tech come out to test the lines, which tested fine - 7) called tier 2 numerous times, in which they have confirmed they do see packet loss on my connection **Also a side note. I have worked in I.T. for 10+ years, and I am not computer/networking illiterate.** Back to the status, they now tell me a tech has to come back out to look at the problem once more, and if he can't resolve it (which I am confident he 100% will not), he will refer back to the maintenance team. This is absolutely ridiculous and incompetence at the highest level. How is it possible that over 5+ people within the past week have all told me a maintenance ticket was properly created into the system, and the last day I expect it to be resolved, I get word that they cannot even see a maintenance ticket on my account. After I requested to speak to a supervisor this morning (15 minutes ago), I told him he needs to go back and review all my calls (I hope they are recorded). It is nearly impossible for everyone to magically see that maintenance ticket, but then suddenly it disappears? I even talked to the CAG Line yesterday, in which they also confirmed a maintenance ticket. I am about to ready to completely cancel my service with COX, because this is the most unprofessional and incompetent practice I have seen since Comcast.4.8KViews0likes14Comments
Intermittent Daily Packet Loss and Connection Drops - 92673
Hello, I'm in Southern California, ZIP CODE 92673 and have been getting intermittent packet loss and connection drops on a daily basis. It usually happens in the late morning or early afternoon when I'm working from home and is proving to be very disruptive as I'm on wi-fi calling and the calls often drop during the middle of a conversation or I lose my Skype session. I suspect that node saturation might be a factor, but need someone to take a look. I have used continuous pings to isolate the issue and feel that the problem is occurring beyond my equipment. I'm hardwired from my laptop to my router which is connected directly to Cox's Cisco DPQ3212 DOCSIS 3.0 2-PORT Voice Modem. Attached are pictures of the power levels on the modem pings to different hops when everything is working fine. I'm now working to capturing examples of when the packet loss occurs so you can see where things are failing. Since I'm using PingPlotter Free, I only have 10 minutes of history, so I will attempt to catch this problem soon. So right now I have continuous pings to my router (192.168.1.1) the internal IP of the cable modem: (192.168.1.1), My External Public IP and the first private 10.X address that is a hop away from the cable modem. I assume this IP is on the node? TTL for the 10.X address is 254. While I wait to catch this packet loss, can you take a look at the attached power levels to see if my modem has adequate power levels and Signal to Noise Ratio's? Also, not sure if it helps, but when the packet loss/drops occur, the power levels on the downstream spike by at least +1 dBmV. BTW, I replaced the Cisco cable modem a few weeks ago and nothing has improved. Phil3.5KViews0likes6CommentsMultiple connection timeouts happening every few minutes
I have been having multiple connection timeouts while using my service, usually happening every 5 minutes. I can't enjoy my online gaming for more than that time without being disconnected from the servers. I have tried everything from unplugging the modem for a few minutes then plugging it back in, having the modem's power go directly into the power outlet, replacing the rental modem that I was using with a newer and faster one, being directly hardwired into the modem and not using the router, changing DNS servers, and flushing the DNS. Cox even sent a "technician", though he was only contracted, to my home to check my wires. He said everything looked fine. Yet the problem persists. This problem has been going on for more than year now and I'm extremely frustrated and just lost on what else to do. Any help or advice would be greatly appreciated. Thank you.Solved2.5KViews0likes5Comments
Packet Loss and Latency Spikes
This is not the first time this is happened (it happens periodically), but I am having issues with packet loss and disconnects between my modem and the ISP (hop 2). They are intermittent and very annoying. I pay $75 a month for fast internet, and I am the only person who uses it, yet I have constant problems. I had these issues with the old Cox-issed Cisco modem and my current Surfboard SB6183. Same issues with three different routers as well (Apple AirPort Extreme, Netgear Nighthawk X6, Linksys WRT1900AC). It has to be on Cox's end, but I get zero help when I call in and talk to support. They always ask me stupid questions (have you reset the modem, have you checked your router, have you tried connecting directly to the modem via ethernet, etc.) and say everything looks fine on their end. I had a tech out last month and he pulled a filter/splitter off and replaced it and said things were fixed. I was at work when he came and my housemate said that he was here for about 10 minutes. Below is a screenshot of Pingplotter, the status page of my modem, and the event log of my modem. http://i.imgur.com/1Gnp1a5.png 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 QAM256 73 813000000 Hz 8.7 dBmV 40.2 dB 9 65 2 Locked QAM256 74 819000000 Hz 9.1 dBmV 40.3 dB 23 48 3 Locked QAM256 75 825000000 Hz 8.9 dBmV 40.3 dB 17 56 4 Locked QAM256 76 831000000 Hz 9.1 dBmV 40.2 dB 43 133 5 Locked QAM256 77 837000000 Hz 9.4 dBmV 40.3 dB 15 84 6 Locked QAM256 78 843000000 Hz 9.8 dBmV 40.1 dB 11 67 7 Locked QAM256 79 849000000 Hz 9.7 dBmV 40.5 dB 13 60 8 Locked QAM256 80 855000000 Hz 9.6 dBmV 40.3 dB 18 69 9 Locked QAM256 89 909000000 Hz 8.8 dBmV 40.3 dB 15 55 10 Locked QAM256 90 915000000 Hz 8.7 dBmV 40.3 dB 38 61 11 Locked QAM256 91 921000000 Hz 8.7 dBmV 40.3 dB 24 98 12 Locked QAM256 92 927000000 Hz 9.2 dBmV 40.5 dB 38 31 13 Locked QAM256 93 933000000 Hz 8.8 dBmV 40.3 dB 22 81 14 Locked QAM256 94 939000000 Hz 8.2 dBmV 40.1 dB 49 107 15 Locked QAM256 95 945000000 Hz 7.7 dBmV 39.9 dB 18 57 16 Locked QAM256 96 951000000 Hz 8.2 dBmV 40.0 dB 12 69 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 37300000 Hz 36.9 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 19400000 Hz 34.8 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 24300000 Hz 35.3 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 30800000 Hz 36.0 dBmV Current System Time: Mon Jan 02 20:18:17 2017 Time Priority Description Mon Jan 02 20:02:24 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:45:13 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:44:45 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:44:44 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:43:15 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:40:31 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:39:48 2017 Notice (6) TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jan 02 19:38:47 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Mon Jan 02 19:14:32 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 14:49:12 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Jan 01 12:18:24 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Sun Jan 01 12:06:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:08 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:04 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 07:45:18 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 04:12:00 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:36 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:26 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 01:04:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 00:34:59 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 22:08:29 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:37:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:57 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:29:30 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:21:46 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:04:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 18:26:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 17:06:43 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 14:38:58 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:22:19 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:20:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 09:14:17 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 20:11:54 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:32:03 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:31:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 14:19:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:53:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:32:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:06:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:44:52 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:16:42 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 09:43:45 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 08:47:55 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 23:01:39 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:37:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:10:05 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:09:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:05:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:04:38 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 12:16:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 10:44:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 04:02:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:35:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:46 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 20:58:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 14:04:29 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:26:04 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:25:50 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:26:12 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:24:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:36 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:18:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:29:10 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:27:38 2016 Critical (3) Resetting the cable modem due to docsDevResetNow Tue Dec 27 14:13:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 14:06:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 13:57:24 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 12:15:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 11:34:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 09:26:31 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 17:42:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:59 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:45 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 14:20:37 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 13:40:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:39:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 04:37:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 00:05:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 14:36:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 09:44:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0;8.6KViews0likes24Comments
!!!!---Constant Internet Speed Issues---!!!!
Since I have had Cox I have had constant connectivity issues. Our modem has been upgraded to the Netgear N450 CG3000Dv2 to assist with our previous connectivity issues. We were running at 15 Megs on our previous plan and had constant speed of 8 Megs MAX. I just upgraded our internet to 50 Megs and we are lucky to get 2 Megs of download speed on a good day. We are paying almost 2x the prior cost for a slower speed. I checked our modem compatibility and it states the hardware can process up to 150 Megs of download speed. I have hard RESET the modem and RESET the connection on the online tool multiple times now. I understand Cox to be more reliable than other internet providers. Their customer service is extremely friendly, but unfortunately I have not been able to have any of these issues resolved. I have our most recent speed test provided below. Of which, I see it doesn't show up. Basically, it details we are running at 1.66 Megs on download and 2 Megs on upload. Our upload speed is faster than the download! Any advise or information would be greatly appreciated.2.2KViews0likes1Comment
Internet shutting off
So whenever I turn on my Xbox and play online, eventually my wifi will turn off. The router will still be on, but the wifi light shuts off and we lose wifi throughout the whole house. The wifi will only turn off when the xbox is connected online. Any explanation why this happens?1.2KViews0likes1Comment
Poor Connection Quality at Night
I stream games on Twitch.Tv and have been in this apartment for over a year now. I have experienced the usual disconnects due to maintenance, a rogue storm, etc. Starting November 11th, however, every night around 6:00 PM -8:00 PM CST, my connectivity to Twitch takes a dive. Download seems consistent, but Uploads are choppy and drop anywhere from 25 - 80% frames. Initially, I thought this was an OBS encoding/settings issue so I spent the weekend troubleshooting and changing settings with no success. I began checking my hardware for driver updates, put additional memory into my computer, etc. I tried to fix ever issue I could find before moving onto the next step, my internet connection. Using the Twitch Broadband Tester, I got the following results: Prior to November 11th, I saw some minor dropped frames, but even at its worse, the connection never went with more than 10% dropped frames. I usually connect to the Dallas hub, but have tried Chicago and San Fransisco with no improvements. I troubleshot the Twitch connection via their website and staff and everything I keep turning up points to an issue with the ISP Cox. I've run multiple speed tests, (speedtest.net, cox speed test, testmy.net) and the only one that consistently shows a "good connection" is Cox's. I don't know if I can rely on it, because I am sure that my connection to Cox is good (4 techs visiting have confirmed it), but my connection to Twitch.Tv at night drops significantly. (Also experience slower internet over all at night, but Cox's speed test again shows everything's OK.) I've had my modem replaced (a newer Arris modem), had Ingress checked multiple times (all during the morning because us night shifters get NO love from Cox or their technicians). Performed multiple DNS flushes, Modem Resets, Changed the Cables from computer to modem, changed the splitter cable from the TV and Modem, BYPASSED the splitter cable from the TV and modem, updated the modem firmware and have called into tech support so much I have memorized a good chunk of their call center staff. After being told all is good and it was Twitch's fault, I switched over to Youtube Gaming and experienced the exact same problem. A supervisor was sent out during the daytime on 11/7 to test the lines again and found no issues, but sure enough, 6 PM rolls around and my internet tanks. He believes there may be noise intermittent noise in the line during that time frame, but no techs are available to troubleshoot at that time. Called the call center again tonight after experiencing bad connectivity and was told everything is alright. Checked the forums and found that there have been other people experiencing the same/similar issues in other parts of Cox's networks. I need to know what is going on. Please let me know what information you need, will provide it. TL;DR - Cannot stream to Twitch.Tv, Youtube Gaming or Hitbox because of poor connection quality. Send help.2KViews0likes2CommentsNo internet
yesterday, Saturday, cox service apparently out in my area and said so on website. Now, Sunday, still out and no recognition of this on website. router internet and connect lights out. Is coverage still out in area code 89107? Is there something wrong with my router. Need internet for business.1.3KViews0likes1CommentFrequent Short Term Disconnects
Hi, been having some internet issues lately and was hoping to get them resolved. Recently replaced modem due to frequent service interruptions. It resolved the issues for some time but now I'm faced with a new issue. My internet cuts out for 30-60 seconds multiple times per day. This has been occurring with steadily increasing frequency. This is a wired connection, directly to modem, no splitters. Here is a copy of the modem log: 2016-08-15, 15:44:32.0 Warning (5) Dynamic Range Window violation 2016-08-15, 15:39:03.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM- MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-15, 15:20:21.0 Warning (5) Dynamic Range Window violation 2016-08-15, 15:16:53.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-15, 15:16:52.0 Warning (5) Dynamic Range Window violation 2016-08-15, 06:06:50.0 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-15, 04:13:05.0 Warning (5) Dynamic Range Window violation 2016-08-15, 02:33:53.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-15, 02:31:43.0 Warning (5) Dynamic Range Window violation 2016-08-15, 02:31:42.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-15, 02:31:26.0 Warning (5) Dynamic Range Window violation 2016-08-15, 02:30:40.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-15, 02:19:43.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-15, 02:19:42.0 Warning (5) Dynamic Range Window violation 2016-08-15, 00:08:11.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-15, 00:08:10.0 Warning (5) Dynamic Range Window violation 2016-08-15, 00:08:09.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-14, 23:56:11.0 Warning (5) Dynamic Range Window violation 2016-08-14, 18:06:50.0 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-14, 15:49:18.0 Warning (5) Dynamic Range Window violation 2016-08-14, 13:27:49.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-14, 13:03:52.0 Warning (5) Dynamic Range Window violation 2016-08-14, 12:44:25.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-14, 09:24:05.0 Warning (5) Dynamic Range Window violation 2016-08-14, 09:06:25.0 Warning (5) Dynamic Range Window violation 2016-08-14, 09:06:25.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-14, 07:24:30.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-14, 06:15:43.0 Warning (5) Dynamic Range Window violation 2016-08-14, 06:06:50.0 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-14, 01:49:06.0 Warning (5) Dynamic Range Window violation 2016-08-13, 20:01:22.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-13, 18:06:50.0 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 2016-08-13, 17:17:20.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Downstream Channel Power stays between -5db and -9db Upstream Power typically between 34db and 46db1.7KViews0likes1Comment
