Upload Speeds

[HorusLupercal]

Hello All,

TLDR -

1. From Tech visit on August 18th, 2024 - the tech indicated the line was not properly grounded and would send a crew to fix. No further contact was made by Mediacom or 3rd party. I ended up calling back for follow-up.
2. From Tech visit on September 5, 2024 - a local issue was to blame for my issues. the tech didn't want to investigate anything on prem and promptly left - He said the issue would be resolved when maintenance was complete
3. From Tech visit September 10, 2024 - new drop line run from TAP to residence with proper grounding to electrical equipment. The issue still persists tech said TAP maintenance needs to be done. Arizona 811 was out here maybe over a week ago.
4. When can I expect someone to address my upload issue? Just to be clear with request I don't care, nor did I ever care, about the line being buried. I just want to know when someone will actually fix whatever is the tech found so that I can login to my company's remote assets so I can do my job. Otherwise, I can no longer afford internet.

I've been back and forth with several methods of support (text, chat, telephone, tech visit, x(formerly twitter), escalation to on-duty manager) at Mediacom as of late so I thought I would give this place a try. I've been having issues since May in Southern Arizona. In August, I was able to get someone to come take a look at the issue and confirm that the issues did in fact exist.

The mcc tech claimed that an improper ground was responsible for my issues which sounded dubious but I allowed him to dispatch his "team" to fix it. A week later, I hadn't been contacted. So I decided to call back and scheduled another tech visit.

When the second mcc tech arrived, they did not want to come on premises to investigate the issues because there was a "local issue" that was currently being worked on. Rather than have someone working on my connection that didn't want to be there, I allowed them to cancel based on their recommendation. Oh boy what a mistake to trust that guy.

I once again contacted support to schedule a tech visit. This time the original mcc tech from the first visit showed up and claimed that an improper ground wouldn't cause the issues I'm seeing (I'm glad he finally agreed with me.) I insisted that whatever the problem was, that I be fixed during today's visit. His solution was to run a new line from TAP to residence.

Now this is where I can get no traction. My issue is not fixed and MCC support seems to believe I'm calling about line burial services and will not discuss further.

I'm hoping there is a level-headed community manager out there that can investigate and assist. Please share this with whoever you feel appropriate.

Full disclosure, please do not suggest the following course of action we are well past this : "If it is still not working please power cycle the power to the modem and, if you have one, the power to your wireless router. Please wait 30 seconds and then, in this order, please plug the modem back in first and then plug in the wireless router and wait for the devices to boot up. If you're still having issues with the services after that please reach back out to us."

SAMPLE OF ERRORS:

Spoiler

Time Priority Description
Wed Sep 11 23:45:58 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 23:45:45 2024 Warning (5) MDD message timeout;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 21:35:06 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 21:34:44 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 21:34:41 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 20:34:00 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 20:33:49 2024 Warning (5) MDD message timeout;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 20:24:32 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 16:53:12 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 16:53:03 2024 Warning (5) MDD message timeout;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 15:56:38 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 15:56:12 2024 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 15:56:09 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 15:56:09 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 15:56:09 2024 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 11 15:56:05 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv4
Wed Sep 11 15:55:50 2024 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi

Time Priority Description
Thu Sep 12 15:32:27 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 15:12:00 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 15:11:47 2024 Warning (5) MDD message timeout;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:58:11 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:16:13 2024 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:16:12 2024 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:09:35 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:05:52 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:05:08 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:05:04 2024 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:05:02 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:05:02 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:05:01 2024 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:04:57 2024 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:04:53 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv4
Thu Sep 12 14:04:47 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:04:21 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 14:03:07 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:39:26 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:38:57 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:38:04 2024 Warning (5) Auth Reject - No Information;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:57 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:54 2024 Warning (5) Auth Reject - No Information;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:53 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:48 2024 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:46 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:46 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:46 2024 Warning (5) ToD request sent - No Response received;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:46 2024 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:41 2024 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:37 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv4
Thu Sep 12 13:36:34 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:36:20 2024 Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:35:44 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:35:17 2024 Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:34:11 2024 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:34:02 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:33:54 2024 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=94:18:65:cc:39:7b;CMTS-MAC=94:d4:69:55:05:60;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 12 13:33:41 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv4
Thu Sep 12 13:33:29 2024 Error (4) T6 Timeout and retries exceeded;CM-MAC=94:18:65:cc:39:7b;CMTS-

[MediacomErin]

Hello @HorusLupercal,

I apologize for the duration of the issue you are having. Please email my team at Totalcare@mediacomcc.com and we will help.

Thank you

- Erin 

[HorusLupercal]

I'm not sure if I'm being trolled or simply disrespected, but the appointment you set up for me was an absolute joke. Besides completely losing my patience, nothing was done to improved my situation. In fact, it is actually worse now.

The tech who arrived, same tech from visits 1 and 2 from TLDR, to install a grey plastic box. This is beyond extremely disappointing, I feel like I've been slapped in the face and spit on.

He also, urged me to "follow him down the street" so I could see that another tech was working on my block. Naturally, I was not in any way interested in dropping my job (which is relying on 5G cell service instead of cable internet right now) so that I could go watch someone not work on my problem. As if what he was offering was some sort of sign of good faith. What a ridiculous notion. 

A sign of good faith would have been fix my problem that I've been calling about and offering great detail and even greater patience.

I only have one question:

What are you all going to do to fix this?

[MediacomErin]

I  am sorry that the technician was not able to resolve the problem when he was on site. Please email my team Totalcare@mediacomcc.com for assistance with your account. 

Thank you

-Erin