Recent Discussions
continuous internet outage and cox has blocked calls
My son and his roommates live around Mclintock and Ivanhoe in Chandler 85226. They have been having non stop internet issues for the last 10 days or so. It's out again today. Cox has given them one $10 credit but cannot tell them what's wrong. It now seems that Cox has blocked their number from support both on the phone and via chat. One of they boys went into the cox store today and still couldn't get any answers. They are all doing classes online from home and aren't able to do any school work! I'm not on the acct so I'm not able to call but really, what the heck is going on in that neighborhood?
Internet Outages Every Day for the last month, and no way to chat with reps?
This is becoming absolutely absurd and I am on the verge of leaving Cox altogether. Every single day for the last month the internet has gone out at least once, but usually multiple times a day. I know for a fact this is not only an issue I am having, because if you search on twitter or downdetector at the same time, you see hundreds of people complaining their internet is out. Now, I come to the site to chat with a rep like I used to be able to but lo-and-behold Cox has rigged their website to not allow anyone to chat. The link is gone where the graphic says "chat with support" and here on the forums where it says "chat with support" if you click it, it redirects you to the general support page that is just videos. Videos aren't going to help me if my internet is repeatedly going out, Cox. Every day of losing internet while paying $100 a month is unacceptable, and further unacceptable is how Cox has made it near impossible to contact them. This business tactic is a scammy one, and i have seen it before with comms companies when they are doing something shady. Why would you make it impossible for your customers to contact you if you have nothing to hide? Having to resort to Twitter to get support is absolutely ridiculous. Cox needs to credit customers for these constant outages, and fix their website so it is not impossible to get support.
Recurring issue - Burnt Coax Cable
My internet has gone out again and for what will be the 4th time I'll have scheduled a tech come out to look at the lines. The trend I've noticed is that the drop cable from the street to the house keeps frying/getting burned up for some reason. https://imgur.com/a/OY0GM00 Note in the image the black wire is the drop from the street to the house. The white wire is the line going to the crawl space of the house. Would there be anything I may say to the tech tomorrow to try and resolve this for good?Can I get reports of outages from previous billing cycles?
I'd like to get reports of cable internet outages for previous and current billing cycles. Is there a way to get a report of these dates and times? Getting the event log from the modem and/or the alerts from the Enhanced Messaging service isn't sufficient enough proof of an outage to some employers.
Suggestions for down internet at same time every night?
Hi, I’ve had problems with my internet (50 mbps) either going out or becoming slow intermittently for awhile now and can often solve the problem with a modem refresh. For the last five nights my internet has gone down between 6-8pm and does not come up until the following morning around 8 or 9 am. After multiple attempts to get through to customer service with long wait times I was able to speak with someone over chat last night and after troubleshooting for an hour and a half was told they could not fix the problem but could see I had a problem. The only offer was to send a tech out for $75 that would stand outside of my door and tell me what to do to see if that would fix the issue. I have been down this road before and 1. I’m not paying for a service that should be provided as part of their contract for the exorbitant fees I’m paying for month in addition to the equipment I am renting from them and 2. My internet works fine during the day. This has been an ongoing issue for 5 days in a row now and is once again happening tonight and is extremely frustrating. Is cox turning off internet access at night? Is anyone else having this issue? Or can anyone recommend something that may help. I have manually unplugged and rebooted my modem. Unscrewed the cable, let it reboot. Powered down all of my devices and repeated the same process. It will not let me do a modem reset on the website now. It says it is unable to. It’s upsetting that cox is trying to make money on service calls for issues like this when they should be the ones offering a credit for the now 60 hours of time I have not been able to use my internet, but that is another issue of customer service. I would just like to find a solution to this issue.Internet Connection Keeps Dropping/Resetting
Hello from the Phoenix Area, I've been fighting with support for over a month now to get my service stabilized. I'm expecting my 3rd Tech Visit tomorrow, which is supposed to be a Supervisor Technician. I've been calling and tracking the outages. I'm getting between 10-15 disconnects a day. Some lasting up to 2 hours. I've only had service for 7 weeks now with a brand new out of the box modem, which I've already replaced with another brand new out of the box modem. Both having the same issues. The cable has been tested and checked and new connectors put on the ends twice. We've moved the connection to a different node. Still getting dropped internet. This happens throughout the day. It doesn't seem to matter the time, amount of internet traffic, or possible other usage related issues. It'll drop at 2am or 2pm or any other time in between either way. I'm getting charged $75 for each tech visit to come in and "redo my cabling" (ie put new connectors on) and I'd gladly pay for the first tech trip if it would have fixed the issue. However, it hasn't and I'm on my 3rd tech trip now.My Meraki Router is showing outages coinciding with the critical errors in the event log with the record going all the way back to July 31st. During the busy hours (Evenings 5pm to Midnight) latency will jump20-25ms to 35-50ms, dropped packets will go from 0-3% tovaryingbetween 10-50%. This is consistent every evening. I've had to contact support, insist on speaking to a manager (Which BTW none one wants to let you talk to), and demand escalated service because it's been weeks of "Reset you modem, check to make sure your connections are tight, look we reset your modem it's working now...." and getting nothing fixed. How does COX expect to retain customers if they can't provide the service that we are paying for? Hopefully we can bring this to a resolution before decide it's not work dealing with COX anymore and switch to a different ISP. Just know, if I switch at home, so to will I switch at work where we have over 60+ retail locations in the Metro Phoenix and surrounding areas.COX isn't the only ISP in town and customer service should remember that Business Users are made up of Home Users. Piss off the wrong home user and you lose a lot of business overnight. And yes I'm venting because I'm at the end of my patience. Anyways, here's the pertinent information below concerning my modem, router, errors, connection stats, etc. Current Hardware Arris SB6183 Modem Meraki MX64 Router Current Status Log 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 2 789000000 Hz -5.8 dBmV 37.6 dB 680 673 2 Locked QAM256 1 783000000 Hz -5.6 dBmV 37.6 dB 598 453 3 Locked QAM256 3 795000000 Hz -5.5 dBmV 37.7 dB 670 756 4 Locked QAM256 4 801000000 Hz -5.9 dBmV 37.5 dB 496 691 5 Locked QAM256 5 807000000 Hz -6.6 dBmV 37.2 dB 596 341 6 Locked QAM256 6 813000000 Hz -7.0 dBmV 37.1 dB 708 568 7 Locked QAM256 7 819000000 Hz -6.9 dBmV 37.1 dB 650 743 8 Locked QAM256 8 825000000 Hz -6.7 dBmV 37.2 dB 457 720 9 Locked QAM256 17 879000000 Hz -7.0 dBmV 37.1 dB 459 448 10 Locked QAM256 18 885000000 Hz -7.9 dBmV 36.6 dB 468 549 11 Locked QAM256 19 891000000 Hz -8.2 dBmV 36.4 dB 625 609 12 Locked QAM256 20 897000000 Hz -8.2 dBmV 36.5 dB 547 762 13 Locked QAM256 21 903000000 Hz -8.6 dBmV 36.4 dB 612 678 14 Locked QAM256 22 909000000 Hz -8.6 dBmV 36.3 dB 2783 640 15 Locked QAM256 23 915000000 Hz -8.4 dBmV 36.3 dB 3684 939 16 Locked QAM256 24 921000000 Hz -8.3 dBmV 36.3 dB 766 556 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 44.0 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 18400000 Hz 43.8 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 47.0 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 47.3 dBmV Current System Time:Mon Aug 06 19:23:08 2018 Current Modem Event Log Time Priority Description Mon Aug 06 14:40:02 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:15:01 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:14:13 2018 Notice (6) TLV-11 - unrecognized OID;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;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 Ranging Response received - T3 time-out Mon Aug 06 13:13:25 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:11:15 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:41:48 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 12:40:04 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:37:56 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:37:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:26:34 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 12:24:55 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:45 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:45 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:44 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 11:12:47 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 11:10:31 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 11:08:21 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 10:54:45 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 10:53:01 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 10:50:50 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:53:55 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:08:31 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 04:06:43 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:04:33 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:30:05 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:17:48 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 00:15:24 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:13:14 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 23:46:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 21:58:50 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Aug 05 21:56:58 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 21:54:48 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 12:09:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:34:23 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Aug 05 04:32:33 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:30:23 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:30:23 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:29:39 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 00:21:47 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:51:02 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 23:49:06 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Sat Aug 04 23:42:46 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:37:26 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 23:35:13 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:33:34 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:33:03 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:20:15 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 22:18:20 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Sat Aug 04 22:10:12 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 22:08:18 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:06:08 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:05:41 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:05:41 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:51:53 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 21:50:07 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 21:48:32 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:22 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:20 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:19 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:59 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:58 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:47 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:30 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:26 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:37:31 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:56:03 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 15:54:07 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:51:57 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:16:36 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0;
