U

Visitor

 • 

9 Messages

Thursday, February 23rd, 2023 8:31 PM

Closed

Netgear Orbi CBR750 modem's download speed drops from 600Mbps to < 3Mbps every time "DS profile config update" event occurs (every 3 days)

Hi everyone,

I'm noticing a clear pattern here and need help troubleshooting. Every time my modem's event log shows a DS profile config update event occurred, soon after we'll use the internet and notice our download speeds have dropped from our normal 600 Mbps down to less than 3 Mbps. I'm running the speed test directly on the modem via the Netgear Orbi iOS app. Lately the DS profile config update event is occurring every 3 days. The issue seems to never resolve on its own and requires a reset of the modem in order to resolve the issue. A Comcast technician was here two days ago and wasn't able to identify root cause and resolve the issue. His hypothesis was occasional signal strength or connectivity issues, but reported while here our signal strength looks good. His hypothesis also doesn't make sense given the issue occurs every 3 days. I showed him the event log but he said he wasn't knowledgable about it.

What is the root cause of this issue, and how can I resolve it?

Below is a cable diagnostic and event logs from the modem I saved today at Thu Feb 23 08:34:16 2023:

Cable Diagnostic

Status: Poor

Internet Access: Good

Downstream Status: Poor

    Downstream Power Level: Poor
    Downstream power is poor (10.4dBmV). The recommended level is between -10dBmV to 10dBmV.

    Downstream SNR: Good

Upstream Status:  Good

    Upstream Power Level: Good


Current time: Thu Feb 23 08:34:16 2023

Startup Procedure
Acquire Downstream Channel: 537000000 Hz   Locked
Connectivity State:          Ok       Operational
Boot State:                  Ok       Operational
Security:                   Enabled   BPI+
IP Provisioning Mode:       Honor MDD   honorMdd(4)


Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID  Frequency        Power       SNR   Correctables Uncorrectables     
      1     Locked     QAM 256      1     417000000 Hz     8.5     37.3     6412     64
      2     Locked     QAM 256      2     423000000 Hz     8.5     37.3     13083     59
      3     Locked     QAM 256      3     429000000 Hz     8.8     37.3     9663     1030
      4     Locked     QAM 256      4     435000000 Hz     8.9     37.3     798843     51
      5     Locked     QAM 256      5     441000000 Hz     8.9     37.3     12550     85
      6     Locked     QAM 256      6     447000000 Hz     9.0     37.3     10693     52
      7     Locked     QAM 256      7     453000000 Hz     9.1     37.3     13126     38
      8     Locked     QAM 256      8     459000000 Hz     9.4     37.3     11483     58
      9     Locked     QAM 256      9     465000000 Hz     9.5     37.6     12293     27
     10     Locked     QAM 256     10     471000000 Hz     9.5     37.6     13119     50
     11     Locked     QAM 256     11     477000000 Hz     9.6     37.6     10941     939
     12     Locked     QAM 256     12     483000000 Hz     9.8     37.6     10509     1136
     13     Locked     QAM 256     13     489000000 Hz     9.9     37.6     9011     33
     14     Locked     QAM 256     14     495000000 Hz     10.0     37.6     8974     54
     15     Locked     QAM 256     15     507000000 Hz     10.0     38.6     6216     21
     16     Locked     QAM 256     16     513000000 Hz     10.1     37.6     5896     29
     17     Locked     QAM 256     17     519000000 Hz     10.1     37.3     2596     30
     18     Locked     QAM 256     18     525000000 Hz     10.3     38.6     2420     24
     19     Locked     QAM 256     19     531000000 Hz     10.3     37.6     2501     27
     20     Locked     QAM 256     20     537000000 Hz     10.3     38.6     2806     120
     21     Locked     QAM 256     21     543000000 Hz     10.3     37.6     2142     17
     22     Locked     QAM 256     22     549000000 Hz     10.1     38.6     2407     0
     23     Locked     QAM 256     23     555000000 Hz     10.4     38.6     2047     0
     24     Locked     QAM 256     24     561000000 Hz     10.4     38.6     1795     27
     25     Locked     QAM 256     25     567000000 Hz     10.3     38.9     1937     0
     26     Locked     QAM 256     26     573000000 Hz     10.4     38.6     1570     0
     27     Locked     QAM 256     27     579000000 Hz     10.1     38.6     1940     0
     28     Locked     QAM 256     28     585000000 Hz     10.1     38.6     2690     0
     29     Locked     QAM 256     29     591000000 Hz     10.3     38.6     1312     7
     30     Locked     QAM 256     30     597000000 Hz     10.1     38.6     1182     0
     31     Locked     QAM 256     31     603000000 Hz     10.3     38.6     1134     0
     32     Locked     QAM 256     32     609000000 Hz     10.1     38.6     1354     0


