jasonb's profile

New Contributor III

 • 

38 Messages

Closed

Internet Issues again

Well, after weeks of fighting with Cox and being told it was my modem they finally sent a tech that found the issue to be in the mainline. They turned that over to the 'mainline' crew and I was told after a week that the issue was resolved. the uncorrectables stayed low on my modem, and the T3 errors disappereared for about 5 days or so. Now tonight it came back with a vengeance. I couldn't load the cox support page, the uncorrectables were incrementing about 100000 a second and the T3 errors are back. When I was finally able to get speedtest.net to open, it was showing .80Mb download, and never made it to the upload. I asked about getting them to send the techs back out to check the mainlines and was told they could sent a tech to my house again, next week? I was also asked if I would like to upgrade my service for 5 dollars more a month to see if that helped. I am not sure why they believe that would when the current service has issues. I also asked about some kind of refund or credit since this issue has been persistant for about 4 months and got transferred to a department that wasn't open. 

30 minutes later, my connection is back, but still having errors in the modem. Does anyone know a way to get the construction/repair people out to look at this stuff with out going through all of the trouble of having them send techs out to look at my home again?
 

Valued Contributor II

 • 

2.8K Messages

Do you have the maintenance ticket from the last time the technician was out at your house as part of this thread?  This is why follow up is KEY. Problems like this disappear and reappear. The procedure to get repair tickets is for the trouble call technician to record data, and then use that data to make a ticket for repair. Sometimes the problem stops occurring, and the repair crew can do nothing but wait for it to return. Its like tracking down a grasshopper. Listen..wait...listen..wait..GOTCHYA. 

New Contributor III

 • 

38 Messages

I don't think I do. The tech came when i wasn't home, my fiance was. He called me and told me the issue was in the mainline somewhere and that he was turning it over to the crew that handles that. He never gave me a ticket number or anything.

New Contributor III

 • 

38 Messages

This is since about 830PM yesterday.

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 2 819000000 Hz -3.8 dBmV 37.2 dB 95809 908
2 Locked QAM256 1 813000000 Hz -3.4 dBmV 37.7 dB 74740 443
3 Locked QAM256 3 825000000 Hz -3.2 dBmV 37.5 dB 177649 1135
4 Locked QAM256 4 831000000 Hz -3.2 dBmV 37.6 dB 380961 2320
5 Locked QAM256 9 861000000 Hz -3.2 dBmV 37.7 dB 63934728 40030
6 Locked QAM256 10 867000000 Hz -3.3 dBmV 37.3 dB 543147552 47273318
7 Locked QAM256 11 873000000 Hz -3.5 dBmV 37.1 dB 41971374 13182356
8 Locked QAM256 12 879000000 Hz -4.1 dBmV 37.1 dB 159539524 28712586

The errors came back after a few days

Time   Priority   Description 
 Sat Oct 31 20:23:18 2015    Error (4)   DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Sat Oct 31 18:24:36 2015    Warning (5)   MDD message timeout;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Sat Oct 31 08:23:18 2015    Error (4)   DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Sat Oct 31 02:53:42 2015    Warning (5)   MDD message timeout;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 20:23:21 2015    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established   Warning (5)   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established   Critical (3)   No Ranging Response received - T3 time-out  
 Fri Oct 30 19:38:24 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:38:10 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:37:25 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:37:10 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:36:55 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:36:40 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:36:25 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:36:10 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:35:55 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:35:40 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:35:25 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:35:10 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:34:55 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:34:25 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:33:55 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:32:41 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:32:11 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:30:41 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 19:30:26 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 13:34:22 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 13:24:24 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 13:21:42 2015    Critical (3)   SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 13:21:42 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Fri Oct 30 11:55:43 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Tue Oct 27 18:19:49 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Tue Oct 27 15:25:24 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Sun Oct 25 18:53:48 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 
 Thu Oct 22 17:28:20 2015    Critical (3)   No Ranging Response received - T3 time-out  
 Time Not Established   Critical (3)   No Ranging Response received - T3 time-out  
 Tue Oct 20 02:02:13 2015    Critical (3)   SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=3c:75:4a:f1:d8:ad;CMTS-MAC=00:15:f9:29:f2:63;CM-QOS=1.1;CM-VER=3.0; 

 

New Contributor III

 • 

38 Messages

I have a number saved in my notes, I am not sure if it is a maintenance ticket, but I believe that maybe the cox lady gave it to me when I was checking on if they come to work on the issue. Does this look like a cox ticket number?     CUI000002933876

New Contributor III

 • 

38 Messages

I'll have to do that. Yesterday they transferred me there but they were closed. So the chat was useless. I spent 15 minutes on there, it took forever for the guy to answer. But he told me that he was having "problems" with his system and couldn't look up the ticket. I finally asked him "I'm guessing your issue won't be resolved anytime soon? Should I try again at a later time?". He just replied yes haha. 

Valued Contributor II

 • 

2.8K Messages

jasonb said:
CUI000002933876

It's a Cox ticket number, but not the right kind. You would usually be looking for something that starts with UNO. CUI is a different system. Couldn't hurt to have someone from Cox to look at it. Could still have notes from the technician with more data.

All I can say is good luck. I been having a issue going on 4 months now.  

New Contributor III

 • 

38 Messages

I guess I'll call and see if they can get me the ticket number. Yeah, I have been having issues for about that long as well I just never got around to calling in until this month. It's gotten progressively worse so I finally had to. Have you talked to them about discounts/credits since you are having issues? I am just curious bc I am thinking about asking. It's frustrating to pay so much for internet when there are so many problems. Unfortunately they kind of have us over a barrel bc there aren't any other decent providers in this area.

New Contributor III

 • 

38 Messages

Decided to chat tech support to see if they could look it up and the guy is telling me that there is a know issue in my area. 

Valued Contributor II

 • 

2.8K Messages

jasonb said:
I guess I'll call and see if they can get me the ticket number.

I kind of doubt it. Many times when a technician calls in a "maintence issue" they are calling a person to report the problem. That person may already have a ticket open on the issue. Or it may be a issue they think can be solved by remote changes to the head end. Either way, if you didn't get a ticket number, the case is probably cold by now. Not to say something didn't get done, it's just going to be hard to find out what, why, and when.

jasonb said:
Have you talked to them about discounts/credits since you are having issues?

Yes, they have given me about a 12$ discount two months. I would suggest it. Many times billing representives want to see reasons for giving credits to be in the notes on the account, so ask someone in technical to do that if needed. 

Moderator

 • 

4.3K Messages

Hi Jason,

It looks like all issues in your immediate area have cleared at this time. If your T3 errors and issues with internet speed continue today, please let us know!

New Contributor III

 • 

38 Messages

So I got a new modem today, SB6190, and got it setup. Weird thing is the Cox site shows 60d/7u, but speedtest.net/testmy.net both show 10-20d/2-3u.

@Becky - New modem was added tonight and I have already seen T3 errors.

Former Moderator

 • 

7.1K Messages

@jasonb

Do any other test sites show similar results as testmy?

New Contributor III

 • 

38 Messages

Yes, both Speedtest.net and TestMy.net both show the same. I didn't try another site, but I can later.

Former Moderator

 • 

7.1K Messages

@jasonb

I'd suggest trying a few others just to see how the results compare.  It's staring to sounds like in-network speeds may not be a problem.  If you could also get some trace routes to hosts you're seeing slower speeds to that might help us better understand where the problem lies.

New Contributor III

 • 

38 Messages

So after some back and forth with cox.help@cox.com, they finally gave me this ticket number. I am guessing this is the one for the tech that came to work on the mainlines. ESR000001900170