Observer

San Diego Intermittent Slow Speeds

Hi,

 

I've been having an issue where my speeds go from great to 2-5 Mbps.  This started with the MAXX rollout about a year ago, and have continued since we were issued an upgraded modem as well as a replacement, newer modem.  Usually things work fine for a day or so, then my 300Mbps download drops considerablly until we do a reboot.  Whats strange is that regardless of the download speeds, we consistently see reports of 25 Mbps uploads.  I've had multiple  service calls, and the best i get is a shrug saying its a software issue with either Spectrum or Arris.   The last few months the issue seems to have improved, but as of the last week, its become an issue multiple times per day.

 

We live in 90237, single family home, and all the cable wiring was replaced about 2 years ago.

The modem is an Arris MTA

I have wireless turned off, but use the Arris for DHCP.  We use an Apple Airport Extreme station that is running at 1000Mbps to the Arris.

The Modem line has three splits, though it was no better than when we had 2.

 

 

Status Page:

 

Downstream 
 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 17543.00 MHz-9.70 dBmV38.61 dB256QAM435114567239516513
Downstream 24525.00 MHz------------------------
Downstream 310561.00 MHz-9.90 dBmV38.61 dB256QAM12113040068033741
Downstream 411567.00 MHz-9.80 dBmV38.61 dB256QAM81929525109013189
Downstream 512573.00 MHz-9.60 dBmV38.98 dB256QAM1012080617614157
Downstream 613579.00 MHz-10.00 dBmV38.61 dB256QAM93147795194417593
Downstream 714585.00 MHz-10.20 dBmV38.61 dB256QAM10603674528823394
Downstream 815591.00 MHz-10.60 dBmV38.61 dB256QAM8879499968020994
Downstream 916597.00 MHz------------------------
Downstream 1017603.00 MHz-10.70 dBmV38.61 dB256QAM8642654366224073
Downstream 1118609.00 MHz-11.00 dBmV38.98 dB256QAM79883300255816825
Downstream 1219615.00 MHz-11.50 dBmV37.64 dB256QAM1131703952251021742
Downstream 1320621.00 MHz-12.30 dBmV37.64 dB256QAM111089069338517748
Downstream 1421627.00 MHz-13.90 dBmV35.78 dB256QAM121103247353243447
Downstream 1523639.00 MHz-16.70 dBmV33.96 dB256QAM98965411326727287
Downstream 1624645.00 MHz-14.10 dBmV36.39 dB256QAM100063219283721315
Reset FEC Counters
Upstream 
 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 12037.00 MHz48.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 21930.60 MHz47.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 31823.30 MHz46.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 41718.50 MHz45.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 Status
System Uptime: 1 d: 0 h: 23 m
Computers Detected:staticCPE(2), dynamicCPE(0)
CM Status:Telephony-Reg Complete
Time and Date:Mon 2017-04-17 16:46:45

 Interface Parameters 
Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledDown-----54:65Smiley Very HappyE:29:92:01
LAN Port 2EnabledDown-----54:65Smiley Very HappyE:29:92:01
LAN Port 3EnabledUp100(Full)54:65Smiley Very HappyE:29:92:01
LAN Port 4EnabledUp1000(Full)54:65Smiley Very HappyE:29:92:01
CABLEEnabledUp-----54:65Smiley Very HappyE:29:92:02
MTAPassUp-----54:65Smiley Very HappyE:29:92:03

 

 
12 REPLIES
Expert

Re: San Diego Intermittent Slow Speeds

You have excessive splitter loss and probable broadcast TV ingress/

The modem must be on the first 2 way splitter after the outside grounding block for a start.

 It's not going to work with levels bel;ow -8dBmv no matter what TWC phone support says or claims they reset. It needs a tech out to clean up the coaxial network.

 

Observer

Re: San Diego Intermittent Slow Speeds

Hi,

 