Upstream Bonded Channels
Channel   LockedStatus  ChannelType ChannelID   SymbolRate        Frequency       Power     
      1       Locked       ATDMA     22       2560       10400000 Hz       40.8
      2       Locked       ATDMA     17       5120       16400000 Hz       40.3
      3       Locked       ATDMA     18       5120       22800000 Hz       41.0
      4       Locked       ATDMA     19       5120       29200000 Hz       41.3
      5       Locked       ATDMA     20       5120       35600000 Hz       41.3
      6       Locked       ATDMA     21       2560       40400000 Hz       41.8
      7       Not Locked       N/A      0       0       0 Hz       0.0
      8       Not Locked       N/A      0       0       0 Hz       0.0


Downstream OFDM Channels
Channel   LockedStatus  ProfileID  ChannelID    Frequency       Power       SNR/MER    ActiveSubcarrier    Unerror    Correctable   Uncorrectable
      1     Locked     3      193     850000000 Hz     12.0 dBmV     40.0 dB     1108~2987     0     0     0
      2     Not Locked     0      0     0 Hz     0.0 dBmV     0.0 dB     0~4095     0     0     0


Upstream OFDMA Channels
Channel   LockedStatus    ProfileID    ChannelID    Frequency       Power
      1     Not Locked     0      0     0 Hz     0.0 dBmV
      2     Not Locked     0      0     0 Hz     0.0 dBmV

Event log

