Spectator

Speed Dropping Drastically During Peak Hours

I read a few posts that seem similar to mine, but thought I would get some insight before calling TWC/Spectrum. I would much rather find and fix the issue myself.

 

I have come home twice in the last week to find no connection to the internet. That usually happens to me about 2-3 times a year. I simple reboot of the modem does the trick, but I picked up on a trend a couple of days ago I had not noticed before. My internet in the evening (7-10pm) seemed sluggish. Especially from 9-10pm. I have been running periodic speed tests and noticed that during the morning or early evening I am getting my usual around 68-70Mbps. I pay for 60 so I am usually estatic and have not had any issues. Now it seems that starting around 6pm that starts to trend down to the 30s and eventually dips into single digits around 9pm and stays there until after 10. I never stay up late enough to see when it recovers, but at 6am the next day it's back around 68-70.

 

I checked connections, disconnected all items except those being used for testing, bypassed my WIFI router, checked for tight connections in the attic, etc..., but then went into the modem and sure enough found an error log starting about the time I can remember having an outage. Some of it I know is from me playing with it. Wondered if any of this is off or what it might mean? I live in a new subdivision, but service has been built out for about 2 years. Modem is a Netgear CM400. Thanks in advance.

 

<tabindex=-1>Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel723000000 HzLocked
Connectivity StateOkOperational
Boot State----
Configuration File----
SecurityEnabledBPI+

<tabindex=-1>Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables
1LockedQAM 2569723000000 Hz-0.1 dBmV34.3 dB1883156134
2LockedQAM 25610729000000 Hz-0.7 dBmV34.3 dB13251971
3LockedQAM 25611735000000 Hz-1.5 dBmV34.0 dB18762286
4LockedQAM 25613747000000 Hz0.1 dBmV34.4 dB41983190
5LockedQAM 25614753000000 Hz-0.8 dBmV34.6 dB42463214
6LockedQAM 25615759000000 Hz-0.1 dBmV34.4 dB53692835
7LockedQAM 25616765000000 Hz0.9 dBmV34.7 dB42942313
8LockedQAM 25617771000000 Hz0.5 dBmV34.3 dB47141798

<tabindex=-1>Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedTDMA372560 Ksym/sec19400000 Hz43.5 dBmV
2LockedATDMA385120 Ksym/sec24200000 Hz44.8 dBmV
3LockedATDMA395120 Ksym/sec30600000 Hz46.0 dBmV
4LockedATDMA405120 Ksym/sec37000000 Hz47.8 dBmV

Current System Time: Thu Oct 12 21:08:13 2017
 
TimePriorityDescription
Oct 4 07:06:24 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:06:24 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:06:24 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:06:24 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:06:24 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:06:24 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:06:24 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:06:24 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:07:12 2017Critical (3)Ranging Request Retries exhausted
Oct 4 07:07:12 2017Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted
Oct 4 07:07:15 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:09:38 2017Critical (3)Ranging Request Retries exhausted
Oct 4 07:09:38 2017Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted
Oct 4 07:09:47 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:12:59 2017Critical (3)Ranging Request Retries exhausted
Oct 4 07:12:59 2017Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted
Oct 4 07:13:11 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 07:13:59 2017Critical (3)Ranging Request Retries exhausted
Oct 4 07:13:59 2017Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted
Oct 4 07:14:02 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 12:03:11 2017Warning (5)TEK Invalid - Invalid Key Sequence Number
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Oct 4 16:00:29 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Oct 5 10:48:42 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 6 11:29:02 2017Critical (3)No Ranging Response received - T3 time-out
Oct 6 11:29:51 2017Warning (5)Lost MDD Timeout
Oct 6 11:30:02 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Oct 6 11:30:29 2017Critical (3)No Ranging Response received - T3 time-out
Oct 6 11:30:47 2017Warning (5)Lost MDD Timeout
Oct 6 11:30:54 2017Critical (3)No Ranging Response received - T3 time-out
Oct 6 11:31:06 2017Warning (5)Lost MDD Timeout
Oct 8 14:46:52 2017Error (4)DBC-ACK not received
Oct 8 14:46:56 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out
Oct 8 14:47:45 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Oct 8 14:48:21 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Oct 8 19:39:52 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Oct 8 19:46:15 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Oct 12 10:07:01 2017Warning (5)Lost MDD Timeout
Oct 12 20:39:55 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Oct 12 20:47:55 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 12 20:48:01 2017Warning (5)Lost MDD Timeout
Oct 12 20:48:03 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Oct 12 20:48:33 2017Critical (3)No Ranging Response received - T3 time-out
Oct 12 20:48:42 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 12 20:49:03 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
 
 
14 REPLIES
Established Sharer

