U

Tuesday, August 13th, 2024 2:05 PM

Internet connectivity issues

Hello, 

I have been having issues with connecting to the internet for the past week or so and it is solved by rebooting my Arris SB8000 modem but the issue presents itself again throughout the day. I'm hoping to get some help from this community to fix the issue.

*CM MAC and the CMTS MAC details were removed for privacy.

Thank you in advance for you assistance!

Here are the details from my connection status:

Connection

The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 555000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
25 Locked QAM256 555000000 Hz 3.2 dBmV 33.9 dB 542193 0
1 Locked QAM256 393000000 Hz 3.3 dBmV 35.5 dB 27120 0
2 Locked QAM256 399000000 Hz 1.5 dBmV 34.8 dB 50638 0
3 Locked QAM256 405000000 Hz 3.1 dBmV 34.8 dB 43425 0
4 Locked QAM256 411000000 Hz 3.1 dBmV 35.0 dB 46965 0
5 Locked QAM256 417000000 Hz 2.0 dBmV 33.9 dB 147040 0
6 Locked QAM256 423000000 Hz 3.3 dBmV 34.4 dB 101849 0
7 Locked QAM256 429000000 Hz 2.0 dBmV 34.1 dB 132855 0
8 Locked QAM256 435000000 Hz 2.4 dBmV 33.9 dB 203272 0
9 Locked QAM256 453000000 Hz 2.2 dBmV 33.9 dB 266282 0
10 Locked QAM256 459000000 Hz 1.9 dBmV 34.7 dB 141865 0
11 Locked QAM256 465000000 Hz 2.7 dBmV 34.4 dB 177525 0
12 Locked QAM256 471000000 Hz 2.2 dBmV 34.6 dB 122312 0
13 Locked QAM256 477000000 Hz 3.3 dBmV 34.5 dB 134573 0
14 Locked QAM256 483000000 Hz 3.5 dBmV 34.3 dB 164117 0
15 Locked QAM256 489000000 Hz 3.8 dBmV 34.2 dB 144693 0
16 Locked QAM256 495000000 Hz 4.8 dBmV 34.0 dB 250233 0
17 Locked QAM256 507000000 Hz 4.2 dBmV 32.9 dB 870708 0
18 Locked QAM256 513000000 Hz 4.6 dBmV 33.6 dB 405626 0
19 Locked QAM256 519000000 Hz 3.4 dBmV 33.0 dB 863589 0
20 Locked QAM256 525000000 Hz 3.5 dBmV 33.3 dB 661573 0
21 Locked QAM256 531000000 Hz 2.2 dBmV 33.5 dB 635910 0
22 Locked QAM256 537000000 Hz 2.5 dBmV 33.8 dB 613861 0
23 Locked QAM256 543000000 Hz 2.3 dBmV 34.2 dB 367061 0
24 Locked QAM256 549000000 Hz 2.2 dBmV 33.8 dB 531212 0
26 Locked QAM256 561000000 Hz 3.0 dBmV 34.1 dB 425555 0
27 Locked QAM256 567000000 Hz 4.2 dBmV 34.2 dB 467899 0
28 Locked QAM256 573000000 Hz 2.5 dBmV 33.4 dB 1003518 1
29 Locked QAM256 579000000 Hz 3.7 dBmV 33.8 dB 580339 0
30 Locked QAM256 585000000 Hz 2.8 dBmV 32.8 dB 1533846 3
31 Locked QAM256 591000000 Hz 2.7 dBmV 33.0 dB 1601522 5
45 Locked Other 690000000 Hz 1.8 dBmV 29.8 dB 126503548 13606569



Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 6 Locked SC-QAM Upstream 10400000 Hz 3200000 Hz 46.0 dBmV
2 7 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 45.0 dBmV
3 8 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 46.0 dBmV
4 9 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 47.0 dBmV
5 10 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 46.0 dBmV
6 11 Locked SC-QAM Upstream 39600000 Hz 1600000 Hz 45.0 dBmV



Current System Time:Tue Aug 13 07:54:47 2024

Here are the details from my event log:

Event Log

The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