Feb 12 2023 10:57:43 Alert (2) CM Certificate Error
Feb 12 2023 17:18:31 Critical (3) No Ranging Response received - T3 time-out
Feb 12 2023 21:49:47 Notice (6) CM-STATUS message sent. Event Type Code: 5
Feb 12 2023 21:56:32 Critical (3) No Ranging Response received - T3 time-out
Feb 13 2023 10:57:41 Alert (2) CM Certificate Error
Feb 13 2023 12:28:15 Critical (3) No Ranging Response received - T3 time-out
Feb 14 2023 10:57:29 Alert (2) CM Certificate Error
Feb 14 2023 14:09:26 Critical (3) No Ranging Response received - T3 time-out
Feb 14 2023 14:32:48 Notice (6) CM-STATUS message sent. Event Type Code: 5
Feb 14 2023 14:32:55 Critical (3) No Ranging Response received - T3 time-out
Feb 14 2023 15:12:22 Notice (6) CM-STATUS message sent. Event Type Code: 5
Feb 14 2023 15:13:33 Critical (3) No Ranging Response received - T3 time-out
Feb 14 2023 18:08:19 Notice (6) DS profile config update. DS Chan ID: 193.
Feb 14 2023 18:25:43 Critical (3) No Ranging Response received - T3 time-out
Feb 14 2023 18:31:28 Alert (2) CM Certificate Error
Speed test run directly on modem via Orbi iOS app. 0.81 down, 9.46 up. restart modem and issue resolves.
Feb 14 2023 19:40:02 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 14 2023 19:40:02 Notice (6) TLV-11 - unrecognized OID
Feb 14 2023 19:40:02 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 14 2023 19:40:07 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 14 2023 19:40:08 Critical (3) No Ranging Response received - T3 time-out
Feb 14 2023 19:40:19 Alert (2) CM Certificate Error
Feb 15 2023 0:13:31 Critical (3) No Ranging Response received - T3 time-out
Feb 15 2023 10:56:08 Alert (2) CM Certificate Error
Feb 15 2023 11:47:39 Critical (3) No Ranging Response received - T3 time-out
Feb 16 2023 10:56:01 Alert (2) CM Certificate Error
Feb 16 2023 11:56:30 Critical (3) No Ranging Response received - T3 time-out
Feb 17 2023 10:35:54 Notice (6) DS profile config update. DS Chan ID: 193.
Feb 17 2023 10:55:19 Alert (2) CM Certificate Error
Speed test run directly on modem via Orbi iOS app. 0.0 down, 0.0 up. restart modem and issue resolves.
Feb 17 2023 11:20:21 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 17 2023 11:20:21 Notice (6) TLV-11 - unrecognized OID
Feb 17 2023 11:20:21 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 17 2023 11:20:26 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 17 2023 11:20:26 Critical (3) No Ranging Response received - T3 time-out
Feb 17 2023 11:20:44 Alert (2) CM Certificate Error
Feb 17 2023 11:38:46 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 17 2023 11:38:46 Notice (6) TLV-11 - unrecognized OID
Feb 17 2023 11:38:46 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 17 2023 11:38:56 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 17 2023 11:38:56 Critical (3) No Ranging Response received - T3 time-out
Feb 17 2023 11:39:13 Alert (2) CM Certificate Error
Feb 17 2023 11:55:03 Critical (3) No Ranging Response received - T3 time-out
Feb 17 2023 14:03:20 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 17 2023 14:03:20 Notice (6) TLV-11 - unrecognized OID
Feb 17 2023 14:03:20 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 17 2023 14:03:26 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 17 2023 14:03:35 Alert (2) CM Certificate Error
Feb 17 2023 14:42:01 Critical (3) No Ranging Response received - T3 time-out
Feb 18 2023 10:55:42 Alert (2) CM Certificate Error
Feb 18 2023 12:16:52 Critical (3) No Ranging Response received - T3 time-out
Feb 19 2023 10:55:37 Alert (2) CM Certificate Error
Feb 19 2023 12:28:21 Critical (3) No Ranging Response received - T3 time-out
Feb 20 2023 4:49:51 Notice (6) DS profile config update. DS Chan ID: 193.
Feb 20 2023 5:29:14 Critical (3) No Ranging Response received - T3 time-out
Wife texts me that the internet is not working all morning. She restarts the modem and issue resolves.
Feb 20 2023 9:11:58 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 20 2023 9:11:58 Notice (6) TLV-11 - unrecognized OID
Feb 20 2023 9:11:58 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 9:12:08 Warning (5) RCS Partial Service
Feb 20 2023 9:12:08 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 9:12:09 Critical (3) No Ranging Response received - T3 time-out
Feb 20 2023 9:12:20 Alert (2) CM Certificate Error
Feb 20 2023 9:12:23 Notice (6) CM-STATUS message sent. Event Type Code: 4
Feb 20 2023 10:55:30 Alert (2) CM Certificate Error
Feb 20 2023 13:32:53 Critical (3) No Ranging Response received - T3 time-out
Feb 21 2023 10:55:02 Alert (2) CM Certificate Error
Feb 21 2023 13:32:27 Notice (6) CM-STATUS message sent. Event Type Code: 24
Feb 21 2023 13:32:27 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Feb 21 2023 13:32:30 Notice (6) CM-STATUS message sent. Event Type Code: 17
Feb 21 2023 13:32:38 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Feb 21 2023 13:32:40 Notice (6) CM-STATUS message sent. Event Type Code: 2
Feb 21 2023 13:32:42 Warning (5) Lost MDD Timeout
Feb 21 2023 13:33:13 Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Feb 21 2023 13:38:37 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Feb 21 2023 13:38:43 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 21 2023 13:38:43 Notice (6) TLV-11 - unrecognized OID
Feb 21 2023 13:38:43 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 21 2023 13:38:51 Warning (5) RCS Partial Service
Feb 21 2023 13:38:51 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 21 2023 13:39:01 Alert (2) CM Certificate Error
Feb 21 2023 13:39:13 Notice (6) CM-STATUS message sent. Event Type Code: 4
Feb 21 2023 13:40:04 Critical (3) No Ranging Response received - T3 time-out
Feb 21 2023 15:12:16 Notice (6) CM-STATUS message sent. Event Type Code: 5
Feb 21 2023 15:17:54 Critical (3) No Ranging Response received - T3 time-out
Feb 21 2023 18:44:42 Alert (2) CM Certificate Error
Feb 21 2023 23:44:47 Critical (3) No Ranging Response received - T3 time-out
Feb 22 2023 10:55:04 Alert (2) CM Certificate Error
Feb 22 2023 11:16:36 Critical (3) No Ranging Response received - T3 time-out
Feb 22 2023 13:06:48 Notice (6) CM-STATUS message sent. Event Type Code: 5
Feb 22 2023 13:38:11 Critical (3) No Ranging Response received - T3 time-out
Feb 23 2023 3:48:03 Notice (6) DS profile config update. DS Chan ID: 193.
Feb 23 2023 7:06:22 Critical (3) No Ranging Response received - T3 time-out
Speed test run directly on modem via Orbi iOS app. 2.74 down, 11.14 up. restart modem and issue resolves.
Feb 23 2023 8:50:23 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 23 2023 8:50:23 Notice (6) TLV-11 - unrecognized OID
Feb 23 2023 8:50:23 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 23 2023 8:50:27 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 23 2023 8:50:28 Critical (3) No Ranging Response received - T3 time-out
Feb 23 2023 8:50:39 Alert (2) CM Certificate Error
Feb 23 2023 8:58:01 Critical (3) No Ranging Response received - T3 time-out
Feb 23 2023 10:54:45 Alert (2) CM Certificate Error
Feb 23 2023 11:08:23 Critical (3) No Ranging Response received - T3 time-out

