Download speed is very low, Worst customer service as usual
My internet plan was 150Mbps and the download speed I got is 30Mbps maximum. I contacted the customer service and explained my situation. The representative suggested they would send a technician to check my location if there are any issues and they will charge me $75.00 for that visit. I don't know why should I pay for Cox to do their job and provide a reliable service to the customers. COX always takes the advantage of customers who don't have an option to switch to other service providers as my community has only COX as the service provider. The service is always slow and disgusting Cox doesn't care about their customers at all.381Views0likes1Comment
High Pings and Jitters along with Packet Loss
Hi all, I have been having high pings and large packet loss every single day for the past 2 months (before the COVID-19 outbreak), and have had bufferbloat every time I connect to wifi. I thought the problem was with the Ethernet and hence bought a new wire to test yet this problem persisted. The following is my trace route to google: Tracing route to www.google.com [2607:f8b0:4007:804::2004] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 2600:8800:802:900:120c:6bff:fe78:2352 2 56 ms 52 ms 39 ms 2600:8800:87f:ffff::1111 3 * 12 ms * 2001:578:801:fffc::e 4 202 ms 38 ms 77 ms 2001:578:800:4:9800::2 5 33 ms 55 ms * 2001:578:1:0:172:17:249:33 6 49 ms 39 ms 26 ms 2001:4860:1:1::131a 7 34 ms 59 ms 26 ms 2607:f8b0:820d::1 8 29 ms 31 ms 38 ms 2001:4860:0:110f::1 9 31 ms 28 ms 25 ms 2001:4860:0:110f::13 10 24 ms 43 ms 37 ms 2001:4860::c:4000:de3c 11 * 30 ms * 2001:4860::9:4000:de3b 12 23 ms 72 ms 67 ms 2001:4860:0:1::1039 13 26 ms 44 ms 35 ms lax28s15-in-x04.1e100.net [2607:f8b0:4007:804::2004] Trace complete. The third hop almost always times out and I have no idea why. Please let me know what I can do, I have tried everything contacted all technicians but they have not been able to figure out anything. I currently use a 150mbps residential connection with a Netgear C6250 router modem.1.4KViews0likes1CommentSpeeds
So who all has issues with their speeds not being consistent or instead just losing connection to the internet completely? I find myself driving up my cellphone bill more often then not since I have to rely on my cellphones internet to do most things at home since the connection from COX seems to not work most of the time. I know I have talked to a group of people from work that also have a facebook thread talking about this same issue with their speeds and connections constantly going out only to be told it is their cable modem so they buy a new one only to have the same issue. I myself have done this in the past a few times as well and it gets old. I had to sign a contract for internet service just a few months back and I do the exact same stuff with my internet as I did before and sometimes even less (sometimes by choice other times since internet is down) I feel like I definitely dont want to pay more for the same terrible service it seems I keep getting. But the Internet rates seem like they constantly go up and we get less for it. I have been made to feel like I am not worth having as a customer by customer service many times when getting an attitude that seems like "well if you dont like it go somewhere else" . Anybody else get the same kind of issues or feeling that COX really doesn't care about their customers at all? Seems like more and more they just care about the next swindle they can pull to get more money and give less.644Views0likes2Comments
Unstable Internet and Packet Loss (8 Months)
I have been dealing with this issue for coming up on 8 months now. I called back in January about massive packet loss. The rep I spoke to basically said that it could be the modem. I did not believe this to be an issue but decided to look up the modem I had at the time and found out that it had a Puma 6 chipset which can cause issues with online games and other issues, so I decided I might as well replace it anyway. Went out the next day and spent a little over $200 on a new modem. Called and got it updated to my account and still experiencing the same issues. At this time I then start experiencing issues with internet outages and unstable internet connections. Mostly my upload will not be consistent and will eventually just zero out and lose connection but running a speed test will show that I am still getting about 30mbs up. This mostly happened at night until early morning until around 9AM then go back to being mostly fine throughout the day. I call again and they suggest sending a service tech out. The tech comes and tests my hardware and finds no problems but suggested replacing the line in the wall and that could be the issue. Issues is still not resolved. Call again and they send another service tech out and again is not able to replicate issues since they come after the issue clears up. They suggest replacing the line that runs from the house to the box in the front yard. Ok. They replace this and still the issue is happening. I consult with a friend that now lives in Germany that does live streaming for a living and told me that he dealt with this exact same issue before he moved and told me that it is a problem with the node and I will need to keep calling and harassing Cox until they come out and fix it because getting them to escalate anything is a pain. At this time I notice that there have been multiple Cox trucks out in my area by my house just down the street over the months and have had 2 internet outages completely that Cox was aware of. I have had other techs out at least 1 per month at this point. I call Cox again and tell them that I am still experiencing the same issues but now the issue is starting to get worse because it is happening earlier in the day. They tell me again that they need to send another service tech out. I tell them that they have already sent multiple to the house and they never find anything or do anything that makes any difference and want to get this escalated and taken care of and that they need to come look at the node. The rep informs me that the only way that they can get this escalated to someone that can come look at the node is to have 3 service techs out within the same month and that the service tech needs to be the one to escalate it to that point. They schedule the tech to come out again and he says that he does see the packet loss and was working with someone in "engineering"? (I believe that was the department he said) and that he would get this escalated and that they should be reaching out to me within 24-48 hours. 2 Days go by and I have not heard anything from Cox. I call them to get the details on if they have come out and was told that they have come out but wasn't told what they had done. I let a few days go by and still experiencing issues. The internet is worse than ever. My connection is not stable at all. My upload will fluctuate constantly and will eventually 0 out and just give up. Packet loss is worse that ever upwards of 50-60 percent. I call Cox again and ask to speak to a manager. She tries to get me to tell her what is going on but I do not want to have to repeat myself to her then the manager. I then have to tell her what is going on and that I need to get this issue resolved. She sounds like she is consulting with someone on her end since she is pausing a lot and then tells me that she will get the issue escalated with her supervisor's help. 2 more days go by and I don't hear anything from Cox. I call Cox again and demand to speak to a manager. I get to a manager and explain everything that I have been going through. I tell her that I called and was told that my issue was getting escalated and that there should be a ticket for it. The manager tells me that they opened the wrong type of ticket and that the escalation had been cancelled. I do not have her name but this manager was very nice and professional and actually sounded like she knew what she was talking about. She got my issue escalated and scheduled them to come look at the node FINALLY and the tech was out the next day. I even saw the tech and know where the node is now. A week goes by and within this week it seems that everything has been resolved. Some packet loss here and there but Its nothing terrible like it was. Upload was solid as well and no issues. Then all the sudden everything starts coming back. Upload is completely unreliable and unstable. Again the upload will completely zero out and just give up and packet loss is back. The issues I am experiencing are happening all the time now. The packet loss is constantly happening and the upload is never stable. I work from home and upload very large files and do streaming on the side. The files I upload will time out and eventually fail and streaming is constantly dropping frames and will eventually disconnect from Twitch. I call again and inform them that the issue is happening again. I have to explain everything to a rep and am told that they will get my issue escalated. I ask to speak to manager/supervisor. They transfer me over and the supervisor tells me that the previous rep is now getting it escalated and should be here on Monday 7/29/2019 and that I will not have to be home for this. Today is 7/29/2019 and at 6:30PM I have not noticed any Cox truck down my street and they did not leave a thing on my door letting me know that service was done. I call Cox for an update and speak to a rep that informs me that a ticket was open but can not inform me when they will be out and was scheduled for today. I hang up because that is not an acceptable answer. I call again and ask to a supervisor/manager. (I know at this point that Cox's Tier 1 reps are almost worthless and cannot get the information you need for anything you follow up with) The supervisor explains to me that they opened a ticket that will go no where because they are not able to escalate tickets to that department. The rep I spoke with is Brittany 6773. She informed me that to get this properly escalated that she needs to send a service tech out. I tell her I do not want any service techs to come to my house anymore because they do nothing and they typically say they do not see an issue. She informs me that she will re-open the ticket I had before when they came and looked at the node and will follow up with me tomorrow. I am now waiting for this to see if it eventually goes through. My experience with Cox has been completely miserable. It has been 8 months and I am still dealing with the same issues and nothing has been resolved. They have only credited me $100 dollars which doesn't even cover a full month and all I have is internet service. I pay $86 per month and another $50 a month for their unlimited data plan. Which Cox should not be limiting data in the first place. I have been lied to 2 times and have been told that an issue was escalated and will be taken care of to find out that the ticket was escalated to the wrong department. I have had MULTIPLE techs come to my house to do basically nothing because anything they do does not effect the issue in anyway. I have called and had to explain my situation so many times to these reps and supervisors which always try to up sale to a higher plan or a business account which even if I did it is still going through the same node and will still be experiencing the same issues.I have also been told that they can not credit me anything until the work gets done and the issue is resolved which I know they are not going to credit me the last 8 months of the same issue. I am completely at a loss at this point and do not know what else to do to get Cox to fix this issue with the packet loss and unstable connection. I am extremely frustrated and thinking at this point of just switching to Century Link and seeing if their lower speed connection will at least be stable enough for me to use my internet... I have lost so much time and I am sure have cost COX quite a bit of money to have all these techs sent out and take up the time speaking to reps on the phone but they do not seem to care about their customers. I have to deal with someone different every time I call them and explain my situation to them every time. COX has not helped me with my issues with their service and at this point do not believe they will.2.7KViews0likes5Comments
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
webmail
i have been unable to send or rec email since early august. My bill is always around $200 and i have internet that at times can not do anything, when it does i get possibly half what i pay for. Then thry nickel and dime you with box rental and a rouvalidter rental fee for one thats no longer even . i hope someone who has s9ome authority receives a fwd of this message. will be looking fwd to the downfall of Cox in thr upcoming years as more people catch on its not necessary to watch t.v. Nothimg I cant do over the web or phone and bluetooth to my big screen. been getting bent over too long, starting tio hurt, sad in Louisiana1.7KViews0likes2CommentsHIGH bill!!!!! Had 2 YEAR price guarantee... Laughable joke ...
Since having your service, I've been lied to repeatedly.. My bill continues to get higher, even though I was told my bill would be the same for TWO years!!! (Kept the recording as proof!) It hasn't even been a year and my price has gone up... I call in and complain, they 'fix it' (to what it should have been anyway!) next month same thing... and you want me to continue with your service??????? I don't think so!! Fix your problems with billing, follow through with what your employees are telling people, and maybe, maybe you might keep more customers and have a LOT less complaints to deal with...1.6KViews0likes2CommentsRE: Downgrade Internet Service
Response from Cox Moderator is *** **! The fact is, Cox or any other communication provider will not allow on-line down-grades! You're screwed man! The providers want to make it *** near impossible to downgrade services. They will gladly "upgrade" (= more $) your "service", even if it already screws you! I know Cox wont post this, but at least I can vent!!!!!!!!!!!!!!!! Forum: Internet Forum Posted: 14 Nov 2015 Post Subject: RE: Downgrade Internet Service Post author: NicholeC Hi Medginful, The purpose of the Cox Internet Forum is to allow customers to discuss technical topics related to residential Cox High Speed Internet services with other customers. If you need help with billing or other account specific issues, please reach us on Twitter at @CoxHelp, visit us on Facebook, or at cox.help@cox.com. Thank you,0Views0likes0CommentsConstant outages (starting at 8 AM)
I work from home, and I keep having outages that coincidentally start at 8 am and go until around 10-11 AM. Your customer service team tells me that each day, the issue will be resolved, yet it comes back again (3 times this week so far). Today they told me my issues would be resolved by 5 PM, which is coincidentally 1 hour after my scheduled work day ends. I'm ready to take my 200/month and go with a competitor (who could get me service for much cheaper). Do you not provide any uptime guarantee or higher priority service for your outages (for a business account who needs reliable internet)? I could get more reliable service from WIFI tethering on my cell phone at this point.1.5KViews0likes1Comment
Download speed is very low, Worst customer service as usual
My internet plan was 150Mbps and the download speed I got is 30Mbps maximum. I contacted the customer service and explained my situation. The representative suggested they would send a technician to check my location if there are any issues and they will charge me $75.00 for that visit. I don't know why should I pay for Cox to do their job and provide a reliable service to the customers. COX always takes the advantage of customers who don't have an option to switch to other service providers as my community has only COX as the service provider. The service is always slow and disgusting Cox doesn't care about their customers at all.High Pings and Jitters along with Packet Loss
Hi all, I have been having high pings and large packet loss every single day for the past 2 months (before the COVID-19 outbreak), and have had bufferbloat every time I connect to wifi. I thought the problem was with the Ethernet and hence bought a new wire to test yet this problem persisted. The following is my trace route to google: Tracing route to www.google.com [2607:f8b0:4007:804::2004] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 2600:8800:802:900:120c:6bff:fe78:2352 2 56 ms 52 ms 39 ms 2600:8800:87f:ffff::1111 3 * 12 ms * 2001:578:801:fffc::e 4 202 ms 38 ms 77 ms 2001:578:800:4:9800::2 5 33 ms 55 ms * 2001:578:1:0:172:17:249:33 6 49 ms 39 ms 26 ms 2001:4860:1:1::131a 7 34 ms 59 ms 26 ms 2607:f8b0:820d::1 8 29 ms 31 ms 38 ms 2001:4860:0:110f::1 9 31 ms 28 ms 25 ms 2001:4860:0:110f::13 10 24 ms 43 ms 37 ms 2001:4860::c:4000:de3c 11 * 30 ms * 2001:4860::9:4000:de3b 12 23 ms 72 ms 67 ms 2001:4860:0:1::1039 13 26 ms 44 ms 35 ms lax28s15-in-x04.1e100.net [2607:f8b0:4007:804::2004] Trace complete. The third hop almost always times out and I have no idea why. Please let me know what I can do, I have tried everything contacted all technicians but they have not been able to figure out anything. I currently use a 150mbps residential connection with a Netgear C6250 router modem.Speeds
So who all has issues with their speeds not being consistent or instead just losing connection to the internet completely? I find myself driving up my cellphone bill more often then not since I have to rely on my cellphones internet to do most things at home since the connection from COX seems to not work most of the time. I know I have talked to a group of people from work that also have a facebook thread talking about this same issue with their speeds and connections constantly going out only to be told it is their cable modem so they buy a new one only to have the same issue. I myself have done this in the past a few times as well and it gets old. I had to sign a contract for internet service just a few months back and I do the exact same stuff with my internet as I did before and sometimes even less (sometimes by choice other times since internet is down) I feel like I definitely dont want to pay more for the same terrible service it seems I keep getting. But the Internet rates seem like they constantly go up and we get less for it. I have been made to feel like I am not worth having as a customer by customer service many times when getting an attitude that seems like "well if you dont like it go somewhere else" . Anybody else get the same kind of issues or feeling that COX really doesn't care about their customers at all? Seems like more and more they just care about the next swindle they can pull to get more money and give less.