Date Time Event ID Event Level Description
08/13/2024 07:50 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;
08/13/2024 07:50 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;
08/13/2024 07:33 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;
08/13/2024 07:33 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;
01/01/1970 00:00 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 21:25 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 21:25 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 21:25 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;
08/10/2024 21:25 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 21:25 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;
08/10/2024 21:25 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 21:25 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;
08/10/2024 21:25 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 21:25 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;
08/10/2024 21:25 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 21:25 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;
08/10/2024 21:25 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 21:24 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
08/10/2024 21:24 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 21:24 73000200 3 "REG RSP not received;
08/10/2024 21:24 82000200 3 "No Ranging Response received - T3 time-out;
08/10/2024 21:24 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 21:23 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
08/10/2024 21:23 73000200 3 "REG RSP not received;
08/10/2024 21:23 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 21:22 82000200 3 "No Ranging Response received - T3 time-out;
08/10/2024 21:22 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 21:22 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
08/10/2024 21:22 68000600 3 "TFTP failed - configuration file NOT FOUND;
01/01/1970 00:02 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
01/01/1970 00:02 82000200 3 "No Ranging Response received - T3 time-out;
01/01/1970 00:01 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 13:27 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08/10/2024 13:26 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 13:26 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
08/10/2024 13:26 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 13:26 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
08/10/2024 13:26 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 13:26 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
08/10/2024 13:26 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 13:24 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 13:21 82000200 3 "No Ranging Response received - T3 time-out;
08/10/2024 13:21 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;
08/10/2024 13:21 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
08/10/2024 13:17 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;

Expert

 • 

107.1K Messages

3 months ago

All of the downstream channels SNR values are too low / out of spec. It appears that there is spurious noise ingress leaking into the line(s) somwhere. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

Here are some things that you can try to see if they apply but you may need a tech out to investigate and correct this one;

In an effort to try to obtain better connectivity, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


Good luck with it !

(edited)

8 Messages

I personally don't have any coax splittters but I'm not sure how the comcast technician set everything up in the crawl space 10 years ago. I only use comcast for internet (no phoen or TV). I may need to have a comcast tech out to the house, meanwhile, I will await some other comments. 

Thank you for your input!

Official Employee

 • 

1.6K Messages

 

user_v93vc5 Hello! We see that you've been working with our amazing Expert @EG and thank you for providing as much information as you can. We can certainly take a look at your connection and see what is going on including possibly scheduling a technician if necessary. When you can, please send a Direct Message with your full name and address. Here are instructions on how to send a DM in case you need them:

 Click "Sign In" if necessary
  • Click the "Direct Message" 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 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

Expert

 • 

107.1K Messages

3 months ago

You're welcome ! Everything is already in black and white.... Good luck !

(edited)

Expert

 • 

107.1K Messages

3 months ago

@user_v93vc5 @XfinityBenjaminM 

Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.

8 Messages

@EG​ will do! A Comcast technician is scheduled to come out tomorrow and I will post an update!

8 Messages

3 months ago

A Comcast technician came out to the house this weekend and confirmed our signal was strong at the street side but was weak at the modem. After doing some investigative work, he determined the source of the issue where our home was connected to the street (source). Adjustments were made and all is well.

There was also a monster splitter that was likely put into place when we had triple play, which we no longer have, and this also strengthened our internet connection. 

Case closed. 

Expert

 • 

107.1K Messages

3 months ago

Thanks for the update ! For curiosity, would you please post what the signal values look like now ? Thanks.

8 Messages

@EG​ I just posted the signal values. Do you need me to post the event log as well?

8 Messages

3 months ago

Here is an updated Connection log: 

Connection