Thanks for the help - i moved the adapter and my signal looks much better, though I still have the issue after about 12 hours of happy browsing:

 

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 124645.00 MHz3.20 dBmV40.95 dB256QAM7845759953211064
Downstream 21507.00 MHz3.60 dBmV40.37 dB256QAM4890621582582890
Downstream 32513.00 MHz3.90 dBmV40.95 dB256QAM4327396551771653
Downstream 43519.00 MHz4.10 dBmV40.37 dB256QAM43352184831313830
Downstream 54525.00 MHz4.30 dBmV40.95 dB256QAM42604715720812061
Downstream 65531.00 MHz4.20 dBmV40.95 dB256QAM42013887179517806
Downstream 76537.00 MHz4.10 dBmV40.95 dB256QAM42899080941689
Downstream 87543.00 MHz3.90 dBmV40.95 dB256QAM4350647194949714
Downstream 98549.00 MHz3.90 dBmV40.37 dB256QAM4237740432596767
Downstream 109555.00 MHz3.80 dBmV40.95 dB256QAM4048610361183752
Downstream 1110561.00 MHz3.20 dBmV40.37 dB256QAM42068152114699
Downstream 1211567.00 MHz1.70 dBmV38.61 dB256QAM39656845461625069
Downstream 1312573.00 MHz-0.40 dBmV38.61 dB256QAM4407216194954251
Downstream 1417603.00 MHz2.90 dBmV40.37 dB256QAM4366010693131461
Downstream 1518609.00 MHz2.90 dBmV40.95 dB256QAM50559544121649334
Downstream 1623639.00 MHz2.90 dBmV40.37 dB256QAM4815212724115888
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 12037.00 MHz38.50 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 21930.60 MHz38.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 31823.30 MHz36.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 41718.50 MHz35.75 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 Status
System Uptime:0 d: 17 h: 48 m
Computers Detected:staticCPE(2), dynamicCPE(0)
CM Status:Telephony-Reg Complete
Time and Date:Tue 2017-04-18 18:35:23

 

 Interface Parameters
Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledUp1000(Full)54:65Smiley Very HappyE:29:92:01
LAN Port 2EnabledUp1000(Full)54:65Smiley Very HappyE:29:92:01
LAN Port 3EnabledDown-----54:65Smiley Very HappyE:29:92:01
LAN Port 4EnabledDown-----54:65Smiley Very HappyE:29:92:01
CABLEEnabledUp-----54:65Smiley Very HappyE:29:92:02
MTAPassUp-----54:65Smiley Very HappyE:29:92:03

 

DOCSIS(CM) Events

Date TimeEvent IDEvent LevelDescription
4/18/2017 17:41840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:41840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:41840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:41840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:41840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51820002003No Ranging Response received - T3 time-out;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/18/2017 17:51840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;

 PacketCable(MTA) Events

Date TimeEvent IDDescription
4/12/2017 2:3126MTA PROV: Successful!
4/12/2017 2:313Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/14/2017 12:584000960006New time has been retrieved from ToD server.
4/14/2017 14:3614Power Supply Telemetry Log - BATTERY MISSING
4/14/2017 14:3616MTA TFTP: Successful
4/14/2017 14:3626MTA PROV: Successful!
4/14/2017 14:363Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/14/2017 16:453Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
4/14/2017 16:4614Power Supply Telemetry Log - BATTERY MISSING
4/14/2017 16:4616MTA TFTP: Successful
4/14/2017 16:4626MTA PROV: Successful!
4/14/2017 16:463Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/15/2017 0:4814Power Supply Telemetry Log - BATTERY MISSING
4/15/2017 0:4816MTA TFTP: Successful
4/15/2017 0:4826MTA PROV: Successful!
4/15/2017 0:483Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/16/2017 16:2514Power Supply Telemetry Log - BATTERY MISSING
4/16/2017 16:2516MTA TFTP: Successful
4/16/2017 16:2526MTA PROV: Successful!
4/16/2017 16:253Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/17/2017 16:5314Power Supply Telemetry Log - BATTERY MISSING
4/17/2017 16:5316MTA TFTP: Successful
4/17/2017 16:5326MTA PROV: Successful!
4/17/2017 16:533Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/17/2017 17:4516MTA TFTP: Successful
4/17/2017 17:4526MTA PROV: Successful!
4/17/2017 17:453Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/17/2017 17:4514Power Supply Telemetry Log - BATTERY MISSING
4/18/2017 0:4916MTA TFTP: Successful
4/18/2017 0:4926MTA PROV: Successful!
4/18/2017 0:493Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/18/2017 0:4914Power Supply Telemetry Log - BATTERY MISSING

 

 
Expert

