B

Visitor

 • 

10 Messages

Monday, September 12th, 2022 5:32 PM

Closed

MB8611 not producing Gigabit Extra speeds

Hello all, 

I have been reading through the forum since this issue started to try and see what will resolve it. Unfortunately, it doesn't seem like there is a clear-cut answer, but there sure are a lot of people with similar issues. Back on the 6th, I upgraded to the Gigabit Extra package from Performance Pro that I had. My previous package was 175 down, 5 up. Typically we received 200 down and 5.5 up from a wired connection. Since the upgrade, we are still getting the same exact speeds as before. Long story short, we were finally able to get a tech out to check everything since Comcast saw there were issues with the signals. The tech arrived this morning and did his thing. After his work we gained a downstream channel, and went from 2 upstream channels to 6 (Awesome!); however, the speeds remained the same.

He plugged directly into the back of our modem with his tool and saw the speeds were only reaching 200 down and 8 up. The speeds in the cable were reaching the appropriate levels and he even showed that to me to confirm. At first, he said the modem (Motorola MB8611) was not compatible with gigabit internet, but I showed him on the website that it was. He then said there must be something wrong with the modem. I showed him the event logs from my modem, but he said everything looked fine. He recommended using the Xfinity modem/router or buying a new modem. However, reading the forums I have seen this being said to other people with similar issues and even after those people dump money towards new modems it does not seem to resolve their issues. I would rather not spend additional money to speculate, but I would also rather not rent the modem/router combo from Comcast and prefer to use my own equipment. Any advice or help is appreciated. Unfortunately, because of the reset of the modem, the logs seem to have been cleared, and this is all that is available. These are the same errors as previously.  

Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Warning (5)   Lost MDD Timeout;CM-MAC=REDACTED;CMTS-MAC=REDACTED;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=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv6
    08:27:41