The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 555000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
25 Locked QAM256 555000000 Hz 6.6 dBmV 37.6 dB 64293840 906
14 Locked QAM256 483000000 Hz 7.2 dBmV 37.4 dB 27639990 32
15 Locked QAM256 489000000 Hz 8.1 dBmV 37.8 dB 24752330 21
16 Locked QAM256 495000000 Hz 8.3 dBmV 37.1 dB 43763196 247
17 Locked QAM256 507000000 Hz 7.5 dBmV 36.0 dB 168966445 47915
18 Locked QAM256 513000000 Hz 8.4 dBmV 37.0 dB 68878839 1272
19 Locked QAM256 519000000 Hz 7.2 dBmV 36.3 dB 147162052 26004
20 Locked QAM256 525000000 Hz 7.3 dBmV 36.9 dB 100832454 6075
21 Locked QAM256 531000000 Hz 6.7 dBmV 37.1 dB 87372878 3465
22 Locked QAM256 537000000 Hz 6.5 dBmV 37.4 dB 77297825 1867
23 Locked QAM256 543000000 Hz 7.0 dBmV 38.0 dB 41032590 162
24 Locked QAM256 549000000 Hz 6.6 dBmV 37.6 dB 59534339 637
26 Locked QAM256 561000000 Hz 7.1 dBmV 37.7 dB 55108042 484
27 Locked QAM256 567000000 Hz 7.3 dBmV 37.7 dB 64030872 890
28 Locked QAM256 573000000 Hz 6.8 dBmV 37.0 dB 152154906 26879
29 Locked QAM256 579000000 Hz 7.7 dBmV 37.6 dB 81606708 2068
30 Locked QAM256 585000000 Hz 7.1 dBmV 36.8 dB 201512043 77880
31 Locked QAM256 591000000 Hz 7.4 dBmV 36.9 dB 178252942 43716
32 Locked QAM256 597000000 Hz 7.6 dBmV 37.0 dB 134195230 21869
33 Locked QAM256 603000000 Hz 8.0 dBmV 37.4 dB 81913071 22682
34 Locked QAM256 609000000 Hz 7.2 dBmV 37.2 dB 140354250 46773
35 Locked QAM256 615000000 Hz 7.7 dBmV 37.7 dB 81716883 39633
36 Locked QAM256 621000000 Hz 7.2 dBmV 37.4 dB 84624019 41716
37 Locked QAM256 627000000 Hz 6.1 dBmV 36.6 dB 178234400 68401
38 Locked QAM256 633000000 Hz 6.6 dBmV 37.4 dB 73033367 38652
39 Locked QAM256 639000000 Hz 5.1 dBmV 36.0 dB 256506133 141509
40 Locked QAM256 645000000 Hz 5.1 dBmV 35.8 dB 207023561 76509
41 Locked QAM256 651000000 Hz 4.7 dBmV 35.5 dB 266387377 158362
42 Locked QAM256 657000000 Hz 3.6 dBmV 34.6 dB 586609639 3673467
43 Locked QAM256 663000000 Hz 3.2 dBmV 34.1 dB 851074107 18343527
44 Locked QAM256 669000000 Hz 2.9 dBmV 34.1 dB 1065618664 42615420
45 Locked Other 690000000 Hz 3.1 dBmV 32.5 dB 808120797 1494360760



Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 6 Locked SC-QAM Upstream 10400000 Hz 3200000 Hz 40.0 dBmV
2 7 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 41.0 dBmV
3 8 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 42.0 dBmV
4 9 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 42.0 dBmV
5 10 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 43.0 dBmV
6 11 Locked SC-QAM Upstream 39600000 Hz 1600000 Hz 43.0 dBmV



Current System Time: Mon Aug 19 14:07:29 2024

8 Messages

3 months ago

Here is the Event Log

The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

Date Time Event ID Event Level Description
08/19/2024 12:45 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;
08/19/2024 12:42 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 12:41 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 12:41 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 12:41 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:49 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:48 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:46 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:41 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:40 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 21 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.
08/19/2024 11:40 84020300 5 "MDD message timeout;
08/19/2024 11:39 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:39 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
"CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:38 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:37 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:34 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:33 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:32 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:29 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.
08/19/2024 11:29 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:18 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1
08/19/2024 11:18 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:16 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:15 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:08 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:07 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:07 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:05 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:05 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:04 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 11:03 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 11:02 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 10:48 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 10:47 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 10:41 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 10:41 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 10:38 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 10:38 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 10:38 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 10:37 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 10:34 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 10:29 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.
08/19/2024 10:29 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.
08/19/2024 10:28 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID:

Expert

 • 

107.1K Messages

3 months ago

So the SNR's are a bit better but they are still on the low side. We'd like to see them even higher. Mine are at 43-44 dB. And there are a fair number of uncorrectable bit errors. Seems more work needs to be done. Good luck with it ! 

8 Messages

I wish the comcast tech would have addressed it on Saturday. Is this something customer service can help with or does a comcast technician need to come back to the house?

Official Employee

 • 

1.7K Messages

 

user_v93vc5 We certainly want to get this addressed for you as quickly as possible. 

Can you send us a direct message with your full name, name of account holder (if different), and service address please?

To send a "Direct Message" to Xfinity Support:

Click "Sign In" if necessary

Click the "Direct Messaging" icon (speech bubble)

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

The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there

- As you are typing a drop-down list appears. Select "Xfinity Support" from that list

- An "Xfinity Support" graphic replaces the "To:" line

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

Press Enter to send it

 

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

Expert

 • 

107.1K Messages

3 months ago

It can't be fixed remotely. It requires boots on the ground.  And bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.

Expert

 • 

107.1K Messages

For clarity. It appears that the post for which my post above is a reply to has been removed.

(edited)

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Please mark an Accepted Answer!tick
forum icon

New to the Community?

Start Here