Community Forum

Cable Modem keeps losing connection. T3 & T4 errors in log

Frequent Visitor

Cable Modem keeps losing connection. T3 & T4 errors in log

Okay, so for the last 14 days I've been suffering random outages, 4 to 10 times a day.  I purchased a new CM1100 modem.

 

I've checked my cable run and have no splitters.  I actually ran a single long shot of coax from my outside to my cable modem.  The connections look clean and showed no sign of water intrustion.

 

Help?

 

This is the dump from my new modem:

 
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency

<tabindex=-1>Startup Procedure</tabindex=-1>
Procedure Status Comment
Acquire Downstream Channel 651000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 32 651000000 Hz -3.3 dBmV 38.9 dB 108447866 7277 20998
2 Locked QAM256 1 453000000 Hz -2.4 dBmV 39.7 dB 107359257 2307 3921
3 Locked QAM256 2 459000000 Hz -2.6 dBmV 39.7 dB 107358556 3570 6652
4 Locked QAM256 3 465000000 Hz -2.8 dBmV 39.3 dB 107364505 2985 5477
5 Locked QAM256 4 471000000 Hz -2.9 dBmV 39.3 dB 107371141 2217 3301
6 Locked QAM256 5 477000000 Hz -2.9 dBmV 39.1 dB 107375524 2040 2815
7 Locked QAM256 6 483000000 Hz -3.2 dBmV 38.8 dB 107380994 1455 1437
8 Locked QAM256 7 489000000 Hz -3.2 dBmV 38.9 dB 107386070 865 796
9 Locked QAM256 8 495000000 Hz -3.5 dBmV 38.6 dB 107388597 1159 1603
10 Locked QAM256 9 519000000 Hz -3.7 dBmV 36.8 dB 107385694 1912 2824
11 Locked QAM256 10 525000000 Hz -3.6 dBmV 38.6 dB 107391352 1274 1617
12 Locked QAM256 11 531000000 Hz -3.7 dBmV 38.5 dB 107396835 463 405
13 Locked QAM256 12 537000000 Hz -3.8 dBmV 38.4 dB 107400960 324 318
14 Locked QAM256 13 543000000 Hz -3.9 dBmV 38.3 dB 107404582 504 321
15 Locked QAM256 14 549000000 Hz -4.0 dBmV 38.5 dB 107407107 949 1128
16 Locked QAM256 15 555000000 Hz -4.3 dBmV 38.4 dB 107408823 1471 2355
17 Locked QAM256 16 561000000 Hz -4.1 dBmV 38.5 dB 107409806 2287 4353
18 Locked QAM256 17 567000000 Hz -3.6 dBmV 38.1 dB 107414033 2225 4038
19 Locked QAM256 18 573000000 Hz -3.5 dBmV 38.8 dB 107418231 2311 3385
20 Locked QAM256 19 579000000 Hz -3.5 dBmV 38.8 dB 107424317 1372 1695
21 Locked QAM256 20 585000000 Hz -3.3 dBmV 38.9 dB 107431597 340 217
22 Locked QAM256 21 591000000 Hz -3.3 dBmV 38.7 dB 107435960 64 54
23 Locked QAM256 22 597000000 Hz -3.8 dBmV 38.4 dB 107439537 33 70
24 Locked QAM256 23 603000000 Hz -4.2 dBmV 38.2 dB 107442688 373 309
25 Locked QAM256 24 609000000 Hz -4.3 dBmV 38.3 dB 107442177 2183 2648
26 Locked QAM256 25 615000000 Hz -4.2 dBmV 37.9 dB 107434509 5447 11219
27 Locked QAM256 26 621000000 Hz -4.2 dBmV 38.4 dB 107427118 8435 18990
28 Locked QAM256 27 627000000 Hz -4.0 dBmV 38.6 dB 107411492 11876 29432
29 Locked QAM256 28 633000000 Hz -3.4 dBmV 38.9 dB 107414315 10504 27569
30 Locked QAM256 30 639000000 Hz -3.3 dBmV 38.9 dB 107392373 9940 27577
31 Locked QAM256 31 645000000 Hz -3.1 dBmV 38.9 dB 107403448 7861 20733
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 9 36500000 Hz 43.3 dBmV
2 Locked ATDMA 10 30100000 Hz 43.8 dBmV
3 Locked ATDMA 11 23700000 Hz 43.3 dBmV
4 Not Locked Unknown 0 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Hz 0.0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked 0, 255 29 690000000 Hz -2.0 dBmV 36.3 dB 1108 ~ 2987 212832863 211968878 221
2 Not Locked 0, 255 0 0 Hz 0.7 dBmV 0.0 dB 0 ~ 4095 0 0 0

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked Unknown 0 0 Hz 0 dBmV
2 Not Locked Unknown 0 0 Hz 0 dBmV

