Xfinity plant
Xfinity globe
Community Forum

Internet drops throughout the day

Frequent Visitor

Internet drops throughout the day

Backstory

 

I've had xfinity internet for just over a month. The speeds have been good, but it has been unreliable to say the least. I started off with a TP Link Archer 500 but quickly found out that it will not work for voice applications. So I purchased one of the xfinity approved retail equipment for internet + voice... Netgear C7100v. However, just like the Archer 500 the connection is not very stable and it goes down 3-5 times everyday. 

 

I'm not sure exactly what the problem so I hope someone here could be of help.

 

Logs:

 

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
Procedure Status Comment
Acquire Downstream Channel 609000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK ------------
Security Enable BPI+

<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 16 609000000 Hz 9.3 dBmV 39.8 dB 89 55
2 Locked QAM256 1 513000000 Hz 9.4 dBmV 40.2 dB 71 119
3 Locked QAM256 2 519000000 Hz 9.6 dBmV 40.2 dB 143 79
4 Locked QAM256 3 525000000 Hz 9.3 dBmV 40.1 dB 176 68
5 Locked QAM256 4 531000000 Hz 9.0 dBmV 40.0 dB 181 41
6 Locked QAM256 5 537000000 Hz 8.9 dBmV 40.0 dB 169 102
7 Locked QAM256 6 543000000 Hz 9.0 dBmV 40.0 dB 164 95
8 Locked QAM256 7 555000000 Hz 9.2 dBmV 40.0 dB 127 40
9 Locked QAM256 8 561000000 Hz 9.1 dBmV 39.7 dB 96 96
10 Locked QAM256 9 567000000 Hz 8.8 dBmV 39.8 dB 121 39
11 Locked QAM256 10 573000000 Hz 8.9 dBmV 39.8 dB 94 89
12 Locked QAM256 11 579000000 Hz 9.2 dBmV 39.9 dB 142 85
13 Locked QAM256 12 585000000 Hz 9.3 dBmV 39.9 dB 98 63
14 Locked QAM256 13 591000000 Hz 9.2 dBmV 39.9 dB 100 49
15 Locked QAM256 14 597000000 Hz 9.0 dBmV 39.7 dB 96 66
16 Locked QAM256 15 603000000 Hz 9.1 dBmV 39.7 dB 72 67
17 Locked QAM256 17 615000000 Hz 8.9 dBmV 40.3 dB 0 0
18 Locked QAM256 18 621000000 Hz 8.8 dBmV 40.2 dB 0 0
19 Locked QAM256 19 627000000 Hz 8.5 dBmV 39.9 dB 0 0
20 Locked QAM256 20 633000000 Hz 8.2 dBmV 39.5 dB 0 0
21 Locked QAM256 21 639000000 Hz 8.6 dBmV 39.9 dB 0 0
22 Locked QAM256 22 645000000 Hz 8.5 dBmV 39.8 dB 0 0
23 Locked QAM256 23 651000000 Hz 8.5 dBmV 39.8 dB 0 0
24 Locked QAM256 24 657000000 Hz 8.1 dBmV 39.4 dB 0 0

<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 69 5120 Ksym/sec 35800000 Hz 42.8 dBmV
2 Locked ATDMA 70 5120 Ksym/sec 29400000 Hz 44.0 dBmV
3 Locked ATDMA 71 5120 Ksym/sec 23000000 Hz 44.8 dBmV
4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 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

 

 

 

 
 
 
Time Priority Description
2018-02-04, 19:50:16.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 18:00:37.0 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-02-04, 18:00:15.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 17:55:55.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 17:55:41.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 17:55:41.0 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 17:55:41.0 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 17:43:45.0 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-02-04, 17:43:33.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.0;CM-VER=3.0;
2018-02-04, 17:43:13.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 17:38:52.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 15:55:03.0 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-02-04, 15:54:54.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.0;CM-VER=3.0;
2018-02-04, 15:54:53.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.0;CM-VER=3.0;
2018-02-04, 15:54:33.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 15:50:13.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 15:08:42.0 Warning (5) MDD message timeout;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 15:08:01.0 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-02-04, 15:07:36.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 15:03:12.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 14:26:36.0 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-02-04, 14:26:26.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.0;CM-VER=3.0;
2018-02-04, 14:26:08.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 14:21:42.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 13:43:50.0 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-02-04, 13:43:41.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.0;CM-VER=3.0;
2018-02-04, 13:43:24.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 13:39:03.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 13:34:48.0 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-02-04, 13:34:36.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.0;CM-VER=3.0;
2018-02-04, 13:34:19.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 13:29:59.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 13:29:34.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 13:29:34.0 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 13:29:34.0 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.1;CM-VER=3.0;
2018-02-04, 11:53:39.0 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-02-04, 11:53:27.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:d7:19:b0;CMTS-MAC=00:01:5c:82:e2:62;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT
Time Not Established Notice (6) WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:N/A) - Reason:INIT

 

 

 

