I moved from Comcast in Morgantown WV to Comcast Shrewsbury PA and have had awful connectivity ever since. We kept the same 50/10 service.
Every 6 hours I get massive lag spikes and packet loss to the primary gateway (50.152.127.1 or 174.54.224.1 depending on the IP address of the month); I've started tracking Google's 8.8.8.8 latency as well for consistency. 8.8.8.8 is no better.
Google DNS Latency & packet loss 8.8.8.8 Latency Graph
Historical Primary Gateway Graph Historical Graph Before September was Morgantown WV everything else is Shrewsbury.
Morgantown didn't drop packets like Shrewsbury does. My wife and I can no longer stream HD video from Netflix, You Tube or HBO Go. 240 to 384 SD from Netflix to the PS3 in stereo only and rarely get to 480. We once saw 1080 HD once then back to 240 after watching a slide show of Doctor Who....
The PS3 would almost always instantly go to 720 or 1080 HD in Morgantown with surround sound.
There have already been multiple techs out to the house; all of the internal wiring has been replaced and only one splitter (1 -> 2). Everything including line maintenance says the connection is great. But we'll have an hour when no one is awake at 3 or 6 am and the system can't ping 8.8.8.8 or even the primary route! It doesn't seem to be usage based and forget gaming on the connection.
I really just want my Morgantown connection back! It was awesome. What's wrong in Shrewsbury?
Any help would be appreciated.
Thanks!
Modem Information:
Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.10-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Firmware Build Time: Oct 29 2012 18:07:13
Images of Logs and Signal -- odd formatting issues.
Raw text of Signal:
Downstream Bonding Channel Value
Channel ID 2 3 5 7
Frequency 705000000 Hz 711000000 Hz 723000000 Hz 735000000 Hz
Signal to Noise Ratio 36 dB 36 dB 36 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
11 dBmV 10 dBmV 10 dBmV 10 dBmV
Upstream Bonding Channel Value
Channel ID 11 10 12
Frequency 29400000 Hz 22000000 Hz 36200000 Hz
Ranging Service ID 10843 10843 10843
Symbol Rate 5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec
Power Level 42 dBmV 41 dBmV 43 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM
[3] QPSK
[3] 64QAM
Ranging Status Success Success Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 2 3 5 7
Total Unerrored Codewords 4550676031 4550676332 4550676334 4550676512
Total Correctable Codewords 13 0 1 0
Total Uncorrectable Codewords 1543 1349 1474 1427
Raw Text of Logs.
Time Priority Code Message
Jan 24 2014 22:31:49 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 23 2014 19:41:00 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to IP loss ;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 23 2014 19:34:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 20:48:42 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 20:19:23 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 12:22:27 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 12:21:06 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 12:21:01 5-Warning T202.0 Lost MDD Timeout;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 12:20:38 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 12:17:12 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 11:43:17 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 11:43:14 5-Warning T202.0 Lost MDD Timeout;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 11:43:05 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 11:42:50 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2014 11:42:33 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:01:5c:23:86:0d;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=3c:75:4a:6a:c9:bd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;