Visitor

 • 

9 Messages

2 years ago

Senior technician scheduled to come out tomorrow afternoon.

My brother in law used to be a Comcast tech for many years. He looked at my event log and cable diagnostics and seems to be concerned about the T3 timeouts and wonders if there's static electricity or noise ingress in the line.

Does anyone know if a DS profile config update could cause a modem to drop downstream speeds like I'm observing?

Do the DS profile config updates occur on a recurring schedule or only when my modem has issues/disruptions/timeouts?

Official Employee

 • 

1.6K Messages

Hello, u/user_jb223. I'm sorry to hear you're having internet signal issues lately. The DS profile is known to update with problems in the line, interruptions and T3 T4 timeouts. I'm glad to see you were able to set up an appointment to have the technician check the lines. I would be more than happy to follow up with you after the tech visit. It's important to me that your services are working properly after the work order.

 
 

 
So that I can set up a personal reminder, can you please send me a private message to Xfinity Support with your full name and full address by clicking the chat icon in the top right?

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Visitor

 • 

8 Messages

I'm having this exact same problem. It's been happening since November. Every 3 days, that "DS profile config update" message appears and my connectivity drops to nothing. I reboot, it works fine for 3 days, then it happens again.

I've had a technician here twice testing the line (he just left a few minutes ago), and there's nothing wrong. He installed a MoCA filter on his prior visit, but that doesn't help with this problem. I've been watching my event log the past couple of months, tracking and finally verifying this profile config update is at fault.

I say every 3 days, it's really about every 2 days and 20 hours. It's oddly consistent.

How do I get this resolved?

Visitor

 • 

8 Messages

These are the intervals between each of the failures I've been tracking since February. As I mentioned, it's generally 2 days 20 hours.

  • Feb 17 2023 06:52:44 to Feb 20 2023 00:47:06: 2 days, 17 hours, and 54 minutes
  • Feb 20 2023 00:47:06 to Feb 23 2023 00:16:55: 2 days, 23 hours, and 29 minutes
  • Feb 23 2023 00:16:55 to Feb 27 2023 15:56:23: 4 days, 15 hours, and 39 minutes
  • Feb 27 2023 15:56:23 to Mar 03 2023 10:02:30: 3 days, 18 hours, and 6 minutes
  • Mar 03 2023 10:02:30 to Mar 07 2023 14:24:04: 4 days, 4 hours, and 21 minutes
  • Mar 07 2023 14:24:04 to Mar 10 2023 11:23:15: 2 days, 21 hours, and 59 minutes
  • Mar 10 2023 11:23:15 to Mar 13 2023 08:59:02: 2 days, 21 hours, and 35 minutes
  • Mar 13 2023 08:59:02 to Mar 16 2023 05:41:49: 2 days, 20 hours, and 42 minutes

Feb 23 was an odd circumstance, in that that one didn't cause my connection speed to drop until 20:42:55 that evening. All other instances caused a failure pretty much immediately.

(edited)

Visitor

 • 

4 Messages

We are having the same issue with download speed. We downloaded the cable diagnostic and events log today, then called Xfinity and spoke with tech support. The rep advised us that the issue is "a noise filter". He advised us that we should unplug the router/modem and restart it. He stated that the restart is only a temporary solution as the internet speed would drop again in hours or days. He recommended that we set up an appointment with an Xfinity technician to check the lines in our home. We did so. This rep was very professional in responding to our questions. 

We then received a phone call from a rep who stated she was with the Xfinity "advanced technical team". We did not request the phone call. When we told her that the first rep stated that we needed to have a technician come to our home, she insisted that she would fix our problem and that we would not need an appointment for the tech to come to our home. We repeated many times the recommendation of the first tech. She told us he was part of the frontline team and that she has more access to tools to fix our problem. When we mentioned that the issue was a "noise filter" in our line, she stated that she would look into why we were experiencing noise in our speakers and also asked us numerous times to confirm that all of our devices were working. We advised her that our problem is not a matter of our devices not working, but a matter of the internet speed being far slower that what we are paying for. She did not understand our concerns and did not comprehend English very well at all. She was extremely rude and would not respond to our questions and concerns. She ignored what we were saying to her. She insisted time and time again that we would not need to have a technician come to our home as she had solved the problem. The entire encounter with the advanced technical team representative was extremely frustrating and the worst experience we've ever had with a customer service representative, period. The first phone conversation took 33 minutes. The second took 21 minutes, but left us feeling very upset. We have serious doubts about the abilities of the Xfinity team to solve our problem. We truly hope that the technician will provide us with a definitive solution when checking our line in the home.