System Up Time      2:21:54
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN Link Up 155572 409706 99 63969553 465712472 2:20:20
LAN1 100M/Full 389666 238002 0 405642171 72586839 2:21:54
LAN2 Link Down 2:21:54
LAN3 Link Down 2:21:54
LAN4 Link Down 2:21:54
WLAN 289 M 8963 22102 0 7513302 5345905 2:21:54
WLAN 289 M 17695 18415 0 11493799 3453521 2:21:54
Frequent Visitor

Re: Internet drops throughout the day

The list of reasons why is endless. Long answer short... Get a tech out there and have them check the lines. Your Downstream RX power could be a tad lower btw.
Frequent Visitor

Re: Internet drops throughout the day


@ wrote:
The list of reasons why is endless. Long answer short... Get a tech out there and have them check the lines. Your Downstream RX power could be a tad lower btw.

Thanks for your response,

 

For the momement I think I have solved this issue. I plugged in a 6db attenuator and for the last couple hours I have had no drops, error, logs, and the statistics look more healthier. Hope it continues.

 

This is the stats after 3 hours running...

 

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
Procedure Status Comment
Acquire Downstream Channel 609000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK ------------
Security Enable BPI+

<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 16 609000000 Hz 5.5 dBmV 40.1 dB 0 0
2 Locked QAM256 1 513000000 Hz 5.7 dBmV 40.7 dB 0 0
3 Locked QAM256 2 519000000 Hz 5.9 dBmV 40.9 dB 0 0
4 Locked QAM256 3 525000000 Hz 5.8 dBmV 40.6 dB 0 0
5 Locked QAM256 4 531000000 Hz 5.5 dBmV 40.3 dB 0 0
6 Locked QAM256 5 537000000 Hz 5.3 dBmV 40.3 dB 0 0
7 Locked QAM256 6 543000000 Hz 5.4 dBmV 40.3 dB 0 0
8 Locked QAM256 7 555000000 Hz 5.5 dBmV 40.3 dB 0 0
9 Locked QAM256 8 561000000 Hz 5.4 dBmV 40.1 dB 0 0
10 Locked QAM256 9 567000000 Hz 5.2 dBmV 40.1 dB 0 0
11 Locked QAM256 10 573000000 Hz 5.1 dBmV 40.1 dB 0 0
12 Locked QAM256 11 579000000 Hz 5.4 dBmV 40.2 dB 0 0
13 Locked QAM256 12 585000000 Hz 5.4 dBmV 40.2 dB 0 0
14 Locked QAM256 13 591000000 Hz 5.3 dBmV 40.1 dB 0 0
15 Locked QAM256 14 597000000 Hz 5.1 dBmV 40.0 dB 0 0
16 Locked QAM256 15 603000000 Hz 5.1 dBmV 40.0 dB 0 0
17 Locked QAM256 17 615000000 Hz 4.8 dBmV 40.4 dB 0 0
18 Locked QAM256 18 621000000 Hz 4.8 dBmV 40.4 dB 0 0
19 Locked QAM256 19 627000000 Hz 4.4 dBmV 40.3 dB 0 0
20 Locked QAM256 20 633000000 Hz 4.3 dBmV 39.9 dB 0 0
21 Locked QAM256 21 639000000 Hz 4.6 dBmV 40.3 dB 0 0
22 Locked QAM256 22 645000000 Hz 4.5 dBmV 40.3 dB 0 0
23 Locked QAM256 23 651000000 Hz 4.4 dBmV 40.0 dB 0 0
24 Locked QAM256 24 657000000 Hz 3.9 dBmV 39.9 dB 0 0

<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 69 5120 Ksym/sec 35800000 Hz 44.8 dBmV
2 Locked ATDMA 70 5120 Ksym/sec 29400000 Hz 45.8 dBmV
3 Locked ATDMA 71 5120 Ksym/sec 23000000 Hz 47.3 dBmV
4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 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
New Poster

Re: Internet drops throughout the day

My event log looks similar to yours.  Where in the line did you connect the attenuator (connection outside or the coax going to the modem)?

 

m.

Frequent Visitor

Re: Internet drops throughout the day

You’re welcome. I’d still have a tech come out to check the lines for any ingress. Ingress is one of a few things that causes random drops in connection.
Frequent Visitor

Re: Internet drops throughout the day


@

@ wrote:

My event log looks similar to yours.  Where in the line did you connect the attenuator (connection outside or the coax going to the modem)?

 

m.


I just connected it at the terminal end of the coax going into the modem.