Community Forum

Daily partial WAN disconnects

Highlighted
Frequent Visitor

Daily partial WAN disconnects

After upgrading to Xtreme+, I am getting daily WAN disconnects that are somewhat mystifying.  

When the problem occurs, some WebSocket connections are still maintained.  Specifically, 

1. Device freezes on website traffic for all devices connected, whether they are ethernet or WiFi
2. Existing video/audio streams continue, even after router is locked up. So it's not a full stop on traffic, just traffic on new requests.
3. Cannot add new devices to router

 

Modem/Router combo is a Netgear Nighthawk X4S; it's not overheating.  I did a factory reset 3 weeks ago; firmware is latest from Xfinity/Comcast (V3.01.43). Using a variety of devices running iOS, MacOS, Android, and Windows; all experience the same issue.  

 

I checked my signal strength and the values seem to be fine.

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectabables
1 Locked QAM256 20 531000000 Hz 1.4 dBmV 41.9 dB 4 0
2 Locked QAM256 17 513000000 Hz 2.5 dBmV 42.4 dB 1 0
3 Locked QAM256 18 519000000 Hz 2.3 dBmV 42.1 dB 4 0
4 Locked QAM256 19 525000000 Hz 1.9 dBmV 42.1 dB 2 0
5 Locked QAM256 21 537000000 Hz 1.0 dBmV 41.6 dB 13 0
6 Locked QAM256 22 543000000 Hz 0.7 dBmV 41.6 dB 4 0
7 Locked QAM256 23 549000000 Hz 0.3 dBmV 41.6 dB 6 0
8 Locked QAM256 24 555000000 Hz 0.1 dBmV 41.2 dB 11 0
9 Locked QAM256 25 561000000 Hz -0.2 dBmV 41.2 dB 20 0
10 Locked QAM256 26 567000000 Hz -0.3 dBmV 41.0 dB 13 0
11 Locked QAM256 27 573000000 Hz 0.0 dBmV 41.1 dB 14 0
12 Locked QAM256 28 579000000 Hz 0.1 dBmV 41.3 dB 16 0
13 Locked QAM256 29 585000000 Hz 0.2 dBmV 41.3 dB 17 0
14 Locked QAM256 30 591000000 Hz 0.0 dBmV 41.1 dB 16 0
15 Locked QAM256 31 597000000 Hz 0.4 dBmV 41.2 dB 17 0
16 Locked QAM256 32 603000000 Hz 0.6 dBmV 40.9 dB 22 0
17 Locked QAM256 33 609000000 Hz 1.1 dBmV 41.2 dB 18 0
18 Locked QAM256 34 615000000 Hz 1.6 dBmV 41.4 dB 32 0
19 Locked QAM256 35 621000000 Hz 1.8 dBmV 41.5 dB 33 0
20 Locked QAM256 36 627000000 Hz 1.7 dBmV 41.2 dB 21 0
21 Locked QAM256 37 633000000 Hz 1.3 dBmV 40.8 dB 29 0
22 Locked QAM256 38 639000000 Hz 1.1 dBmV 41.1 dB 34 0
23 Locked QAM256 39 645000000 Hz 0.9 dBmV 41.2 dB 13 0
24 Locked QAM256 40 651000000 Hz 0.4 dBmV 40.9 dB 30 0
25 Locked QAM256 41 657000000 Hz -0.1 dBmV 40.7 dB 31 0
26 Locked QAM256 42 663000000 Hz -0.4 dBmV 40.6 dB 41 0
27 Locked QAM256 43 669000000 Hz -0.2 dBmV 40.7 dB 32 0
28 Locked QAM256 44 675000000 Hz 0.3 dBmV 40.9 dB 28 0
29 Locked QAM256 45 681000000 Hz 0.8 dBmV 40.7 dB 32 0
30 Locked QAM256 46 687000000 Hz 1.7 dBmV 41.2 dB 23 0
31 Locked QAM256 47 693000000 Hz 2.7 dBmV 41.5 dB 17 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

 

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 4 5120 Ksym/sec 36700000 Hz 39.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 17300000 Hz 40.8 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 23700000 Hz 40.3 dBmV
4 Locked ATDMA 3 5120 Ksym/sec 30300000 Hz 40.0 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV

 

Netgear community suggested that it may be due to a splitter or other signal quality issues.  Any advice/help would be appreciated.  @ComcastMorgan 

Highlighted
Regular Visitor

Re: Daily partial WAN disconnects

Can't help you solve the problem but I can confirm that I have the same issue, and maybe provide more insight. . I'm using a Netgear Nighthawk CM1200 modem latest firmware. Sometimes it requires rebooting both the modem and WiFi router, and sometimes it requires doing a reset of the CM1200. Behavior only just started in the past 7 days or so. Here's a copy of the log around the event (my CM-MAC is blanked out with Xs, CMTS-MAC blanked out with Y's,- if the MAC is listed as 00:00:00:00:00:00 then that's the way it shows up)

 

Mon Jun 22 16:23:11 2020 — Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;

 

Mon Jun 22 16:22:45 2020 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;

 

Mon Jun 22 16:19:48 2020 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;

 

Mon Jun 22 16:19:43 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;

 

Time Not Established — Notice (6)

Honoring MDD; IP provisioning mode = IPv6

 

Time Not Established — Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

 

Time Not Established — Warning (5)

Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;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=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Time Not Established — Warning (5)

Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;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=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Highlighted
Frequent Visitor

Re: Daily partial WAN disconnects

Here's my event log... more than 3 weeks of regular disconnects

 