Visitor

 • 

4 Messages

Cable Diagnostic

Status: Poor

Action: 
[Downstream Power Level]
Try these actions (Click the Refresh button after each step):
1) Make sure the coaxial cable is tightly connected.
2) Remove any unnecessary splitters.
3) Replace any required splitters.
4) Contact your service provider for troubleshooting help.

Internet Access: Good

Downstream Status: Poor

    Downstream Power Level: Poor
    Downstream power is poor (-13.3dBmV). The recommended level is between -10dBmV to 10dBmV.

    Downstream SNR: Good

Upstream Status:  Good

    Upstream Power Level: Good


Current time: Sat Mar 18 14:02:02 2023

Startup Procedure
Acquire Downstream Channel: 519000000 Hz   Locked
Connectivity State:          Ok       Operational
Boot State:                  Ok       Operational
Security:                   Enabled   BPI+
IP Provisioning Mode:       Honor MDD   honorMdd(4)


Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID  Frequency        Power       SNR   Correctables Uncorrectables     
      1     Locked     QAM 256     13     471000000 Hz     -11.2     38.9     0     0
      2     Locked     QAM 256     14     477000000 Hz     -11.0     38.6     0     0
      3     Locked     QAM 256     15     483000000 Hz     -11.4     38.6     0     0
      4     Locked     QAM 256     16     489000000 Hz     -11.5     38.6     0     0
      5     Locked     QAM 256     17     495000000 Hz     -11.5     38.9     14     0
      6     Locked     QAM 256     18     507000000 Hz     -12.0     37.6     2     0
      7     Locked     QAM 256     19     513000000 Hz     -12.2     37.3     0     0
      8     Locked     QAM 256     20     519000000 Hz     -12.7     37.3     0     0
      9     Locked     QAM 256     21     525000000 Hz     -12.7     37.3     0     0
     10     Locked     QAM 256     22     531000000 Hz     -13.0     37.3     0     0
     11     Locked     QAM 256     23     537000000 Hz     -13.2     36.6     0     0
     12     Locked     QAM 256     24     543000000 Hz     -13.0     37.3     0     0
     13     Locked     QAM 256     25     549000000 Hz     -13.3     37.3     0     0
     14     Locked     QAM 256     26     555000000 Hz     -13.2     37.6     2     0
     15     Locked     QAM 256     27     561000000 Hz     -12.9     37.6     0     0
     16     Locked     QAM 256     28     567000000 Hz     -13.0     36.6     0     0
     17     Locked     QAM 256     29     573000000 Hz     -12.7     37.3     0     0
     18     Locked     QAM 256     30     579000000 Hz     -12.7     37.3     0     0
     19     Locked     QAM 256     31     585000000 Hz     -12.5     37.6     0     0
     20     Locked     QAM 256     32     591000000 Hz     -12.5     37.6     0     0
     21     Locked     QAM 256     33     597000000 Hz     -12.5     37.3     0     0
     22     Locked     QAM 256     34     603000000 Hz     -12.5     37.3     0     0
     23     Locked     QAM 256     35     609000000 Hz     -12.5     37.3     0     0
     24     Locked     QAM 256     36     615000000 Hz     -12.5     37.6     2     0
     25     Locked     QAM 256     37     621000000 Hz     -12.5     37.3     0     0
     26     Locked     QAM 256     38     627000000 Hz     -12.5     37.6     0     0
     27     Locked     QAM 256     39     633000000 Hz     -12.0     37.6     0     0
     28     Locked     QAM 256     40     639000000 Hz     -12.0     37.6     0     0
     29     Locked     QAM 256     41     645000000 Hz     -11.9     37.3     0     0
     30     Locked     QAM 256     42     651000000 Hz     -11.5     38.6     0     0
     31     Locked     QAM 256     43     657000000 Hz     -11.5     37.6     0     0
     32     Locked     QAM 256     44     663000000 Hz     -11.4     37.6     0     0


Upstream Bonded Channels
Channel   LockedStatus  ChannelType ChannelID   SymbolRate        Frequency       Power     
      1       Locked       ATDMA     22       2560       10400000 Hz       43.8
      2       Locked       ATDMA     20       5120       16400000 Hz       44.8
      3       Locked       ATDMA     19       5120       22800000 Hz       46.0
      4       Locked       ATDMA     18       5120       29200000 Hz       46.5
      5       Locked       ATDMA     17       5120       35600000 Hz       46.8
      6       Locked       ATDMA     21       2560       40400000 Hz       46.5
      7       Not Locked       N/A      0       0       0 Hz       0.0
      8       Not Locked       N/A      0       0       0 Hz       0.0


