Hello!

I have Xfinity/Comcast Internet Via Modem & Ethernet.

Today, the internet went down for quite some time, and after trying a dozen things, finally I UNPLUGGED everything for 10 minutes and restarted it.  That seemed to do the trick.

And it occurred to me that perhaps it would be a good idea to UNPLUG Everything --Modem, Computer, ETC.-- Every Day when I go to bed (which is midday because I work graveyard shift) so that the Entire System (including modem) will have a complete rest every day.

Would it be okay to do this?

Thank you for your help & advice!

Chuck

Here is my ongoing problem for the last 2 months.  When I am on the internet my service just drops out.  I run trouble shooting and it tells me my modem has lost its connection and to unplug, wait 10 seconds and to plug back in.  This can happen 10- 20 times a day.  One day I got tired of waiting for the modem to come up and went outside to the box and just unpluged the cable coming into the house, waited a few seconds and plugged it back in.  When I got back inside my connection was restored.  Now I do this everytime it drops (still 10-20tomes a day) and it fixes the probem temporarily and I go do it again.  Does anyone else have this problem and why is it happening?  I am hesitant to call the locals due to bad experiences in the past.

I upgraded to Extreme 250 in October 2015 - was getting the full speed on my own model (Arris TG822G) just fine.  Downloads, speedtests were confirming the speed.

However I noticed in the last few weeks, I am now getting speeds of much less than that - often times even below 100Mbps and it has not recovered.  I also got an email from Comcast saying that it's time for me to upgrade my modem because new equipment is available.

I dont' want to rent one because it was working fine before and I need one that has telephony since I'm on the triple-play packages.

Does anyone know if Comcast changed their technical requirements so that 250Mbps service requires 16x4 DOCSIS 3.0 modems instead of the 8x4 one that I have been using successfully for the last several months?

hi this pacman my connection to my computer is not connecting to my computer keeps telling me that to connect to XFINITY FOR MY COMPUTER WHEN I NEVER WAS CONNECTED TO XFINITY AND NOT MY PASSWORD NUMBER CAUSE XFINITY IS CAUSEING PROBLEMS WITH MY CONNECTIONS SO IF YOU CAN FIX THIS PROBLEM I WOULD BE GREATFUL FOR IT THATS ALL I REALLY HAVE TO SAY ABOUT THIS AND TELL XFINITY TO STOP MESSING WITH MY CONNECTION TO MY COMPUTER LAPTOP....THANK YOU!!!!   

So I upgraded to Blast last month and to get the 75mbs working I needed the help of ComastJohnF,  and now 2 weeks later I am back to 25mbs and after chatting with support, still no change........

Rebooted Modem,  Chatted with support.....  No help.

I hate to complain but Comcast just seems to be running too slow given what I am paying for.

I had a new new IMAC. Ran slow. Gave it to my kid.  I then purchased a new DELL Inspiron 24-3455, 8GB RAM< 64 BIT, AMD A8, 2.2GHZ. Also runs slow.

I am a basic email user and website browsing. I upgraded to BLAST to see if there was a difference.

My speed tests do show improved upload/download speeds. 172/12. But, for basic browsing on Facebook, banking website and even the Comcast homepage,

my response times are not adequate give what I pay for. I also tried the new "speed experience test". That showed no problems.

I have had technicians to the house. They said the signal to my house met the exceptible minimum range but it was at the low end.

I really think there is a problem with the signal strength on my street. Other neighbors have also complained.

My cable box is approx 200 ft from my house. That could be an issue.  

How can I prove this?

I am losing internet connectivity and experiencing large variations in connection speed, using my Arris  SBG6700-AC.  I have 120 mbps service.  A modem reboot resolves the problem for a while.  So does a reset signal sent by Comcast.

Results from Speedtest.net are all over the place.  A sample is shown below.  Connection was to an Ipad using a 5G link.  Distance to the modem/router was about 15 feet.  Distance between the modem and the nearest wireless phone is about 30 feet.

The cable service enters my home and goes into a Comcast supplied Comscope VOIP amplifier/splitter.  The cable modem comes off of the VOIP port and is a straight 50 ft shot to the modem.

My Arris event log shows numerous critical events such as T2, T3 and T4 timeouts.

The table below contains the log of events that the SBG6700-AC has detected. 

Time Priority Description
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Notice (6) WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:N/A) - Reason:INIT
Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT

Tue May 24 13:08:24 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 13:04:04 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 12:27:58 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 12:23:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 12:06:47 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 12:02:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.0;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Tue May 24 11:46:20 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 11:42:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.0;CM-VER=3.0;

Tue May 24 11:32:27 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 11:28:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 11:27:50 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 11:27:50 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 11:27:50 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 10:45:33 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 09:21:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Tue May 24 08:25:43 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 08:21:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 05:23:26 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 05:19:06 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 04:04:34 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 04:04:34 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 04:04:34 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 04:00:50 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 04:00:50 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 04:00:49 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 02:57:42 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 02:57:42 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 02:57:42 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 02:57:40 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 02:57:40 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 02:57:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 00:51:11 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 00:51:11 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Tue May 24 00:51:11 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 21:44:38 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 21:44:38 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 21:44:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 21:44:38 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 21:44:38 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 21:44:37 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 21:37:19 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 21:32:59 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 23 19:24:14 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 19:19:54 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 18:55:03 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 18:50:42 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 18:50:39 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 18:50:39 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 18:50:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 14:03:18 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 13:58:57 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 23 13:53:35 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 13:49:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

                 
Mon May 23 11:44:23 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;    

