CM1000v2 modem with slow speeds of 480mbps

[Alpha1991]

I have been using my CM1000v2 Modem for the past six months. My plan with xfinity is 1200 Mbps. I recently gotten in contact with them and they send an electrician over. They fixed an issued on the outside but still have no more than 480-560 Mbps. I spoke to a rep online and she did all types of test and she tells me is my modem. While, I am still trying to figure out what happen. It has been going like this for the past 3.5 weeks. I usually get around 850-980 Mbps but this is by far less. Xinifty said is my modem, but I see there is a problem.

[Kitsap]

---

@Alpha1991 wrote:
I have been using my CM1000v2 Modem for the past six months. My plan with xfinity is 1200 Mbps. I recently gotten in contact with them and they send an electrician over. They fixed an issued on the outside but still have no more than 480-560 Mbps. I spoke to a rep online and she did all types of test and she tells me is my modem. While, I am still trying to figure out what happen. It has been going like this for the past 3.5 weeks. I usually get around 850-980 Mbps but this is by far less. Xinifty said is my modem, but I see there is a problem.

---

What is the brand name and model number of the router you have connected downstream of your CM1000v2?

Do you have a PC with an Ethernet port you can connect directly to your CM1000v2 for testing?

If yes, use the Ookla installable test application on the PC.  Power down your modem and the PC.  Power up your modem and give it plenty of time to boot and stabilize.  Connect the Ethernet to your computer and boot your computer.  Be patient, it might take a few minutes for your PC to get an IP address direct from your ISP.

[Alpha1991]

What is the brand name and model number of the router you have connected downstream of your CM1000v2?

I am a bit confused by this, what do you mean? I thought that was private information. Sorry! New to all of this. I will send out what router log said.

[Kitsap]

---

@Alpha1991 wrote:
What is the brand name and model number of the router you have connected downstream of your CM1000v2?

I am a bit confused by this, what do you mean? I thought that was private information. Sorry! New to all of this. I will send out what router log said.

---

Just exactly what it says.  You are complaining about the throughput performance of a cable modem, CM1000v2.

Downstream of that modem you should have a router of some unknown brand name and unknown model number that you connect to some unknown device where you are testing performance.  Difficult to provide assistance without knowing what hardware is connected in the data stream path.

When you say send out what router log said, nothing is found.  Where did you send it?

[Alpha1991]

2023-06-15, 13:15:55	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 13:13:47	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 04:06:01	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 04:03:59	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 04:01:26	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 04:01:25	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:30:44	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:28:36	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:10:03	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:08:01	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:05:58	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:05:47	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 01:37:38	Warning (5)	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 01:37:32	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 17:49:06	Critical (3)	Resetting the cable modem due to docsDevResetNow
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 17:19:42	Critical (3)	Resetting the cable modem due to docsDevResetNow
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 16:03:29	Critical (3)	Resetting the cable modem due to docsDevResetNow
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 15:50:46	Critical (3)	Resetting the cable modem due to docsDevResetNow
2023-06-14, 14:06:27	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:06:22	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:03:45	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:03:43	Critical (3)	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:03:39	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:03:35	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:02:01	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:57	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:56	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:55	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:55	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:55	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;

[Alpha1991]

Sorry, I read that wrong, my router is the "nighthawk pro gaming WIFI6 Gaming Router XR1000"

[Kitsap]

Repeat question:  Do you have a PC that you can directly connect to the CM1000v2 with an Ethernet cable and test your throughput?

How is your unknown test device connected to your XR1000?  Via Wi-Fi or via Ethernet cable.

How are you testing your throughput on your unknown test device?  Are you using an application?  A web browser and some testing address?

[Alpha1991]

Repeat question:  Do you have a PC that you can directly connect to the CM1000v2 with an Ethernet cable and test your throughput?
 
I do!



How is your unknown test device connected to your XR1000?  Via Wi-Fi or via Ethernet cable.
 