Downstream OFDM Channels
Channel   LockedStatus  ProfileID  ChannelID    Frequency       Power       SNR/MER    ActiveSubcarrier    Unerror    Correctable   Uncorrectable
      1     Locked     3      193     690000000 Hz     -11.0 dBmV     39.9 dB     1108~2987     0     0     0
      2     Not Locked     0      0     0 Hz     0.0 dBmV     0.0 dB     0~4095     0     0     0


Upstream OFDMA Channels
Channel   LockedStatus    ProfileID    ChannelID    Frequency       Power
      1     Not Locked     0      0     0 Hz     0.0 dBmV
      2     Not Locked     0      0     0 Hz     0.0 dBmV


Event Log
        Time            Priority         Description
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:00:42     Alert           CM Certificate Error
Mar 10 2023 11:58:43     Critical        No Ranging Response received - T3 time-out
Mar 10 2023 15:50:47     Alert           CM Certificate Error
Mar 10 2023 17:44:06     Critical        No Ranging Response received - T3 time-out
Mar 11 2023 15:50:42     Alert           CM Certificate Error
Mar 11 2023 18:02:11     Critical        No Ranging Response received - T3 time-out
Mar 12 2023 15:50:43     Alert           CM Certificate Error
Mar 12 2023 16:29:22     Critical        No Ranging Response received - T3 time-out
Mar 13 2023 03:12:48     Notice          DS profile config update.  DS Chan ID: 193.
Mar 13 2023 10:37:16     Critical        No Ranging Response received - T3 time-out
Mar 13 2023 15:50:38     Alert           CM Certificate Error
Mar 13 2023 22:55:08     Critical        No Ranging Response received - T3 time-out
Mar 14 2023 15:50:46     Alert           CM Certificate Error
Mar 14 2023 19:29:21     Critical        No Ranging Response received - T3 time-out
Mar 14 2023 20:32:01     Alert           CM Certificate Error
Mar 14 2023 21:16:47     Critical        No Ranging Response received - T3 time-out
Mar 15 2023 15:50:43     Alert           CM Certificate Error
Mar 15 2023 16:31:27     Critical        No Ranging Response received - T3 time-out
Mar 15 2023 23:38:33     Notice          DS profile config update.  DS Chan ID: 193.
Mar 16 2023 02:40:05     Critical        No Ranging Response received - T3 time-out
Mar 16 2023 15:50:49     Alert           CM Certificate Error
Mar 16 2023 23:54:57     Critical        No Ranging Response received - T3 time-out
Mar 17 2023 11:00:35     Alert           CM Certificate Error
Mar 18 2023 08:57:17     Critical        No Ranging Response received - T3 time-out
Mar 18 2023 12:57:08     Warning         MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Mar 18 2023 12:57:08     Notice          TLV-11 - unrecognized OID
Mar 18 2023 12:57:08     Critical        Config File Rejected due to Invalid or Unexpected TLV 11
Mar 18 2023 12:57:18     Warning         RCS Partial Service
Mar 18 2023 12:57:18     Warning         RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Mar 18 2023 12:57:19     Critical        No Ranging Response received - T3 time-out
Mar 18 2023 12:57:28     Alert           CM Certificate Error
Mar 18 2023 12:57:45     Notice          CM-STATUS message sent.  Event Type Code: 23
Mar 18 2023 13:09:57     Warning         MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Mar 18 2023 13:09:57     Notice          TLV-11 - unrecognized OID
Mar 18 2023 13:09:57     Critical        Config File Rejected due to Invalid or Unexpected TLV 11
Mar 18 2023 13:10:07     Warning         RCS Partial Service
Mar 18 2023 13:10:07     Warning         RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Mar 18 2023 13:10:08     Critical        No Ranging Response received - T3 time-out
Mar 18 2023 13:10:18     Alert           CM Certificate Error
Mar 18 2023 13:16:59     Notice          CM-STATUS message sent.  Event Type Code: 23

Visitor

 • 

9 Messages

2 years ago

My issue is still unresolved and ongoing!

A senior tech came out on 2/25/23 and investigated. He observed flux and upstream tilt issues impacting my service address and three other services addresses on the same TAP component which is part of the Comcast network infrastructure. He called the network team (maintenance team), reported the flux and upstream tilt findings, and set my expectations that the maintenance team would come investigate the issue within the next 48 hours.