Current System Time: Tue Apr 23 11:15:01 2019 

 

 

Frequent Visitor

Re: Cable Modem keeps losing connection. T3 & T4 errors in log

 
 
 
 
Time Priority Description
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
2019-04-23, 10:23:00 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 10:22:55 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 10:22:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 10:22:31 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 10:21:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 10:21:41 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 10:19:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 10:19:03 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 10:19:01 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;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=3c:37:86:ea:e9:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:49:42 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:49:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:49:10 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:48:57 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:48:56 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:46:29 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:46:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:46:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;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=3c:37:86:ea:e9:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:37:37 Critical (3) Resetting the cable modem due to docsDevResetNow
2019-04-23, 00:35:05 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:34:55 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:34:54 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:34:08 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:34:07 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:31:33 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:31:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-23, 00:31:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;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=3c:37:86:ea:e9:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-04-22, 22:09:14 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-22, 22:08:53 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-22, 22:08:53 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-22, 22:08:05 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-22, 22:08:04 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-22, 22:05:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
2019-04-22, 22:05:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=3c:37:86:ea:e9:40;CMTS-MAC=00:01:5c:6e:18:5b;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=3c:37:86:ea:e9:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Expert

Re: Cable Modem keeps losing connection. T3 & T4 errors in log

The signal stats are o/k but the error log entries and the uncorrectable codewords indicate that something is going on. Perhaps there is noise ingress into the line(s) somewhere.

 

There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.

 

I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS to see whether or not everything is in the green zone, see your node / cable plant and modem health, and also see a history plot for the modem. You should get a reply here in your topic. Good luck !



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? Mark the post as Best Answer!
Official Employee

Re: Cable Modem keeps losing connection. T3 & T4 errors in log

Hi, Jason_Z. Welcome to the community. We appreciate you posting and are glad that you found us here. We'll be happy to help you figure out what might be going on and causing your trouble. If you can please send me PM with your name, we can get started. I will take a look at modem history and signal strengths on this end, as well as check the health of the area that supplies service to your home. I will reply from there, thank you.


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Frequent Visitor

Re: Cable Modem keeps losing connection. T3 & T4 errors in log

PM Sent, let's hope this issue can be resolved!

Official Employee

Re: Cable Modem keeps losing connection. T3 & T4 errors in log

Good deal, I replied back. You're welcome to get back to be at your convenience. Thank you.


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Frequent Visitor

Re: Cable Modem keeps losing connection. T3 & T4 errors in log

For those reading this in the future:

 

I checked all of my connections and made sure each cable plug was tightened in snugly.  I made sure my outside connection was clean and the grounding line was good.

 

After getting phone & forum techs alerted to the problem; something at Xfinity got fixed.   I think someone got my values tweaked/adjusted.

 

I don't know if there was a bad amp, a plant signal issure, or someother problem.

There have been no breaks in service for the last.. two? days now.  No new entries in my modem's logs.

 

For those curious, here's the readout now:

 
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency

<tabindex=-1>Startup Procedure</tabindex=-1>
Procedure Status Comment
Acquire Downstream Channel 651000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 32 651000000 Hz -3.4 dBmV 41.0 dB 1641880522 0 0
2 Locked QAM256 1 453000000 Hz -2.5 dBmV 41.8 dB 1640735464 29 4
3 Locked QAM256 2 459000000 Hz -2.7 dBmV 41.8 dB 1640738912 8 27
4 Locked QAM256 3 465000000 Hz -2.8 dBmV 41.6 dB 1640742761 8 27
5 Locked QAM256 4 471000000 Hz -2.9 dBmV 41.6 dB 1640745676 11 23
6 Locked QAM256 5 477000000 Hz -2.9 dBmV 41.6 dB 1640750163 6 29
7 Locked QAM256 6 483000000 Hz -3.0 dBmV 41.5 dB 1640754621 30 0
8 Locked QAM256 7 489000000 Hz -2.9 dBmV 41.4 dB 1640756397 0 0
9 Locked QAM256 8 495000000 Hz -3.1 dBmV 41.2 dB 1640774027 0 0
10 Locked QAM256 9 519000000 Hz -3.8 dBmV 38.3 dB 1640778929 23 0
11 Locked QAM256 10 525000000 Hz -3.9 dBmV 41.1 dB 1640782383 0 0
12 Locked QAM256 11 531000000 Hz -4.2 dBmV 40.9 dB 1640785518 0 0
13 Locked QAM256 12 537000000 Hz -4.4 dBmV 40.8 dB 1640789029 0 0
14 Locked QAM256 13 543000000 Hz -4.6 dBmV 40.5 dB 1640792425 0 0
15 Locked QAM256 14 549000000 Hz -4.9 dBmV 40.6 dB 1640796161 0 0
16 Locked QAM256 15 555000000 Hz -5.1 dBmV 40.3 dB 1640800467 0 0
17 Locked QAM256 16 561000000 Hz -4.9 dBmV 40.4 dB 1640833014 19 0
18 Locked QAM256 17 567000000 Hz -4.4 dBmV 39.6 dB 1640835802 0 0
19 Locked QAM256 18 573000000 Hz -4.4 dBmV 40.7 dB 1640839841 0 0
20 Locked QAM256 19 579000000 Hz -4.2 dBmV 40.7 dB 1640843593 0 0
21 Locked QAM256 20 585000000 Hz -4.0 dBmV 40.8 dB 1640847352 0 0
22 Locked QAM256 21 591000000 Hz -4.0 dBmV 40.8 dB 1640852295 0 0
23 Locked QAM256 22 597000000 Hz -4.2 dBmV 40.8 dB 1640855052 0 0
24 Locked QAM256 23 603000000 Hz -4.4 dBmV 40.7 dB 1640858731 0 0
25 Locked QAM256 24 609000000 Hz -4.6 dBmV 40.6 dB 1640862494 0 0
26 Locked QAM256 25 615000000 Hz -4.5 dBmV 39.9 dB 1640866925 0 0
27 Locked QAM256 26 621000000 Hz -4.5 dBmV 40.6 dB 1640870424 12 22
28 Locked QAM256 27 627000000 Hz -4.3 dBmV 40.7 dB 1640868925 27 0
29 Locked QAM256 28 633000000 Hz -3.7 dBmV 40.8 dB 1640870364 7 0
30 Locked QAM256 30 639000000 Hz -3.5 dBmV 40.9 dB 1640842397 0 0
31 Locked QAM256 31 645000000 Hz -3.4 dBmV 41.1 dB 1640844166 0 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 9 36500000 Hz 42.0 dBmV
2 Locked ATDMA 10 30100000 Hz 42.5 dBmV
3 Locked ATDMA 11 23700000 Hz 42.0 dBmV
4 Not Locked Unknown 0 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Hz 0.0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked 0, 255 29 690000000 Hz -2.1 dBmV 39.0 dB 1108 ~ 2987 11881756876 11800687599 0
2 Not Locked 0, 255 0 0 Hz 0.3 dBmV 0.0 dB 0 ~ 4095 0 0 0

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked Unknown 0 0 Hz 0 dBmV
2 Not Locked Unknown 0 0 Hz 0 dBmV

Current System Time: Wed Apr 24 23:54:44 2019 

 

 

Official Employee

Re: Cable Modem keeps losing connection. T3 & T4 errors in log

Thank you for the update. We are pleased that your connection is showing improvement and stability. While I didn't see any work done in your area that would have influenced the progress, I'd like to have you continue to monitor your connectivity. It's unlikely that work was done, without it manually being entered and unless it was a declared area issue. Please keep us posted over the next 7 days or so on how your connectivity seems to be. Thanks again. 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Official Employee

Re: Cable Modem keeps losing connection. T3 & T4 errors in log

Hi , Jason_Z. I ended up not hearing back from you on this in order to confirm a solution. I have completed the inaction. If you end up needing further support with it, please let me know. Thanks for your time. 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!