Usually I do test with the Nighthawk app.
3 weeks ago, I noticed the difference in speed because I play intense games. So my latency was high 100 when I usually get 10-14 ping. So this happen out of nowhere.

The last log on the app was at 890 Mbps Upload was 42 MBPS and ping was 13 June 2,2023

Now is at 574.50 Mbps Upload 41.93 Mbps Ping
52.0. Let me remind that I have 1.2 gbps for internet.


How are you testing your throughput on your unknown test device?  Are you using an application?  A web browser and some testing address?

Nighthawk app hasn’t failed me with testing speed. This is the first time I have troubles with my speed since I usually have been running at 800 and had no issues for the past 7 months.

[Kitsap]

The Nighthawk application is testing throughput from the internet to your router through your modem.  That is a good reference point.  Your test values should be 1200+.  Xfinity routinely over provisions by 20%.

Are you certain your Ethernet cable between your modem and your router is good?  Recommend using a cat 6a for your application.

Xfinity is really fond of pointing fingers at customer owned hardware.  The primary goal of Xfinity is to increase their revenue by leasing you one of their modem/gateways.

Recommend you connect a PC direct to your modem as described in my previous post and use the Ookla installable test application.

[Kitsap]

Additional helpful information would be provided by the cable connection page from your modem.  Copy and past just like you did for your modem event log.  Xfinity phone support can be erratic at times.

https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...

[Alpha1991]

When I spoke to the technician yesterday. He said everything is fun in the inside, but the outside he change the cables since they were old. He did made a difference in the upload speed, but not the download speed.

So when I msg support because you just can’t call them for whatever reason it takes an hour to get a hold to a physical person. The lady quickly told me to do the reset and do the troubleshoot. Then after all of that she was it may be your device that is malfunctioning you need to get a hold to NETGEAR to send you a replace one. I am like what!!

I strictly told her, speed doesn’t just randomly decreases in less than 3 weeks and it starts shooting up up and downs she was is a hardware problem.

Sorry to bug you what is a cat 6 and which one is the best one in your opinion.

Just to note I just bought a Netgear Nighthawk ax2700 just to test the waters and see if the hardware is actual the problem, but I want to fix the issue with the one I have first before anything. I wouldn’t be surprise is their end.

[Kitsap]

Cat 6a recommendation available from Amazon.  https://a.co/d/bJA8TgW

I seriously doubt if the problem is your modem.  However, not an impossibility.

Not sure what part of the country you are located, but Xfinity has a major task on its' plate making upgrades to their system as well as keeping the existing system running smoothly.  You might get a glimpse of what is going on looking at the logs in your router.  Not something to post here without sanitizing out the IP addresses.  I live in the Seattle area and Xfinity has been all over the place the past 6 months and I expect it to continue for at least another year.

As a general rule, you do not post your WAN IP addresses or MAC addresses on an open forum.  It is a task to edit them out when you copy and paste.  If I need to share the data, I copy and paste into a word processing program and then use a global search and replace before saving as a PDF file.

[Kitsap]

---

@Alpha1991 wrote:

Just to note I just bought a Netgear Nighthawk ax2700 just to test the waters and see if the hardware is actual the problem, but I want to fix the issue with the one I have first before anything. I wouldn’t be surprise is their end.

---

I would really really hesitate to replace a stand alone modem and a stand alone router with a combination device.

From what I can see about your setup, you have a modem with a 1 Gbps rated output port and a router with a 1 Gbps rated input port.  In reality, the maximum you are ever going to get through the 1 Gbps rated ports is around 940-950 Mbps.

I am not a gamer!  In keeping with the stand alone modem and stand alone router configuration, you need to look for devices with 2.5 Gbps output and 2.5 Gbps input ports.  Avoid devices with link aggregation.

[Alpha1991]