Re: San Diego Intermittent Slow Speeds

Ok, now that you have good levels, click on the reset FEC counters to zero out the corrected/ uncorrecteds. Then repost the level page a few hours later to see if there's an actual ingress issue remaining...

 

"Moved  adapter"??? what is it?

 

Observer

Re: San Diego Intermittent Slow Speeds

By adapter I meant modem Smiley Happy  I moved it to a place in the house with fewer splits.  I reset the counters and will check again in a few hours.  Thanks!

Expert

Re: San Diego Intermittent Slow Speeds

MODEM MUST BE ON THE FIRST 2 WAY SPLITTER AFTER THE GROUNDING BLOCK. Th e other port is then split and fed to cable boxes. if you're still seeing ingress on some channels, there are loose bad connections or a chewed up outside drop from the pole.

 

Observer

Re: San Diego Intermittent Slow Speeds

Modem is on first run after grounded split.  Was working very well for about 2 days, and now its  dropped from 350Mbps to 20Mbps (down).  Up still constant at 24Mbps.  One of the downstream chanells is sudently not reporting.  Here are the logs:

 

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 124645.00 MHz-1.30 dBmV40.37 dB256QAM7002159942416681
Downstream 21507.00 MHz-0.20 dBmV40.37 dB256QAM230055665542245
Downstream 32513.00 MHz------------------------
Downstream 43519.00 MHz0.10 dBmV40.37 dB256QAM22696442611311376336
Downstream 54525.00 MHz0.10 dBmV40.37 dB256QAM2218108162829108
Downstream 65531.00 MHz0.10 dBmV40.95 dB256QAM2336770232559449
Downstream 76537.00 MHz0.20 dBmV40.95 dB256QAM2382011911777060
Downstream 87543.00 MHz0.00 dBmV40.37 dB256QAM22886364591515011
Downstream 98549.00 MHz0.00 dBmV40.37 dB256QAM2360946571572001
Downstream 109555.00 MHz0.10 dBmV40.37 dB256QAM2592748871483052
Downstream 1110561.00 MHz-0.10 dBmV40.37 dB256QAM2645477191885599
Downstream 1211567.00 MHz-0.50 dBmV40.95 dB256QAM2656261812302712
Downstream 1319615.00 MHz-2.30 dBmV40.37 dB256QAM252571498150886
Downstream 1420621.00 MHz-2.10 dBmV40.37 dB256QAM24883655418512147
Downstream 1521627.00 MHz-2.20 dBmV40.37 dB256QAM2473246321964483
Downstream 1622633.00 MHz-2.20 dBmV38.61 dB256QAM250897314129701
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 12037.00 MHz42.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 21930.60 MHz42.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 31823.30 MHz40.50 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 41718.50 MHz39.50 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 Status
System Uptime:2 d: 17 h: 03 m
Computers Detected:staticCPE(2), dynamicCPE(0)
CM Status:Telephony-Reg Complete
Time and Date:Thu 2017-04-20 17:50:45

 

 Interface Parameters

 

Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledUp1000(Full)54:65Smiley Very HappyE:29:92:01
LAN Port 2EnabledUp1000(Full)54:65Smiley Very HappyE:29:92:01
LAN Port 3EnabledDown-----54:65Smiley Very HappyE:29:92:01
LAN Port 4EnabledDown-----54:65Smiley Very HappyE:29:92:01
CABLEEnabledUp-----54:65Smiley Very HappyE:29:92:02
MTAPassUp-----