Re: Speed Dropping Drastically During Peak Hours

Do you have any sort of cloud backups, scheduled updates, antivirus, etc. running during the times of the slowdowns?

Spectator

Re: Speed Dropping Drastically During Peak Hours

I thought about that too, but no. I bypassed the router and connected straight to my ATV4K and then did it again with my Mac with a different CAT6. Same results either way. Maybe it has been going on for a while and I just didnt notice it until I started dabbling in 4K 2 weeks ago. 

Expert

Re: Speed Dropping Drastically During Peak Hours

You have serious noise issues. please describe what's between the pole and the modem...

Is something corroded or loose?

 

Spectator

Re: Speed Dropping Drastically During Peak Hours

Service was bored underground. And there is a pedestal between each house. The cable is ran underground from there 30’ to the house and is terminated at a grounding post. From there it runs up to the attic to a TWC splitter. Only one cable is connected on the Out and that goes down the wall to the wall outlet where the modem connects. I checked all the connections and they are tight. Ground wire is properly installed. Unless something failed I’m not sure what else it could be on my end.
Expert

Re: Speed Dropping Drastically During Peak Hours

there should not be a splitter if you're internet only... Replace it with an "F" splice

repost the level page.. 

Spectator

Re: Speed Dropping Drastically During Peak Hours

Thank you again for the assistance. Here you go. Did not seem to help, at least running a speed test. Looks like about 9pm it just hits a wall. I tested about 8:30 and was getting mid 40s. Not upper 60s, but good enough. At 9pm and just now I am down to 8-12. It spikes into the upper 30s and then drops and levels out at 8-12 right now. I also took the wall plate off and tightened the connection behind. It was hand tight, but solid. Tried wiggling the cable too during the test to see if it was a badly made up head. Just throwing darts....lol. 

 

<tabindex=-1>Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel735000000 HzLocked
Connectivity StateOkOperational
Boot State----
Configuration File----
SecurityEnabledBPI+

<tabindex=-1>Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables
1LockedQAM 2569723000000 Hz8.4 dBmV37.0 dB01381
2LockedQAM 25611735000000 Hz7.0 dBmV36.8 dB441482
3LockedQAM 25612741000000 Hz8.2 dBmV37.0 dB11351
4LockedQAM 25613747000000 Hz8.4 dBmV36.8 dB01391
5LockedQAM 25614753000000 Hz7.2 dBmV37.3 dB171482
6LockedQAM 25615759000000 Hz7.7 dBmV37.0 dB411458
7LockedQAM 25616765000000 Hz8.7 dBmV37.9 dB191561
8LockedQAM 25617771000000 Hz8.3 dBmV37.3 dB191563

<tabindex=-1>Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedTDMA372560 Ksym/sec19400000 Hz37.0 dBmV
2LockedATDMA385120 Ksym/sec24200000 Hz38.3 dBmV
3LockedATDMA395120 Ksym/sec30600000 Hz39.5 dBmV
4LockedATDMA405120 Ksym/sec37000000 Hz41.0 dBmV

Current System Time: Fri Oct 13 20:25:28 2017
 
 

 