A few days later I speak with support and they say the maintenance team actually has a 10 day SLA to work on my escalated issue. 10 days pass and my issue keeps occurring. Over the last month, I've reach out to support and have been given conflicting status updates about the maintenance team's progress investigating my issue. Several times I was told the maintenance team's ticket number was 640311 and it was still in progress. Now this evening a support rep is telling me she sees no maintenance team ticket and no records that indicate that the maintenance team did any work at all to investigate my escalated issue. She tells me that the ticket 640311 is actually the job number of the senior tech's visit on 2/25/23.

I'm forced to schedule yet another service technician appointment and have requested the same senior tech from 2/25 to come out on 3/28 in a few days. The rep tells me this is the only way I can find out if the flux and upstream tilt issues are still present at my service address and other services addresses on the same TAP. The rep also tells me only the technicians can communicate to the maintenance team, and so if I want to find out if the maintenance team did any work when my issue was escalated, I need a tech to come back here.

I'll post an update after the senior tech visits again on 3/28.

(edited)

Visitor

 • 

9 Messages

2 years ago

A tech just came and I found out that the network team apparently fixed the flux and upstream tilt issues on Feb 26th. They also came out and fixed something on March 3rd as well.

My modem's issue was never resolved and kept occurring, so this flux and upstream tilt issue doesn't look like the root cause of my issue.

The tech observed no issues with our signal and observed no flux or upstream tilt.

The tech put me on speaker with a colleague of his, someone I believe is on the network team. He's going to keep digging and said he would forward my issue to the engineering team if he doesn't find any potential root cause but cautioned me that their response time to investigate would be slow since they cover the whole state of California.

I've mentioned how I've seen others on this forum mention this issue not occurring with Comcast rented modems, so the consensus seems the short term solution for now would be to use a rented modem and then bridge it to my Orbi CBR750 modem, effectively removing the modem responsibility from my Orbi device and just using it as a router.

Visitor

 • 

8 Messages

2 years ago

I had a tech here last week, who told me this is a known issue within Xfinity. He specifically called out CBR750 as one of the known trouble modems, and suggested reverting my firmware to before the problem began, which, for me, was November of 2022.

I did so, and so far the problem hasn't occurred again. It's only been a few days, however, so I need to wait a bit longer and see if that DS config profile update message appears.

Visitor

 • 

9 Messages

@Mike_Em​ I'd be interested to know if the firmware rollback actually works. Did you ever run a cable diagnostic report on your Orbi modem via the web interface when you're experiencing the download speed slowdown? I'd be interested to compare reports. I'm told it's bad if the modem had upstream channels with power levels above 54.0 dBmV and indicates some noise on the channel that's disrupting upstream communication between the modem and the cable modem termination system (CMTS).

I'm noticing every time I experience the issue, one of my upstream bonded channels is always 55.0 dBmV like so:

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 22 2560 Ksym/sec 10400000 Hz 55.0 dBmV
2 Locked ATDMA 17 5120 Ksym/sec 16400000 Hz 52.0 dBmV
3 Locked ATDMA 18 5120 Ksym/sec 22800000 Hz 52.0 dBmV
4 Locked ATDMA 19 5120 Ksym/sec 29200000 Hz 52.0 dBmV
5 Locked ATDMA 20 5120 Ksym/sec 35600000 Hz 52.0 dBmV
6 Locked ATDMA 21 2560 Ksym/sec 40400000 Hz 49.0 dBmV
7 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV

(edited)

Visitor

 • 

8 Messages

I went back to V4.6.5.8_2.0.54, but have still having the problem with the DS profile config update. It's happened twice since, so I'm going to go back to the version before that. It happens every 2 days and 20 hours, give or take a couple hours.

I haven't checked the power you mentioned, but will next time. Mine are usually at 47.8 dBmV.

Official Employee

 • 

1.5K Messages

@Mike_Em, we are here for you 24/7. Please let us know if you still need assistance. We would be happy to help. 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Visitor

 • 

9 Messages

@Mike_Em​ Thanks for your update about the firmware rollback attempt #1 not working.

Since your firmware rollbacks aren't working and I've had three failed attempts to identify and resolve the root cause with Comcast technicians and network engineers, I've decided to surrender and resolve this issue by doing the following:

1. Purchase one of the handful of the Xfinity recommended, certified modems. I bought the Arris SB8200 which I got used from Amazon Warehouse for $53.89 and offers free returns.

2. Purchase the Orbi RBK752 (router + satellite bundle) used from Amazon Warehouse for $110.06. Unfortunately our Orbi CBR750 modem/router won't function as a router only, so I need to replace it with a router.

