Cable Modem disconnects several times a day

Not sure where your going with the logs. The 1970 date is just what it defaults to when it has no TOD which can happen any time the modem reboots, not just any time it loses connection to the ISP. 

1. What are the signal levels of your modem?

2. Do you know anything about what happened that caused the outage? Weather? Accident? Etc

3. What do the logs say exactly? Maybe include those with the signal levels in your reply?

Thanks for the replies, here is the signal and the logs

Status | Signal | Addresses | Configuration | Logs | Open Source | Help

Signal levels look good. Great actually.

Logs look to be from Oct 02 2013 03:58:29 to Oct 02 2013 15:03:16 or roughly 11 hours I see 5 T3 error's and each one seems to occur after a reboot, similar to the other thread. But I think a modem locking up and requiring a reboot can be caused by many things, even though the symptoms all look the same in the logs. Three possibilities I see are hardware defect, firmware bug, or signal problem that we can't see via the diagnostics. Given you said this happened after a outage could you give more information on that period? How did you know it was a outage and do you know what caused it?

Thanks for the reply.

The outage was three weeks ago after midnight, and when I called Cox, the fellow I spoke to said estimated time of service restore is around 6 AM.

Than the disconnect issue started which I blamed it on my old Docsis 2 modem, and made me buy the Motorola SB6141.

The Motorola modem is brand new, less than 2 days in service, it was activated less than 2 days ago which probably is on the log as well.

So far over 24hrs since the last disconnect, I'm keeping my fingers crossed.

Are the speed increases coming attached to price increases, and how much of an increase for preferred and premier speeds?

Thanks.

Sounds like a piece of equipment went down, they padded the levels and then schedule maintenance to repair it in the morning. If it was line work, they would want to do it at night. I kind of predict it's going to happen a couple more times unfortunately. Fingers crossed though

I have the same problem.  This is the second time in 60 days this problem surfaced.  I was told my signal leveld were bad but they match the noise levels of other customers.  i have a techcian comming out but i literally have not internet now.  always thought my xbox video buffering problem was strange starting to think i have been getting below quality service (signal) for years.

can somebody check my service codes and see if there is anything that can be done?

Derrick,

If you end up checking I was invested $1o purchase a 25" cable from another room.  Now that i actually have a keyboard I can provide some additional information.

My modem is a SB6121 which I purchase because I was having a similar problem about a year ago.  The only difference between now and then is that I would actually connect to the internet for about 10-15 minutes at a time.

I am going to of course hook it backup ( to the original location )as I had it before the technician comes out because the support call I made last night indicate the signals were bad in my office and good in my bedroom.  I can't keep a 25' coax cable on the ground forever.

The upstream and downstream lights are blue which per the datasheet I have indicates that "high speed data service might not be available in my area"

Tiffany,

I have sent the information as requested to the email address with some additional information and a link to this forum topic.

I did not receive an email to my response I am not getting a feeling like the technician knows what the problem is

I had a feeling we were not the only family experiencing these "rolling blackouts" from cox cable. The Original Poster seems to be describing the same issue which me and my family have been experiencing. Of course this wasn't always the case. We have been cox cable customer for at least 3 years here in Orange County and we had no problems so far. However, for the past week or so we have been plagued with disconnections and all pointing towards the modem. I know that because I can see what the modem is doing during those disconnections.

The cable guy who came over today had absolutely no impact on the problem. Can some explain to me why cox cable is unable to communicate to customers what the problem is? Is there a line half broken somewhere here in Laguna Beach? Are they working on it? A little communication about these issues would make me and my family feel better knowing that cox cable is working on it. 

I think this is a widespread problem not unique to any single customer. I mean no offense by that statement. I just would like this problem resolved so that we can continue online as usual, and as cox customers.

P.S. The disconnection usually don't last very long, sometimes they last for quite a while. I also noticed that uploading data is the first thing to be affected be these disconnections. The downlink may still work during that time, at least for a short while. This info is based on one of my family members playing a game online during these disconnections. As I see it, the server in the game is able to send data to us, but we are not able to send any data back during these disconnections.

OC is a pretty big area, so I think it is more likely a localized signal problem. What your describing sounds like noise or "ingress" on one of the upstream channels, which slows upload bandwidth, then modem notices noise and reboots to correct and locks onto another channel, if it can find one within signal range. Its all just hypothetical, but it fits. Any ingress issue is going to be limited to the device producing the cable signal or CMTS. So unless your in the same CMTS, its probably not related to this post so you might want to make a new thread. 

Cox couldn't tell you what the problem probably because they just didn't know. Troubleshooting is not a perfect science. I am told Ingress is very tricky to track. First, you have to isolate it's frequency and then trace it's source. Alot of times it will stop while your tracing it, and won't come back for months. If the problem wasn't happening when the technician was out there I can see why the technician might just assume it's a fluke or something that someone else fixed. I hope it's not a big problem like I am describing and like you suspect, because those are hard to fix. I would suggest starting a new thread and trying to see if there is perhaps a simpler explanation. Good luck