54:65Smiley Very HappyE:29:92:03

 

 

DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
4/20/2017 17:31840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840202005Lost MDD Timeout;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840007005RCS Partial Service;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;
4/20/2017 17:31840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:65:de:29:92:02;CMTS-MAC=00:01:5c:64:de:48;CM-QOS=1.1;CM-VER=3.0;

 

 PacketCable(MTA) Events

 

 

Date TimeEvent IDDescription
4/14/2017 16:4626MTA PROV: Successful!
4/14/2017 16:463Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/15/2017 0:4814Power Supply Telemetry Log - BATTERY MISSING
4/15/2017 0:4816MTA TFTP: Successful
4/15/2017 0:4826MTA PROV: Successful!
4/15/2017 0:483Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/16/2017 16:2514Power Supply Telemetry Log - BATTERY MISSING
4/16/2017 16:2516MTA TFTP: Successful
4/16/2017 16:2526MTA PROV: Successful!
4/16/2017 16:253Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/17/2017 16:5314Power Supply Telemetry Log - BATTERY MISSING
4/17/2017 16:5316MTA TFTP: Successful
4/17/2017 16:5326MTA PROV: Successful!
4/17/2017 16:533Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/17/2017 17:4516MTA TFTP: Successful
4/17/2017 17:4526MTA PROV: Successful!
4/17/2017 17:453Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/17/2017 17:4514Power Supply Telemetry Log - BATTERY MISSING
4/18/2017 0:4916MTA TFTP: Successful
4/18/2017 0:4926MTA PROV: Successful!
4/18/2017 0:493Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/18/2017 0:4914Power Supply Telemetry Log - BATTERY MISSING
4/19/2017 16:473Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
4/19/2017 16:4814Power Supply Telemetry Log - BATTERY MISSING
4/19/2017 16:4816MTA TFTP: Successful
4/19/2017 16:4826MTA PROV: Successful!
4/19/2017 16:483Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
4/19/2017 23:103Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
4/19/2017 23:1114Power Supply Telemetry Log - BATTERY MISSING
4/19/2017 23:1116MTA TFTP: Successful
4/19/2017 23:1126MTA PROV: Successful!
4/19/2017 23:113Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS

Thanks for all your help!

Observer

Re: San Diego Intermittent Slow Speeds

Hi, just an update that things arent getting any better.  I work from home and this is a huge problem for my productivity.  Is it work having a tech come out (for the 3rd time)?

Established Sharer

Re: San Diego Intermittent Slow Speeds

I notice that your two Ethernet connections into the modem at first reported as 100 Mbps and 1000 Mbps.  After physically moving the modem and changing which ports they were plugged into, both now show a speed of 1000 (Gigabit).  It looks like you had a bad ethernet cable on one of the devices before, which would have limited that device to upload and download speeds of 100 Mbps maximum. 

Your critical issue is still most definitely a severe leakage of broadcast TV into the cable network.  Usually it's not the user's problem, and unless you have old obsolete RG59 cable with a braided copper shield but no foil layer or the amplifier you mentioned is set up improperly and generating excessive noise, the root cause is probably not located within your home.

Typically the causes are either a break in the outer shield of the main trunk line on the street, water-induced corrosion where the cable jacket is abraded by rubbing on tree branches or squirrels keepng their teeth sharp, or a neighbor who has changed his cable wiring using old or improperly assembled hardware.  

If you want TWC to fix the problem you absolutely need a tech who can read the reports you posted here and also knows where and what to look for with his test equipment.  When the problem is not inside your home, it usually requires a follow-up by a line repair crew, which could be scheduled for up to a week later.  None of these causes can EVER be fixed by replacing your modem, despite anything the tech support desk will try to tell you!  

Observer

Re: San Diego Intermittent Slow Speeds

Thanks - I have scheduled a tech for later today, I'll show him this thread and have him check the wires.  

 

FWIW, I swapped ethernet cables to get both links to 1000 - that was a known issue I finally corrected Smiley Happy