Mon May 23 11:40:03 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 11:13:42 2016 Critical (3) No Ranging Response received - T3 time-out

Mon May 23 11:13:33 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.0;CM-VER=3.0;

Mon May 23 11:13:02 2016 Critical (3) No Ranging Response received - T3 time-out

Mon May 23 11:12:26 2016 Critical (3) No Ranging Response received - T3 time-out

Mon May 23 11:12:21 2016 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.0;CM-VER=3.0;

Mon May 23 11:12:11 2016 Critical (3) No Ranging Response received - T3 time-out

Mon May 23 11:10:33 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 11:06:13 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 10:40:05 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 10:35:45 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 23 10:29:04 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 10:24:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.0;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 23 10:15:33 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 10:11:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 10:03:14 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 09:58:53 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 09:58:35 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 09:58:35 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 09:58:35 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 09:21:18 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 09:16:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.0;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 23 08:39:22 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 08:35:02 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

 
Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 23 07:43:58 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Mon May 23 07:39:37 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.0;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.0;CM-VER=3.0;

Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 23 07:33:33 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:36:e4:ff:c5:28;CMTS-MAC=00:01:5c:75:2e:77;CM-QOS=1.1;CM-VER=3.0;

The Status - Connection

The connection statuses listed show the connection state of the cable modem. 

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels

Channel      Lock Status      Modulation Channel ID     Frequency            Power         SNR       Corrected      Uncorrectables

     1             Locked               QAM256          16        609000000 Hz      4.3 dBmV      41.9 dB          6                       28
     2             Locked               QAM256          17        615000000 Hz      4.1 dBmV      41.9 dB          0                         0
     3             Locked               QAM256          19        627000000 Hz       4.0 dBmV     41.9 dB          0                         0
     4             Locked               QAM256          20        633000000 Hz       4.0 dBmV     41.9 dB          0                         0
     5             Locked               QAM256          21        639000000 Hz       4.1 dBmV     41.9 dB          0                         0
     6             Locked               QAM256          22        645000000 Hz       4.3 dBmV     41.9 dB          0                         0
     7             Locked               QAM256          23        651000000 Hz       4.3 dBmV     41.9 dB          0                         0
     8             Locked                QAM256         24        657000000 Hz      4.5 dBmV      41.9 dB          0                         0

Upstream Bonded Channels

Channel Lock Status      US Channel Type     Channel ID     Symbol Rate             Frequency         Power
1            Locked                  ATDMA                         41          5120 Ksym/sec       34800000 Hz     44.3 dBmV
2            Locked                  ATDMA                         42          5120 Ksym/sec       27900000 Hz     43.8 dBmV
3            Locked                  ATDMA                         43          5120 Ksym/sec       21000000 Hz     43.0 dBmV

The Comcast phone representatives say I need to contact my modem vendor for further assistance.  I suspect the issue is outside my home.  Any help on determining what the above data indicate bwould be greatly appreciated.

When I read my meter usage up until a few days ago it used to say 250 MB cap not enforced. Now it no longer says anything about the cap. Chicagoland Area. Sorry if this has been posted before by someone else.

I have Blast in Chicago 75Mbps. Currently have modem: SB6141, router: Asus RT-N66U. For the longest time I've not been able to get more than 40Mbps and there's many times when speeds slow to 1-4Mbps. I've been going round and round with Comcast trying to figure out what's going on. Before I finally give up and have a tech come out - I thought I'd post here.

Just for giggles I bought a SB6183 and had Comcast link it to my account to see if the modem was somehow the problem. I went from consistently geting 30Mbps for the past couple days to 4. I'm getting this off direct line to modem and router. So I'm going to return this 183 and go back to the 141 modem.

I also downloaded and installed the most up-to-date firmware for my router.

I checked Comcast's Speed Experience tool and it says it does see slow speeds - but that everything is fine between Comcast and the modem.

For the past few months every time it's gone down to single digits I call Comcast and have them refresh the modem - and it goes back up to about 40. Restarting modem from the Comcast app doesn't always do the trick so I have to call in all the time.

I've seen on here where people are posting all kind of modem statistics - where can I get those?

I'm thinking at this point it's just got to be somehting with the line itself. The 141 should totally be able to get me 75.

Extreme amounts of packet loss, internet will randomly go in and out at all times of the day, sometimes it will disappear for a week and then come back for three. I have had 2 techs out to the house so far and have contacted support by phone and online chat many many times and nothing seems to be getting resolved. I have no idea whether or not the issue is on my end or comcast but I need assistance with fixing this issue.

My internet service is usually rock solid, but in the last 2 days it has gone down and back up frequently. I noitced my 3 upstream channels, which usually have a power of around 42 dBmV, yesterday went up to 46-47, and today they are 49.3/49.5/49.8. I have a Motorola SB6183. Do any of the Comcast guys frequent here, and can see if there is something upstream causing the modem to work harder to push things upstream? I am in zip code 21030.