Mon Sep 12 2022
  Notice (6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
    08:27:41
Mon Sep 12 2022
  Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
    08:27:47
Mon Sep 12 2022
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
09:32:37
Mon Sep 12 2022
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

Visitor

 • 

10 Messages

3 years ago

Connection
   Startup Sequence    
   Startup Step Status Comment

  
   Acquire Downstream Channel 525000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 02h:02m:17s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 4 525.0 -3.0 40.8 0 0
   2 Locked QAM256 1 489.0 -5.2 39.9 0 0
   3 Locked QAM256 2 513.0 -3.4 40.6 0 0
   4 Locked QAM256 3 519.0 -3.2 40.6 0 0
   5 Locked QAM256 5 531.0 -3.0 40.7 0 0
   6 Locked QAM256 6 537.0 -2.8 40.6 0 0
   7 Locked QAM256 7 543.0 -2.4 40.7 0 0
   8 Locked QAM256 8 549.0 -2.2 40.8 0 0
   9 Locked QAM256 9 555.0 -2.1 40.8 0 0
   10 Locked QAM256 10 561.0 -2.2 40.8 0 0
   11 Locked QAM256 11 567.0 -2.2 40.7 0 0
   12 Locked QAM256 12 573.0 -2.4 40.7 0 0
   13 Locked QAM256 13 579.0 -2.8 40.5 0 0
   14 Locked QAM256 14 585.0 -2.9 40.4 0 0
   15 Locked QAM256 15 591.0 -2.9 40.4 0 0
   16 Locked QAM256 16 597.0 -2.6 40.6 0 0
   17 Locked QAM256 17 603.0 -2.2 40.8 0 0
   18 Locked QAM256 18 609.0 -2.0 40.8 0 0
   19 Locked QAM256 19 615.0 -2.0 40.8 0 0
   20 Locked QAM256 20 621.0 -2.1 40.8 0 0
   21 Locked QAM256 21 627.0 -2.1 40.9 0 0
   22 Locked QAM256 22 633.0 -2.1 40.8 0 0
   23 Locked QAM256 23 639.0 -2.1 40.9 0 0
   24 Locked QAM256 24 645.0 -2.1 40.9 0 0
   25 Locked QAM256 25 651.0 -2.0 40.8 0 0
   26 Locked QAM256 26 657.0 -2.0 40.9 0 0
   27 Locked QAM256 27 663.0 -2.0 40.8 0 0
   28 Locked QAM256 28 669.0 -2.1 40.9 0 0
   29 Locked QAM256 29 675.0 -2.0 40.5 0 0
   30 Locked QAM256 30 681.0 -2.0 40.8 0 0
   31 Locked QAM256 31 687.0 -2.1 40.8 0 0
   32 Locked QAM256 32 693.0 -2.4 40.6 0 0
   33 Locked OFDM PLC 193 805.0 -5.1 38.9 45353827 0


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 17 5120 35.6 45.8
   2 Locked SC-QAM 18 5120 29.2 45.0
   3 Locked SC-QAM 19 5120 22.8 44.5
   4 Locked SC-QAM 20 5120 16.4 44.5
   5 Locked SC-QAM 21 2560 40.4 47.8
   6 Locked SC-QAM 22 2560 10.4 44.5

Visitor

 • 

3 Messages

3 years ago

Hi @BottomoftheBarrel 

I am having a very similar issue with my 900 Mbps service.  I have now tried 4 cable modems (2 Netgear CM2000's, 1 CM1200, 1 Motorola MB8611) over the past week and they are all giving the same speeds - typically between 400-600 Mbps, which is the same or worse as what I got before with my 600 Mbps plan.  

Based on my experience, I agree with you that buying a new modem won't help.  Using the Xfinity-provided router may be an improvement, but I personally don't want to pay the rental fee and I shouldn't have to.  There has to be something else going on in the system and I haven't been able to get to the bottom of it yet.

Visitor

 • 

10 Messages

3 years ago

Since I needed to provide this to Motorola, here is an update to the connections page: 

Connection
   Startup Sequence    
   Startup Step Status Comment

  
   Acquire Downstream Channel 621000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 05h:09m:57s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 20 621.0 -1.9 40.8 38 129
   2 Locked QAM256 13 579.0 -1.8 40.9 0 0
   3 Locked QAM256 14 585.0 -1.6 40.9 97 460
   4 Locked QAM256 15 591.0 -1.4 40.9 100 466
   5 Locked QAM256 16 597.0 -1.3 41.0 129 488
   6 Locked QAM256 17 603.0 -1.2 41.0 116 415
   7 Locked QAM256 18 609.0 -1.4 41.0 118 491
   8 Locked QAM256 19 615.0 -1.7 40.9 141 489
   9 Locked QAM256 21 627.0 -2.1 40.7 110 475
   10 Locked QAM256 22 633.0 -2.1 40.8 101 510
   11 Locked QAM256 23 639.0 -2.1 40.9 142 494
   12 Locked QAM256 24 645.0 -2.0 40.9 100 530
   13 Locked QAM256 25 651.0 -1.8 40.9 143 446
   14 Locked QAM256 26 657.0 -1.7 40.9 121 464
   15 Locked QAM256 27 663.0 -1.6 40.9 108 467
   16 Locked QAM256 28 669.0 -1.9 40.9 103 455
   17 Locked QAM256 29 675.0 -2.0 39.7 125 495
   18 Locked QAM256 30 681.0 -2.1 40.9 100 481
   19 Locked QAM256 31 687.0 -2.2 40.8 136 472
   20 Locked QAM256 32 693.0 -2.4 40.6 113 499
   21 Locked QAM256 33 699.0 -2.4 40.6 102 475
   22 Locked QAM256 34 705.0 -2.6 40.6 111 478
   23 Locked QAM256 35 711.0 -3.0 40.5 108 482
   24 Locked QAM256 36 717.0 -3.3 40.4 135 473
   25 Locked QAM256 37 723.0 -3.6 40.3 133 478
   26 Locked QAM256 38 729.0 -4.0 40.3 133 475
   27 Locked QAM256 39 735.0 -4.6 40.2 116 493
   28 Locked QAM256 40 741.0 -5.4 39.9 128 484
   29 Locked QAM256 41 747.0 -5.7 39.7 15279 16774
   30 Locked QAM256 42 753.0 -6.1 39.4 19933 29269
   31 Locked QAM256 43 759.0 -6.4 39.3 103 486
   32 Locked QAM256 44 765.0 -6.2 39.3 125 481
   33 Locked OFDM PLC 193 805.0 -5.3 38.8 126917895 0


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 17 5120 35.6 45.8
   2 Locked SC-QAM 18 5120 29.2 45.3
   3 Locked SC-QAM 19 5120 22.8 44.8
   4 Locked SC-QAM 20 5120 16.4 44.5
   5 Locked SC-QAM 21 2560 40.4 48.3
   6 Locked SC-QAM 22 2560 10.4 44.5

Visitor

 • 

10 Messages

3 years ago

Hello everyone. For those who are following, or for those in the future who are reading, I will try and update this thread as it proceeds to its conclusion. My issue is still unresolved, so yesterday I contacted Xfinity chat support again, and they have now opened a ticket for a tier 2 technician to call me and come out. I haven't received a confirmation email or text, but I did provide the ticket number the first CSR gave me to a second CSR and that CSR confirmed that the ticket was open, it was indeed for a tier 2 technician, and that it was all in order. They said I may have to wait up to 48 hours to receive a call from them. 

Visitor

 • 

10 Messages

3 years ago

Here is an update on the event logs. Please note that I copied from AFTER the event logs of my previous posts. 

10:36:12
Mon Sep 12 2022
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
    10:36:27
Mon Sep 12 2022
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-QOS=1.1;CM-VER=3.1;
    10:36:31
Mon Sep 12 2022
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-QOS=1.1;CM-VER=3.1;
    10:37:02
Mon Sep 12 2022
  Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;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-QOS=1.1;CM-VER=3.1;
    10:42:19
Tue Sep 13 2022
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;CM-QOS=1.1;CM-VER=3.1;
    10:42:25
Tue Sep 13 2022
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;CM-QOS=1.1;CM-VER=3.1;
    10:43:07
Tue Sep 13 2022
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;CM-QOS=1.1;CM-VER=3.1;
    10:43:07
Tue Sep 13 2022
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.1;
    10:43:08
Tue Sep 13 2022
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;CM-QOS=1.1;CM-VER=3.1;
    10:43:09
Tue Sep 13 2022
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.1;
    10:43:09
Tue Sep 13 2022
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;CM-QOS=1.1;CM-VER=3.1;
    10:43:09
Tue Sep 13 2022
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.1;
    10:43:11
Tue Sep 13 2022
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-QOS=1.1;CM-VER=3.1;
    10:43:11
Tue Sep 13 2022
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;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-QOS=1.1;CM-VER=3.1;
    13:05:50
Tue Sep 13 2022
  Critical (3)   No Ranging Response received - T3 time-out;;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv6
    18:56:57
Tue Sep 13 2022
  Notice (6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    18:57:09
Tue Sep 13 2022
  Critical (3)   No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
    18:57:37
Tue Sep 13 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;;CM-QOS=1.1;CM-VER=3.1;
    20:32:46
Tue Sep 13 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;
    20:33:23
Tue Sep 13 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;;CM-QOS=1.1;CM-VER=3.1;
    04:59:12
Wed Sep 14 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;
    04:59:46
Wed Sep 14 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;;CM-QOS=1.1;CM-VER=3.1;

(edited)

Visitor

 • 

10 Messages

3 years ago

Here is an update from today on the connections page. 

Connection
   Startup Sequence    
   Startup Step Status Comment

  
   Acquire Downstream Channel 621000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 14h:33m:51s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 20 621.0 -2.2 40.6 0 0
   2 Locked QAM256 13 579.0 -1.2 41.0 0 0
   3 Locked QAM256 14 585.0 -1.0 41.1 0 0
   4 Locked QAM256 15 591.0 -1.0 41.0 0 0
   5 Locked QAM256 16 597.0 -1.0 41.0 0 0
   6 Locked QAM256 17 603.0 -1.0 41.0 0 0
   7 Locked QAM256 18 609.0 -1.3 40.9 0 0
   8 Locked QAM256 19 615.0 -1.7 40.7 0 0
   9 Locked QAM256 21 627.0 -2.6 40.3 0 0
   10 Locked QAM256 22 633.0 -2.9 40.2 0 0
   11 Locked QAM256 23 639.0 -3.1 40.3 0 0
   12 Locked QAM256 24 645.0 -2.9 40.1 7 0
   13 Locked QAM256 25 651.0 -2.5 40.4 13 26
   14 Locked QAM256 26 657.0 -2.0 40.7 14 38
   15 Locked QAM256 27 663.0 -1.5 40.9 8 40
   16 Locked QAM256 28 669.0 -1.5 41.0 5 33
   17 Locked QAM256 29 675.0 -1.5 38.7 31 0
   18 Locked QAM256 30 681.0 -1.5 40.9 25 0
   19 Locked QAM256 31 687.0 -1.5 40.9 0 0
   20 Locked QAM256 32 693.0 -1.7 40.8 0 0
   21 Locked QAM256 33 699.0 -1.6 40.9 0 0
   22 Locked QAM256 34 705.0 -1.7 40.7 0 0
   23 Locked QAM256 35 711.0 -2.1 40.5 0 0
   24 Locked QAM256 36 717.0 -2.3 40.7 0 0
   25 Locked QAM256 37 723.0 -2.5 40.6 0 0
   26 Locked QAM256 38 729.0 -2.8 40.7 0 0
   27 Locked QAM256 39 735.0 -3.4 40.6 0 0
   28 Locked QAM256 40 741.0 -4.0 40.3 0 0
   29 Locked QAM256 41 747.0 -4.4 39.8 0 0
   30 Locked QAM256 42 753.0 -4.8 39.5 0 0
   31 Locked QAM256 43 759.0 -5.5 39.6 0 0
   32 Locked QAM256 44 765.0 -5.6 39.6 0 0
   33 Locked OFDM PLC 193 805.0 -4.4 39.2 408767231 0


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 17 5120 35.6 45.5
   2 Locked SC-QAM 18 5120 29.2 45.3
   3 Locked SC-QAM 19 5120 22.8 44.8
   4 Locked SC-QAM 20 5120 16.4 44.5
   5 Locked SC-QAM 21 2560 40.4 47.5
   6 Locked SC-QAM 22 2560 10.4 44.5

Problem Solver

 • 

1.1K Messages

Hey there, @BottomoftheBarrel. I am sorry to hear you are having issues with your speeds. I'd be happy to check into this for you on our end. Can you send us a PM with your name and address? 

 

Here's the detailed steps to direct message us:

• Click "Sign In" if necessary

• Click the “chat" icon (upper right corner of this page)

• Click the "New message" (pencil and paper) icon

• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list

• Type your message in the text area near the bottom of the window

• Press Enter to send your message

I no longer work for Comcast.

Visitor

 • 

10 Messages

3 years ago

Here is what the representative from Motorola was telling me. They say that the modem is functioning properly, and said that "I have noticed in the event logs you have multiple t3 time outs- which indicates network drops/packet losses that the unit has been experiencing intermittent connection. In the connection page, your downstream bonded channels pwr were in the range bn -7 to +7, snr are bn 30-50, corrected&uncorrected - are not 0 shows these channels are experiencing a signal issue, while in the upstream bonded channels the pwr levels are bn 38-50."

She also notes that the technician plugging directly into the back of the modem and getting those speeds and not the ones I am supposed to receive (even though the cables apparently check out) means that Comcast is using the incorrect speed file. 

Visitor

 • 

10 Messages

3 years ago

Hello all!

As promised I am here to provide an update. The tier 2 tech did not need to call, text, email, or anything, and what he was sent to do did not require a home visit. They checked everything and it all checked out. They marked the job as complete, but I still had the same issue. Since I was not aware that they did not need to call, text, email, etc (as I was told they would need to) I was back on the chat with Xfinity to find out where the tech was which is when the CSR explained that they completed their work and did not need to do any of that because it wasn't a home visit. 

The solution, or seemingly at this time, appears to have been a bootfile for my modem. The CSR I spoke with today informed me that the wrong bootfile was being used, and they corrected it. After the bootfile was changed, my modem rebooted, and sure enough, my speeds skyrocketed. My tower uses Windows 10 64-bit, Ryzen 5 2600x, 16GB RAM, SATA-SSD (Shhh), and mobo has a gigabit port. The cable is a Cat5E, about 40 feet, and about a year old. Without changing any config on my end I am currently getting 685.22mbps down and 41mbps up directly from the modem. 

Problem Solver

 • 

948 Messages

3 years ago

I have a mb 8611 modem, I can achieve 1400 Mbps + on a computer from 2011..

forum icon

New to the Community?

Start Here