U

Monday, September 2nd, 2024 5:40 PM

Internet drops multiple times everyday

Modem is a Arris Surfboard S33. I moved from a house to a apartment and now everyday my internet keep dropping constantly. I only have internet, nothing else so i don't know if there is outage, elt. Only thing I can do is post the logs a hope someone can help me out?
2/9/2024
06:02:36
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:36
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:36
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:38
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:43
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:43
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:46
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:46
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:48
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:48
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:48
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:49
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:52
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:52
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:54
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:02:55
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:03:02
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:03:03
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:03:05
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:03:10
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:03:11
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:03:11
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:18:55
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:18:55
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:18:55
3 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:18:56
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:18:56
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:18:56
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:18:56
3 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:07
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:08
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:10
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:20
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:20
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:20
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:25
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:31
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:32
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:32
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:32
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:36
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:46
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:51
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:52
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:53
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:19:58
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:20:00
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:20:02
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:20:03
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:20:04
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:20:10
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:20:14
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:20:48
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:21:15
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:21:44
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:23:48
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:23:48
3 Ranging Request Retries exhausted;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:23:48
3 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:23:51
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:23:51
3 Ranging Request Retries exhausted;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:23:51
3 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:24:05
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:24:10
3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:24:17
3 CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-9, 42MHz.
2/9/2024
06:24:31
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
2/9/2024
06:24:31
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
2/9/2024
06:24:31
3 CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
2/9/2024
06:37:41
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:41:18
3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:41:22
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:41:26
3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:41:40
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:41:41
3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
06:41:47
3 CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-9, 42MHz.
2/9/2024
06:42:01
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
2/9/2024
06:42:01
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
2/9/2024
06:42:01
3 CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
31/12/1969
19:00:16
3 CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz.
31/12/1969
19:00:20
3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:21
3 CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-9, 42MHz.
31/12/1969
19:00:25
6 Honoring MDD; IP provisioning mode = IPv6
31/12/1969
19:00:37
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
31/12/1969
19:00:37
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
31/12/1969
19:00:37
3 CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
2/9/2024
09:02:59
6 DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
09:02:59
3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
09:04:38
3 No Ranging Response received - T3 time-out;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
09:05:25
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Redacted];CMTS-MAC=[Redacted];CM-QOS=1.1;CM-VER=3.1;
2/9/2024
09:05:25
5

Dynamic Range Window violation

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
5 Locked QAM256 501000000 Hz 0 dBmV 41 dB 260 427
1 Locked QAM256 477000000 Hz 0 dBmV 41 dB 167 254
2 Locked QAM256 483000000 Hz 0 dBmV 42 dB 256 355
3 Locked QAM256 489000000 Hz 1 dBmV 42 dB 203 223
4 Locked QAM256 495000000 Hz -1 dBmV 41 dB 217 418
6 Locked QAM256 507000000 Hz 1 dBmV 42 dB 115 209
7 Locked QAM256 513000000 Hz -2 dBmV 41 dB 236 520
8 Locked QAM256 519000000 Hz 0 dBmV 42 dB 160 204
9 Locked QAM256 525000000 Hz 0 dBmV 41 dB 147 180
10 Locked QAM256 531000000 Hz -1 dBmV 41 dB 170 349
11 Locked QAM256 537000000 Hz 0 dBmV 42 dB 98 186
12 Locked QAM256 543000000 Hz 0 dBmV 41 dB 130 148
13 Locked QAM256 555000000 Hz 0 dBmV 41 dB 156 133
14 Locked QAM256 561000000 Hz 0 dBmV 41 dB 137 236
15 Locked QAM256 567000000 Hz 0 dBmV 41 dB 93 152
16 Locked QAM256 573000000 Hz 0 dBmV 41 dB 125 185
17 Locked QAM256 579000000 Hz 0 dBmV 41 dB 153 157
18 Locked QAM256 585000000 Hz 0 dBmV 41 dB 140 143
19 Locked QAM256 591000000 Hz -1 dBmV 41 dB 178 395
33 Locked OFDM PLC 690000000 Hz 1 dBmV 40 dB 39504040 4468
34 Locked QAM256 453000000 Hz 0 dBmV 42 dB 126 138
35 Locked QAM256 459000000 Hz 0 dBmV 42 dB 139 173
36 Locked QAM256 465000000 Hz -1 dBmV 41 dB 196 395
37 Locked QAM256 471000000 Hz 1 dBmV 42 dB 125 166
38 Locked QAM256 423000000 Hz 0 dBmV 41 dB 142 189
39 Locked QAM256 429000000 Hz 0 dBmV 42 dB 164 262
40 Locked QAM256 435000000 Hz -1 dBmV 41 dB 141 174
41 Locked QAM256 441000000 Hz 0 dBmV 42 dB 253 230
42 Locked QAM256 399000000 Hz -1 dBmV 41 dB 158 159
43 Locked QAM256 405000000 Hz -1 dBmV 41 dB 259 210
44 Locked QAM256 411000000 Hz 2 dBmV 42 dB 134 238
45 Locked QAM256 417000000 Hz -1 dBmV 41 dB 101 203
Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
5 Locked SC-QAM 35600000 Hz 6400000 48.0 dBmV
6 Locked SC-QAM 29200000 Hz 6400000 46.8 dBmV
7 Locked SC-QAM 22800000 Hz 6400000 48.8 dBmV
8 Locked SC-QAM 16400000 Hz 6400000 46.0 dBmV
10 Locked SC-QAM 39600000 Hz 1600000 49.0 dBmV


Expert

 • 

107.1K Messages

3 months ago

This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless. The upstream power is on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, 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 !

Official Employee

 • 

1.2K Messages

3 months ago

@user_xsm3vp Hi there! Thank you so much for reaching out to us for help with the internet connections dropping. I'm sorry your have been experiencing this issue, I know how impactful this can be on our everyday lives. We will help find the right solution! 

@EG Thanks for your input on this and guidance on troubleshooting the wiring. 

@user_xsm3vp It's possible that eliminating a splitter (if any) and checking the connections for being secure and undamaged may help out with correcting the signals to correct levels. If the trouble continues, we can set up a repair appointment to have our awesome technicians work on any needed repairs. Simply send us a direct message with your name and service address.

To send a direct message, please click on the chat icon in the top-right corner of the screen, and select "Xfinity Support" to initiate a live chat. 
Click "Sign In" if necessary
Click the "direct messaging" icon or https://comca.st/3J0ir1l
Click the "New message" (pencil and paper) icon
Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "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

forum icon

New to the Community?

Start Here