This help a lot, didn’t know that either. That’s how much I was getting for the past 7 months before this became a problem. I didn’t mind the 850-950 I was getting, but when it dropped to 500 that’s when I saw the problem!

[Kitsap]

Copy and paste your cable modem connection sheet as requested above.  We can see what it takes to get you back to your ~950 Mbps throughput.

[Alpha1991]

I thought I did that? Sorry

If not how do I do that?

[Kitsap]

---

@Alpha1991 wrote:
I thought I did that? Sorry

If not how do I do that?

---

You posted your cable modem event log.  Not the cable modem connection sheet.  Two different things.

Details here:  https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...

There is nothing in those sheets that needs to be edited out.  Be sure and get clear to the bottom where is shows system up time. 

[Alpha1991]

I honestly thought I send it this morning. I put it tmw night, sorry.

[Alpha1991]

This is what i was able to send out

[Alpha1991]

Here is the other one 

[Kitsap]

Your cable connection logs show a couple of things.

First, your signal power levels are good.  The modem expects signal power levels between +7 and -7 dBmV.  Yours are basically in the middle.  The dynamic range is very good. Info for reference: https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router.

Your correctable/uncorrectable code words show some significant values.  These are transmission errors and should essentially be zero.  On the connection page, these values accumulate over time since the modem was last booted.  Your screen snips did not show the system up time so I do not know if these values accumulated over a few hours, a few days, a few weeks or ?.

Recommend your pull the power cord on your modem, restart it and monitor the code word values.  Right after the restart, they should all be zero.  The page does not update in real time.  When you access the page, the values are a snapshot in time.  To get new values, you have to go to a different page and then come back.

Continued correctable/uncorrectable signal errors are the responsibility of the ISP.  Xfinity has been doing significant upgrade work in my area and there are time frames with a lot of transmission errors and a lot of disconnects.

[FURRYe38]

Any Criticals, Errors or Warnings seen in the Event logs needs to be reviewed and resolved by the ISP.

Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
Be sure your using good quality RG6 coax cable up to the modem. 
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.

---

@Alpha1991 wrote:

2023-06-15, 13:15:55	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 13:13:47	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 04:06:01	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 04:03:59	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 04:01:26	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 04:01:25	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:30:44	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:28:36	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:10:03	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:08:01	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:05:58	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 03:05:47	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 01:37:38	Warning (5)	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 01:37:32	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 17:49:06	Critical (3)	Resetting the cable modem due to docsDevResetNow
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 17:19:42	Critical (3)	Resetting the cable modem due to docsDevResetNow
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 16:03:29	Critical (3)	Resetting the cable modem due to docsDevResetNow
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 15:50:46	Critical (3)	Resetting the cable modem due to docsDevResetNow
2023-06-14, 14:06:27	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:06:22	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:03:45	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:03:43	Critical (3)	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:03:39	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:03:35	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:02:01	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:57	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:56	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:55	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:55	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;
2023-06-14, 14:01:55	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:a5:11:8d:c4:84;CMTS-MAC=00:01:5c:86:f6:62;CM-QOS=1.1;CM-VER=3.1;

---

[Alpha1991]

Here is the thing when I ran a test on DUMA OS
Now I have 921/212.0 mbps
41/23 MBps
Max Ping 12.98

[Kitsap]

---

@Alpha1991 wrote:
Here is the thing when I ran a test on DUMA OS
Now I have 921/212.0 mbps
41/23 MBps
Max Ping 12.98

---

When compared to your throughput on June 13, these numbers are a direct indication you have just been through the Xfinity mid-split upgrade.  That is why you are showing the 200+ Mbps upload and why your download has been sporadic in the previous few weeks.  It may take a few weeks for Xfinity to fine tune their new hardware.  Then your service should settle down.  What area of the country do you live in?

[Alpha1991]

In New Jersey, but I am surprise they never said anything or send out a later they are doing upgrades. Since it effected my system. Isn’t the reason why some of us pay so muck for internet?