TimePriorityDescription
Oct 4 07:13:59 2017Critical (3)Ranging Request Retries exhausted
Oct 4 07:13:59 2017Critical (3)Ranging Request Retries exhausted
Oct 4 07:13:59 2017Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted
Oct 4 07:14:02 2017Critical (3)No Ranging Response received - T3 time-out
Oct 4 12:03:11 2017Warning (5)TEK Invalid - Invalid Key Sequence Number
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Oct 4 16:00:29 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Oct 5 10:48:42 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 6 11:29:02 2017Critical (3)No Ranging Response received - T3 time-out
Oct 6 11:29:51 2017Warning (5)Lost MDD Timeout
Oct 6 11:30:02 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Oct 6 11:30:29 2017Critical (3)No Ranging Response received - T3 time-out
Oct 6 11:30:47 2017Warning (5)Lost MDD Timeout
Oct 6 11:30:54 2017Critical (3)No Ranging Response received - T3 time-out
Oct 6 11:31:06 2017Warning (5)Lost MDD Timeout
Oct 8 14:46:52 2017Error (4)DBC-ACK not received
Oct 8 14:46:56 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out
Oct 8 14:47:45 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Oct 8 14:48:21 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Oct 8 19:39:52 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Oct 8 19:46:15 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Oct 12 10:07:01 2017Warning (5)Lost MDD Timeout
Oct 12 20:39:55 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Oct 12 20:47:55 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 12 20:48:01 2017Warning (5)Lost MDD Timeout
Oct 12 20:48:03 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Oct 12 20:48:33 2017Critical (3)No Ranging Response received - T3 time-out
Oct 12 20:48:42 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 12 20:49:03 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Oct 13 09:56:42 2017Critical (3)No Ranging Response received - T3 time-out
Oct 13 20:13:10 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 13 20:13:16 2017Warning (5)Lost MDD Timeout
Oct 13 20:13:26 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Oct 13 20:13:34 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 13 20:13:34 2017Critical (3)No Ranging Response received - T3 time-out
Oct 13 20:13:39 2017Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Oct 13 20:13:43 2017Critical (3)No Ranging Response received - T3 time-out
Oct 13 20:13:45 2017Warning (5)Lost MDD Timeout
Oct 13 20:23:56 2017Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
 
 
Spectator

Re: Speed Dropping Drastically During Peak Hours

Now it is ranging back to 30-45. Nothing I did on my end. It's a new neighborhood and they are about 10 houses into building a second new subdivision next door too. Can it just be growing pains of number of users? Although if they do it like this one, none of those houses have service yet.
Spectator

Re: Speed Dropping Drastically During Peak Hours

Here is current while it seems to be working at about 75% speed.

 

<tabindex=-1>Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables
1LockedQAM 2569723000000 Hz8.5 dBmV37.0 dB01381
2LockedQAM 25611735000000 Hz7.1 dBmV36.8 dB441482
3LockedQAM 25612741000000 Hz8.2 dBmV37.0 dB11351
4LockedQAM 25613747000000 Hz8.5 dBmV36.8 dB01391
5LockedQAM 25614753000000 Hz7.3 dBmV37.3 dB171482
6LockedQAM 25615759000000 Hz7.8 dBmV37.0 dB411458
7LockedQAM 25616765000000 Hz8.9 dBmV37.9 dB191561
8LockedQAM 25617771000000 Hz8.3 dBmV37.3 dB281563

<tabindex=-1>Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedTDMA372560 Ksym/sec19400000 Hz37.0 dBmV
2LockedATDMA385120 Ksym/sec24200000 Hz38.3 dBmV
3LockedATDMA395120 Ksym/sec30600000 Hz39.5 dBmV
4LockedATDMA405120 Ksym/sec37000000 Hz41.0 dBmV

Current System Time: Fri Oct 13 20:34:26 2017
Expert

Re: Speed Dropping Drastically During Peak Hours

corrected and uncorrecteds didn't increase so it appears it's either one of your devices hoarding bandwidth or the entire node is slowing down. 

 Make sure you don't have cloud, sync, onedrive or win 10 peer upgrade running on any of your devices...