High packet loss every time it rains. No fix so far
I'm to the point I'm ready to go to AT&T and downgrading to 50 down and 3 up just to get internet that actually works. I'm paying 190$ a month for internet that doesn't work. I've been with Cox for the 10 years I've been in my house. I never had any issues. Then August 2019 happened. We had 100 mph winds come through. Ever since I get 35-50% or more of packet loss every time the wind blows or it rains. I have tech after tech after tech out to look at my equipment. The last tech that came out said "everything is fine" well yes while he was here everything was working fine. Unfortunately the techs cancel or I can't seem to get a tech out here when the issue is actually happening. Right now I'm sitting at 35% packet loss. My logs in my modem look like this.
22:11:48 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:12:08 Thu Nov 21 2019 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:12:11 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:12:41 Thu Nov 21 2019 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:13:31 Thu Nov 21 2019 |
Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:13:33 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:14:03 Thu Nov 21 2019 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:14:56 Thu Nov 21 2019 |
Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:15:29 Thu Nov 21 2019 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:15:53 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:16:23 Thu Nov 21 2019 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:17:25 Thu Nov 21 2019 |
Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:17:46 Thu Nov 21 2019 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:17:50 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:18:20 Thu Nov 21 2019 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:19:22 Thu Nov 21 2019 |
Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:19:28 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:19:58 Thu Nov 21 2019 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:20:56 Thu Nov 21 2019 |
Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:22 Thu Nov 21 2019 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:26 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:56 Thu Nov 21 2019 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:25 Thu Nov 21 2019 |
Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:25 Thu Nov 21 2019 |
Critical (3) | Ranging Request Retries exhausted;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:25 Thu Nov 21 2019 |
Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:24:09 Thu Nov 21 2019 |
Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:24:20 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:24:50 Thu Nov 21 2019 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:05 Thu Nov 21 2019 |
Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:09 Thu Nov 21 2019 |
Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:39 Thu Nov 21 2019 |
Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:05 Thu Nov 21 2019 |
Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:b8:de;CMTS-MAC=00:b6:70:99:58:f0;CM-QOS=1.1;CM-VER=3.1; | |||
|
|
||||||||||||||||||||||||||||||||||||||
|
Is there anyone out there that works for Cox that can assist me. I am the head of IT at work. If I hear one more technician tell me it's because I don't have a Cox branded modem/router or ask me "how many devices I have connected and if they are wired or wireless" I'm going to lose my *** mind. Last Chance. I will not be paying another bill from Cox unless this is fixed.