3. If that setup is reliable, sell the Orbi CBR750 modem/router and move on with life.

Regular Visitor

 • 

5 Messages

@XfinityAngie​ I am experiencing the same issue as @Mike_Em and @user_jb223 .  Is there anything that you can do to help resolve this issue for me/us?  @Mike_Em did the firmware rollbacks ever provide any resolution to this issue? 

(edited)

Visitor

 • 

1 Message

2 years ago

I'm having the same issue as the experiences described above. To include the poor experience with the advanced team. So is there truly no resolution to this problem? 

Expert

 • 

107.6K Messages

2 years ago

@user_8687ba 

Please create a new topic of your own here on this board detailing your issue. Thanks. 


For future reference, it is better to submit your own post as it creates a ticket to get help, and posting on an old thread can delay getting help.

Visitor

 • 

9 Messages

2 years ago

@user_8687ba @Mike_Em @AlanD58 Hey guys, I believe Xfinity and Netgear need to work together to figure out why the CBR750 fails to reliably perform on Xfinity's network. I'm super happy I replaced by CBR750 and I've had no service issues the last 30 days! I wanted to keep the Orbi system to have a WIFI 6 mesh network in the home, so here's what I did:

1. Purchase one of the handful of the Xfinity recommended, certified modems. I bought the Arris SB8200 which I got used from Amazon Warehouse for $53.89 and offers free returns.

2. Purchase the Orbi RBK752 (router + satellite bundle) used from Amazon Warehouse for $110.06. Unfortunately our Orbi CBR750 modem/router won't function as a router only, so I need to replace it with a router.

3. Sell the Orbi CBR750 modem/router and move on with life.

I strongly encourage you all to return the CBR750 if you can. If you can't sell it and do what I did. I believe you'll be glad you made the decision. Alternatively, if you have the ability to get fiber to the home internet I'd go that route. Not an option for me here at our residence.

Visitor

 • 

4 Messages

2 years ago

I just wanted to add to the conv that it is not only that modem that is having issues I have an Arris G36 and I'm experiencing the same issue, which makes me think it is an Xfinity compatibility issue rather than modem manufacturers fault, and as a cherry on top support has been unimaginably useless, all they do is redirect the problem while at the same time saying "lets get this fixed permanently" every time. 

Visitor

 • 

8 Messages

@user_k09​ Yep. There's a reason Xfinity is rated so poorly in customer service. As mentioned earlier, I've been having this issue since November. Every time I try chatting with support, they give me the same [Edit: language] about rebooting the modem, etc. I've had multiple technicians here, and an engineer. The engineer left me his supervisor's email, but he isn't responding. This is clearly Xfinity's fault. That DS profile config update they keep sending is causing the problem.

(edited)

Valued Contributor

 • 

406 Messages

I'm so sorry you're having this issue, @user_k09. I know this was from a couple of days ago, but are you still experiencing this?

I no longer work for Comcast.

Problem Solver

 • 

567 Messages

We'd love to further investigate this issue together. Would you be willing to send us a private message with your full name and address?

 

To send a "Peer to peer" ("Private") message:

Click "Sign in" if necessary

-Click the "Direct Message" icon (square chat icon in the upper right corner of your screen next to the bell icon)

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

-Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list that appears, and the "Xfinity Support" graphic will replace the "To:" line

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

-Press Enter to send it

I no longer work for Comcast.

Visitor

 • 

8 Messages

@user_k09 @user_jb223​ A week and a half ago, I swapped the Orbi with a Motorola MT8733, and guess what? It's still happening. Every three days, I have to reboot the modem. And every single time, the last entry in the event log is another DS profile config update.

Whatever Xfinity is doing is just plain wrong, and nobody seems to be able to resolve the problem. I've been dealing with this since November, have been in chat with multiple support reps, have had multiple technicians at my house, and an engineer, and it's still happening, even with a new modem.

It's utterly ridiculous that this is still going on. And for all the Xfinity employees @XfinityTimothy @XfinityJoshuaE @XfinityAngie @XfinityRaul who keep dropping into this topic and asking if it's still going on, you're clearly not reading messages here. Yes, it's still going on. It has been for months. Xfinity is sending that DS profile config thingy to our modems and it's causing us to disconnect. Over and over and over. For months.

Visitor

 • 

4 Messages

@XfinityTimothy​ yes it is still happening
@XfinityJoshuaE will try but if this is just chatting with support I'm 100% sure that it will be pointless and useless as per all my experiences dealing with support

forum icon

New to the Community?

Start Here