Time Priority Description
2020-06-22, 14:48:48 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-19, 11:11:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-16, 13:28:52 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-15, 15:08:49 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-14, 07:55:02 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-13, 22:27:18 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-11, 13:03:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-09, 15:55:35 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-07, 23:45:38 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-06-07, 12:49:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-05-30, 14:50:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2020-05-30, 14:46:05 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;
Highlighted
Frequent Visitor

Re: Daily partial WAN disconnects

Another one today...

 

2020-06-25, 11:19:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=yy:yy:yy:yy:yy:yy;CM-QOS=1.1;CM-VER=3.1;

 

Any suggestions from Comcast folks? 

Highlighted
Frequent Visitor

Re: Daily partial WAN disconnects

@ComcastMorgan  @ComcastIdris @ComcastJK @ComcastZach @ComcastSeanR   .... looking for a friend.  

Highlighted
New Poster

Re: Daily partial WAN disconnects

Seems I have a similar/identical issue, despite tier 1 support telling me everything is fine...

 

https://forums.xfinity.com/t5/Your-Home-Network/Constant-Network-Drops/td-p/3348322 

Highlighted
Frequent Visitor

Re: Daily partial WAN disconnects

Quite frustrating indeed.   Looking for a friend, Comast.  

Highlighted
New Poster

Re: Daily partial WAN disconnects

I'm having the same issues (using Netgear C7000v2, though). T-3, T-4, and MDD timeouts everyday. All support staff has done is ignore me (phone, chat, and social media). I think I'm just going to call AT&T later, and switch services. I've already confirmed that my setup on my side of the drop is in perfect condition.

Highlighted
New Poster

Re: Daily partial WAN disconnects

Exactly the same  situation for me.  I have a CM1200 and started getting drops about 3 weeks ago.  I have to reboot the modemabout 3 times per day.  Here is my connection status.

 

 


Cable Connection

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 0

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 507000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 5 507000000 Hz 4.8 dBmV 41.4 dB 0 0
2 Locked QAM256 1 477000000 Hz 4.9 dBmV 41.7 dB 0 0
3 Locked QAM256 2 483000000 Hz 4.6 dBmV 41.6 dB 0 0
4 Locked QAM256 3 489000000 Hz 4.7 dBmV 41.5 dB 0 0
5 Locked QAM256 4 495000000 Hz 4.7 dBmV 41.3 dB 0 0
6 Locked QAM256 6 513000000 Hz 5 dBmV 41.5 dB 0 0
7 Locked QAM256 7 519000000 Hz 5 dBmV 41.4 dB 0 0
8 Locked QAM256 8 525000000 Hz 5 dBmV 41.4 dB 2 0
9 Locked QAM256 9 531000000 Hz 4.9 dBmV 41.3 dB 0 0
10 Locked QAM256 10 537000000 Hz 4.9 dBmV 41.3 dB 0 0
11 Locked QAM256 11 543000000 Hz 4.6 dBmV 41.1 dB 0 0
12 Locked QAM256 12 549000000 Hz 4.4 dBmV 41 dB 0 0
13 Locked QAM256 13 555000000 Hz 4.7 dBmV 41.1 dB 0 0
14 Locked QAM256 14 561000000 Hz 4.8 dBmV 41.1 dB 0 0
15 Locked QAM256 15 567000000 Hz 4.9 dBmV 41 dB 1 0
16 Locked QAM256 16 573000000 Hz 4.6 dBmV 41 dB 1 0
17 Locked QAM256 17 579000000 Hz 4.9 dBmV 41.1 dB 1 0
18 Locked QAM256 18 585000000 Hz 4.8 dBmV 41.1 dB 2 0
19 Locked QAM256 19 591000000 Hz 4.8 dBmV 41 dB 2 0
20 Locked QAM256 33 453000000 Hz 4.6 dBmV 41.8 dB 1 0
21 Locked QAM256 34 459000000 Hz 4.6 dBmV 41.6 dB 0 0
22 Locked QAM256 35 465000000 Hz 4.7 dBmV 41.5 dB 0 0
23 Locked QAM256 36 471000000 Hz 4.7 dBmV 41.6 dB 0 0
24 Locked QAM256 38 423000000 Hz 4.8 dBmV 42 dB 0 0
25 Locked QAM256 39 435000000 Hz 4.8 dBmV 42 dB 0 0
26 Locked QAM256 40 441000000 Hz 4.5 dBmV 41.9 dB 0 0
27 Locked QAM256 41 447000000 Hz 4.5 dBmV 41.8 dB 0 0
28 Locked QAM256 42 399000000 Hz 4.9 dBmV 42.2 dB 0 0
29 Locked QAM256 43 405000000 Hz 4.9 dBmV 42.2 dB 0 0
30 Locked QAM256 44 411000000 Hz 4.9 dBmV 42.1 dB 0 0
31 Locked QAM256 45 417000000 Hz 4.8 dBmV 42 dB 0 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 48.5 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 49.3 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 48.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 48.5 dBmV
5 Locked ATDMA 5 1280 Ksym/sec 39800000 Hz 47.3 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

Downstream OFDM Channels
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 ,1 ,2 ,3 37 690000000 Hz 5.2 dBmV 40.6 dB 1228 ~ 2867 106010121 44940424 0
2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0

Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV

Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power

Current System Time:Wed Jul 01 15:50:46 2020
System Up Time:03:43:48

Highlighted
New Poster

Re: Daily partial WAN disconnects

Had another disconnection, and was able to collect my own data, right afterwards:

https://forums.xfinity.com/t5/Your-Home-Network/Intermittent-T-3-T-4-and-MDD-Timeouts-Please-fix-our...

Highlighted
Frequent Visitor

Re: Daily partial WAN disconnects

Update:  Disconnects mysteriously disappeared and have stayed away for ~3 weeks.   Hoping it keeps up.