Skip to main content
JillPill's profile

JillPill

New Contributor

 • 

9 Messages

Closed

Modem techies: Need advice Please

I really just need to be pointed in the right direction because I am being sent in circles.  I have Gigablast and normally I have no issues.  A couple months ago, there was a worker in a bucket truck working on something at the pole.   I am not sure what he was working on but ever since then, my service has been a roller coaster. My internet speed fluctuates dramatically anywhere from double digits to 500 in downloads, hardly ever going above that.  I would normally have a consistent 940s and rarely dropping below 800. The uploads fluctuate as well, at times even being 0. Internittent disconnects yet lights stay on, on the modem.  Zoom calls dropping out.  A tech came out and all cables have been checked inside the house. He tested the line at the box outside on my house and said everything looks good going in and coming out and couldn't find any issues.  I had just replaced my router (because I thought that might be the issue originally).  The issues continued even with that fix.  I showed the tech my modem logs and he suggested possibly replacing modem, so I did.  The issues are still continuing.  Looking at the modem logs (and they were pretty similar even with the old modem), looks like some issues to me, including uncorrectable numbers lol, but of course I am no expert, not even close.

Can someone please tell me who I need to request or what I need to request to get fixed?  I originally asked for a line tech but they said I needed to start at Level 1, but it all ended there. Everyone keeps saying everything looks good.  

Thanks in advance!

Motorola MB8611 _Log files

Connection
   Startup Sequence    
   Startup Step Status Comment

  
   Acquire Downstream Channel 381000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 1 days 23h:57m:11s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 37 381.0 3.3 39.7 102470 204554
   2 Locked QAM256 1 681.0 0.7 42.1 74619 133366
   3 Locked QAM256 2 687.0 0.8 42.2 73224 127295
   4 Locked QAM256 3 693.0 0.8 42.1 71942 124427
   5 Locked QAM256 4 699.0 0.8 41.8 67216 114847
   6 Locked QAM256 5 705.0 1.0 42.1 63933 111423
   7 Locked QAM256 6 711.0 1.2 42.3 61029 107294
   8 Locked QAM256 7 717.0 1.2 42.3 57516 100814
   9 Locked QAM256 8 723.0 1.2 42.4 53525 96724
   10 Locked QAM256 9 729.0 1.5 41.3 51541 94343
   11 Locked Unknown 10 735.0 1.6 0.0 110942628 99667471
   12 Locked Unknown 11 741.0 1.6 0.0 129093076 143727455
   13 Locked QAM256 12 747.0 1.5 33.9 1254668 198058
   14 Locked QAM256 13 753.0 1.8 33.6 3881856 481514
   15 Locked QAM256 14 759.0 1.8 31.3 41639981 26021358
   16 Locked QAM256 15 765.0 1.4 28.5 182807219 179841041
   17 Locked QAM256 16 771.0 1.1 42.2 55365 95717
   18 Locked QAM256 33 357.0 3.0 38.2 113760 228892
   19 Locked QAM256 34 363.0 2.9 37.9 114774 225240
   20 Locked QAM256 35 369.0 3.3 37.7 101590 199638
   21 Locked QAM256 36 375.0 3.5 35.9 119677 244251
   22 Locked QAM256 38 387.0 3.3 39.6 118756 241136
   23 Locked QAM256 39 393.0 3.5 39.7 125769 241567
   24 Locked QAM256 40 399.0 3.3 40.0 116701 223065
   25 Locked QAM256 41 405.0 3.0 39.3 118399 226823
   26 Locked QAM256 42 411.0 2.9 38.3 118420 228623
   27 Locked QAM256 43 417.0 2.9 39.3 103169 213053
   28 Locked QAM256 44 423.0 2.7 40.4 96322 206639
   29 Locked QAM256 45 429.0 2.6 40.8 90512 216281
   30 Locked QAM256 46 435.0 2.6 38.6 90303 222430
   31 Locked QAM256 47 441.0 2.5 41.0 86379 235376
   32 Locked QAM256 48 447.0 2.5 39.6 90922 222903
   33 Locked OFDM PLC 159 300.0 2.7 32.6 -2026803473 72957236


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 36.8 49.8
   2 Locked SC-QAM 2 5120 30.4 47.8
   3 Locked SC-QAM 3 5120 24.0 47.8
   4 Locked SC-QAM 4 5120 17.6 49.8
   5 Locked SC-QAM 5 5120 60.0 47.3
   6 Locked SC-QAM 6 5120 67.0 46.8
   7 Locked SC-QAM 7 5120 74.0 47.3
   8 Locked SC-QAM 8 5120 81.0 46.8


   Downstream Frequency Setting    
   Downstream Frequency Select   
  

Event Log

Top of Form

   Event Log

 


  

   

Time 

 

Priority 

 

Description 

   

18:11:53
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:13:27
Tue Jan 4 2022

 

Warning (5)

 

MDD message timeout;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:13:34
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 15 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:13:34
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:13:45
Tue Jan 4 2022

 

Warning (5)

 

MDD message timeout;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:13:47
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:13:55
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 15 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:13:55
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:15:05
Tue Jan 4 2022

 

Warning (5)

 

MDD message timeout;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:15:12
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:17:05
Tue Jan 4 2022

 

Warning (5)

 

MDD message timeout;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:17:10
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:18:21
Tue Jan 4 2022

 

Warning (5)

 

MDD message timeout;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:18:24
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:18:24
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 1; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:18:32
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 15 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:18:37
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:19:05
Tue Jan 4 2022

 

Warning (5)

 

MDD message timeout;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:19:09
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 1; Chan ID: 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:19:18
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:19:25
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 15 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:19:29
Tue Jan 4 2022

 

Warning (5)

 

MDD message timeout;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:19:30
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:19:30
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 1; Chan ID: 10 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:19:32
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:20:30
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 15 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:20:41
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:20:51
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 15 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:21:11
Tue Jan 4 2022

 

Warning (5)

 

MDD message timeout;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:21:21
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 15 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:21:25
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 4; Chan ID: 10 11 13 14 15; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

18:21:37
Tue Jan 4 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 5; Chan ID: 10 11 13 14 15 43; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

 

 

   

 

Bottom of Form

Discussions

 • 

Updated 

6.8K

5

0

0

C

CrystalS

Former Moderator

 • 

440 Messages

Dear @JillPill,

I am so very sorry to learn of your Internet troubles. You deserve reliability and I'm truly sorry we've let you down. I'm here to help. We would definitely be able to assist you with this. Please reach us on Twitter at @CoxHelp, visit us on Facebook, or email us at cox.help@cox.com. Provide us the name on the account with the complete service address with a link to this thread so we can get started.

Crystal S.
Cox Support Forum Moderator

1

0

J
JillPill

New Contributor

 • 

9 Messages

Will do.

Like

Reply

0

B

Bruce

+4 more

Honored Contributor III

 • 

5.7K Messages

I’m not implying a loose connection is the problem because you could have 2 problems.  Since the Bucket Guy, the consistent degradation of your Internet signal is 1 problem.  The pixilation during wind could be another problem.  Or whatever the Bucket Guy did only gets exacerbated…and noticeable…during wind.  This all began with the Bucket Guy.

The problem could be at the pole, where the pole connects to your house, at the outside box, in your attic, at a neighbor's house or further down the road where Bucket Guy did more maintenance.

4

0

J
JillPill

New Contributor

 • 

9 Messages

Right lol. Could be a real cluster of issues and not exactly related, which is why I didn't initially mention the pixelation of tvs.  Hubby was not able to run any bypasses tonight cuz he got caught up in work calls, unfortunately, but he is going to try and do it in the morning.

You mentioning the possibility of it even being something further down the line in the neighborhood is the other thing that has crossed my mind.  There has been alot of work around here in the last few months since Hurricane Ida, and even though everything was working fine when they originally got me back up, who's to say it didn't get messed up further down when they did other repairs? I just wonder, if that does happen to be the case, is it an easy find and fix or does it take some major effort? lol

I do understand that things take time, which is why I haven't been pushy the last couple of months, but it's just becoming harder and harder to work on unreliable internet and I thought after 2 months, it should at least be improving and not getting worse lol.

Like

Reply

0

J
JonathanJ

Former Moderator

 • 

1.9K Messages

@JillPill

I apologize for any inconvenience this has caused. If you're still having an issue after the tech visit please let us know.

Jonathan J
Cox Moderator

Like

Reply

0

B
Bruce

+4 more

Honored Contributor III

 • 

5.7K Messages

Are you in the New Orleans area?  Yeah, there's been lots of complaints and repair work since Ida.  It's probably not even you.

Like

Reply

0

V
VeronicaDrew

New Contributor

 • 

3 Messages

Just reading this is giving me a headache and bad flashbacks.  You changed nothing, but right after "bucket man" everything went to hell.  So the techs will come out, look at this and that, ask you questions you already answered to prove that you did nothing different, then they'll offer to replace your modem with theirs ("it will be so much faster, for all these reasons").  You'll do the trial and probably just keep it because you're so worn down by the whole thing. If you're like me, it won't help much if at all. ~ Congratulations, you're now renting from Cox what you previously owned (just like me!).  In the meantime, you'll waste time and energy sitting on hold to consult with level 1, then level  2, on and on to "level whatever" tech support, read online articles, switch wires around, speed test, ask forums like this, and sorry to tell you - it's not going to help.  It's not what you did, it's something they did, and my guess it's so that they can service the "free internet for all" mentality crowd moving here that we get to support by having lousy service and getting gaslighted that "nothing is different on our end."  Anyway, I wish you luck, you're going to need it until there's service competition in town.

Like

Reply

0

S

ShockHelpmaster

New Contributor

 • 

2 Messages

Before Blaming the bucket guy you have to consider some things and im not saying he didnt mess up but until your side is pristine condition there is no way to ever convince them its their side of the box with the issues because they do have to check there work and log it.  BUT Man its more just increase in traffic with all the people no longer going to work but working at home from their computers you can time it and see what parts of the day are worse than others it's just like the freeway They say we don't share our bandwidth like DSL but at some point of course we do its unavoidable But there are things you can try replacing all connections like couplers where two wires screw together they go out all the time very easily and cause most problems with tv internet anything traveling along that wire basically and the fewer you have the better of course as well, and you can totally rewire your modem line being sure it is split correctly off the main line with good quality RG6 cable with proper ends as well I hate the compression ones usually used  by Cox techs as they Loesing and will cause a worse connection then they first gave I like real Crimp style ends with no *** out middle no small or to long Tang or wire and make sure the grounding wire is stripped and done correctly Now that's a little over board maybe but that is what you can do on your side so there is no doubt that it is not your side of the box with problems but theirs which is all the care or will want to fix So if you have a friend or someone like me knowledgeable with RG cabling It's not hard or expensive to get them to do it offer them something and in 2 4 hours you'll have the best possible connection to cox you can do yourself. Now sadly as giga blast customers we are not guaranteed that speed plus you also have to take into effect the server or service you are connecting to as they might not have as great of a connection as you think.  But we passed the Load tests now when they stop squeezing every half Shekel out of DOSIC 3.1 and get DOSIC 4.0 available that is when a giga blast will be a giga blast customer with at least a 1gig upload which is the biggest and most important increase needed and 2 to 6gig down load which is probably unneeded truly but That copper line has a lot more to offer than most could imagine cause this is just with a few upgrades to their lines and nothing huge so they can still take it beyond this next level and here in phoenix fiber probably isn't ever coming to your house especially if you knew Who really owned all of it (Hint its a water and power distributor who owns most of Phx infrastructure as my dad who work for them 55 years enlightened to me one day when i brought it up back in google fiber days Its SRP and cox pays them well to keep them on lock) But copper has at least a decade maybe more and is already there and everywhere and is better than fiber to the house in my opinion It has its place and need and its used there properly I watch A whole prison get wired for fiber witched it had already Blown millions of tax payers money runing it thruout their prison to sit unused and now outdated being fiber is much purer and more flexible and durable now.  But paid to run a 48 line trunk i believe into there comm room for 2 of those 48 wires to run the whole prisons everything It was hilarious to me especially all the problems it caused at first just switching to that kind of in out system and the usual bottlenecks it creates instead of the magical flow most all think it is easily switch over to. But i digress back to our COX and what we should be asking for and demanding updates about and possible release dates or beta trials as I am almost positively sure they have already done the simple upgrades to DOSIC 4.0 needed by them on their few components required, but maybe Like with everything else 5g cell and all those other wonders promised 4 years ago when it was feasible COX like all others are still tearing out all of their Huawii equipment from the network as I can only imagine how it must of been so immense and costly to replace especially if they had to go with cisco.  And i am all for any product not made in Communist China or any communist country ide love USA but that is a dream just like the excuse from mister half shekel that Huawii and the other banned companies which if looked into has more to do with US citizens not being able to buy or invest in their companies not the stuff fed to us more lies and things that made is easier for them to do things quickly and quietly by saying things like they have Spying stuff in its setup or systems in them with no proof or evidence just accusations lies and money from other competitors and other countries illegally arresting others for a good show to make it real because there is no way it had nothing to do with their uncanny ability to release the same techs either as fast or faster for far cheaper with no real lose in quality really if you knew what you were doing.  Either way when DOSIC 4.0 comes at least here in Phoenix its going to be what most have been really wanting and some actually needing 1 gig upload now gaming becomes something and even this emerging meta verse has potential of real growth all from the beautiful nice pure solid wire of copper.  And DOSIC 4.0 is just the first and easiest and fastest upgrade they can still get even more out of that one wire than you can imagine and only need the one not 2 like fiber and all it will take it some upgrades to the network with new tech now the next update will be alot more and still not as destructive as google fiber or any of those destructive projects tried all over I mean like i said all the main fiber is already laid I saw it years ago but COX has it on lock and i think for good reason I really feel with the next update we will have the better internet system in the nation Of course competion would be nice and there is some finally but not enough i know. 

3

0

B
Bruce

+4 more

Honored Contributor III

 • 

5.7K Messages

Did you say something?

Like

Reply

J
JillPill

New Contributor

 • 

9 Messages

Ok. So I was trying to post on here earlier after husband bypassed splitters but there was too much happening at home.  So here we go now.  After he bypassed the splitter and did a direct barrel connect, speedtest was good but internet kept dropping.  These are not lengthy drops but enough for the computer to notify me every couple of minutes.  I copied the current modem logs after a little time went by and will attach to this post.  In the meantime, the tech came out, tested at the box (just like the last tech) except this one said there was ingress and the problem is inside, then left. He said ingress is always inside.  He was here maybe 5-10 mins.  I mentioned the pixelation of tv as well and he said he hears that all the time and there's no telling what is causing that. 

Should we just redo all of our indoor wiring?

Here are my modem logs while connected with NO splitter.

Connection

Top of Form

   Startup Sequence

 

 

   Startup Step

Status

Comment



  

   Acquire Downstream Channel

381000000 Hz

Locked


  

   Upstream Connection

OK

Operational


  

   Boot State

OK

Operational



  

   Configuration File

OK


  

   Security

Enabled

BPI+


  

 

   Connection Status

 

 

   System Up Time

0 days 00h:52m:44s

 


  

   Network Access

Allowed

 


  

 

   Downstream Bonded Channels

 


  

   Channel

Lock Status

Modulation

Channel ID

Freq. (MHz)

Pwr (dBmV)

SNR (dB)

Corrected

Uncorrected

   1

Locked

QAM256

37

381.0

7.1

45.1

0

0

   2

Locked

QAM256

1

681.0

3.7

42.5

0

0

   3

Locked

QAM256

2

687.0

3.9

42.8

0

0

   4

Locked

QAM256

3

693.0

3.9

42.8

0

0

   5

Locked

QAM256

4

699.0

4.0

42.6

0

0

   6

Locked

QAM256

5

705.0

4.2

42.9

0

0

   7

Locked

QAM256

6

711.0

4.3

42.9

0

0

   8

Locked

QAM256

7

717.0

4.4

42.9

0

0

   9

Locked

QAM256

8

723.0

4.3

42.7

0

0

   10

Locked

QAM256

9

729.0

4.5

42.7

0

0

   11

Locked

QAM256

10

735.0

4.5

42.6

0

0

   12

Locked

QAM256

11

741.0

4.5

42.7

0

0

   13

Locked

QAM256

12

747.0

4.4

42.7

0

0

   14

Locked

QAM256

13

753.0

4.7

42.8

0

0

   15

Locked

QAM256

14

759.0

4.6

42.7

0

0

   16

Locked

QAM256

15

765.0

4.4

42.6

0

0

   17

Locked

QAM256

16

771.0

4.1

42.4

0

0

   18

Locked

QAM256

33

357.0

7.0

44.9

0

0

   19

Locked

QAM256

34

363.0

6.9

45.0

0

0

   20

Locked

QAM256

35

369.0

7.2

45.2

0

0

   21

Locked

QAM256

36

375.0

7.3

45.2

0

0

   22

Locked

QAM256

38

387.0

7.0

45.2

1

0

   23

Locked

QAM256

39

393.0

7.2

45.2

0

0

   24

Locked

QAM256

40

399.0

7.1

45.2

0

0

   25

Locked

QAM256

41

405.0

7.0

45.3

0

0

   26

Locked

QAM256

42

411.0

7.0

45.2

0

0

   27

Locked

QAM256

43

417.0

7.2

45.3

0

0

   28

Locked

QAM256

44

423.0

7.1

45.2

0

0

   29

Locked

QAM256

45

429.0

6.9

45.2

0

0

   30

Locked

QAM256

46

435.0

6.9

45.0

0

0

   31

Locked

QAM256

47

441.0

6.8

45.1

0

0

   32

Locked

QAM256

48

447.0

6.7

45.0

0

0

   33

Locked

OFDM PLC

159

300.0

7.5

43.3

27035069

0

 

   Upstream Bonded Channels

 


  

   Channel

Lock Status

Channel Type

Channel ID

Symb. Rate (Ksym/sec)

Freq. (MHz)

Pwr (dBmV)

   1

Locked

SC-QAM

1

5120

36.8

38.5

   2

Locked

SC-QAM

2

5120

30.4

38.0

   3

Locked

SC-QAM

3

5120

24.0

38.0

   4

Locked

SC-QAM

4

5120

17.6

37.3

   5

Locked

SC-QAM

5

5120

60.0

39.5

   6

Locked

SC-QAM

6

5120

67.0

40.0

   7

Locked

SC-QAM

7

5120

74.0

40.0

   8

Locked

SC-QAM

8

5120

81.0

40.5

 

   Downstream Frequency Setting

 

 

   Downstream Frequency Select

  


  

 

Bottom of Form

Event Log

Top of Form

   Event Log

 


  

   

Time 

 

Priority 

 

Description 

   

10:28:28
Tue Jan 4 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

14:34:44
Tue Jan 4 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

16:30:13
Tue Jan 4 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

16:34:39
Tue Jan 4 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

17:26:08
Tue Jan 4 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

17:33:27
Tue Jan 4 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

17:41:47
Tue Jan 4 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

19:13:26
Tue Jan 4 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

08:10:43
Wed Jan 5 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

07:48:31
Thu Jan 6 2022

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:16:17
Thu Jan 6 2022

 

Critical (3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

Time Not Established

 

Critical (3)

 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

   

Time Not Established

 

Critical (3)

 

No Ranging Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

Time Not Established

 

Notice (6)

 

Honoring MDD; IP provisioning mode = IPv4

   

10:24:15
Thu Jan 6 2022

 

Warning (5)

 

DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:16
Thu Jan 6 2022

 

Notice (6)

 

TLV-11 - unrecognized OID;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:21
Thu Jan 6 2022

 

Notice (6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:26
Thu Jan 6 2022

 

Warning (5)

 

REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:27
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

10:24:28
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:24:28
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

10:36:36
Thu Jan 6 2022

 

Critical (3)

 

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

10:36:39
Thu Jan 6 2022

 

Warning (5)

 

DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

 

 

   

 

Bottom of Form

 

Like

Reply

0

J
JillPill

New Contributor

 • 

9 Messages

And we were still connected without splitters when he tested.

Like

Reply

0

B

Bruce

+4 more

Honored Contributor III

 • 

5.7K Messages

Well, the difference between Corrected and Uncorrected tells the story.  It's now 0.

SNR (Signal to Noise Ratio)
This is how clear the downstream signal at your modem.
For 256 QAM
Minimum:  30 dB
Recommended:  33+ dB
Before/After
• Before, you had averaged almost Minimum at 36 dB
• After, you had averaged better than Recommended at 44 dB
• You gained an average of + 7.34 dB

Downstream Power
This is the amount of signal from Cox to your modem.
Recommended:  - 7 to + 7 dBmV
Acceptable but out of spec:  +/- 8 to +/-10 dBmV
Maximum but out of spec:  +/- 11 to +/- 15 dBmV
Before/After
• Before, your Power appeared to be within spec
• After, your Power still appears to be within spec but gain an average of 3.60 dBmV

If anything, your signal got clearer.

Ingress is just a perceptive.  If you're testing on the Cox network (outside your house), ingress would be noise coming from your house onto the Cox network.  As a Cox tech, I'm sure the tech would call it ingress.

If you were testing inside your house, ingress would be noise coming from the Cox network onto your house.  The tech said your house is creating noise.  Just to be clear, the previous tech(s) did not detect or report ingress?

Was this ingress before or after your husband bypassed the splitters?  Meaning, what was connected inside your house...just the modem and speed-testing laptop or everything?  I think the tech tested before your husband tested.

This appears you have faulty splitters.  Others are much smarter at this than I, so let's see what they conclude.

8

0

J
JillPill

New Contributor

 • 

9 Messages

Lol, once again, I had a whole reply and I keep losing internet. Once, right as I hit send, so I am having to retype everything lol.  This might take a while to get posted lol. 

You were correct in that the previous tech said that everything looked good when he tested.

The modem logs that I posted were after hubby bypassed the splitter but before the tech got here and we only used 1 computer.

Now, hubby did bypass splitters BEFORE the tech came out today and we left them like that for the duration of the testing when the tech was here (which he reported ingress).

After the tech left, hubby had to get back to working so I hooked the router back up. I should have made a copy of the modem logs before I hooked up the router, but the uncorrectables were starting to show up prior to hooking up router, but in low digits and they weren't in every channel yet like they are now.

Now here we are a little over 4 hours since a modem reboot and the uncorrectables are climbing again.  I don't know if that's normal. 

For the record, we are still bypassing splitters at the moment. 

Connection

Top of Form

   Startup Sequence

 

 

   Startup Step

Status

Comment



  

   Acquire Downstream Channel

381000000 Hz

Locked


  

   Upstream Connection

OK

Operational


  

   Boot State

OK

Operational



  

   Configuration File

OK


  

   Security

Enabled

BPI+


  

 

   Connection Status

 

 

   System Up Time

0 days 04h:16m:06s

 


  

   Network Access

Allowed

 


  

 

   Downstream Bonded Channels

 


  

   Channel

Lock Status

Modulation

Channel ID

Freq. (MHz)

Pwr (dBmV)

SNR (dB)

Corrected

Uncorrected

   1

Locked

QAM256

37

381.0

8.2

45.1

22113

61582

   2

Locked

QAM256

1

681.0

3.8

42.3

32923

84538

   3

Locked

QAM256

2

687.0

4.0

42.2

32814

81781

   4

Locked

QAM256

3

693.0

4.0

42.4

32998

78549

   5

Locked

QAM256

4

699.0

4.1

42.5

29050

70096

   6

Locked

QAM256

5

705.0

4.3

42.7

28504

66630

   7

Locked

QAM256

6

711.0

4.4

42.6

26986

63722

   8

Locked

QAM256

7

717.0

4.5

42.6

24285

56670

   9

Locked

QAM256

8

723.0

4.4

42.3

22326

53606

   10

Locked

QAM256

9

729.0

4.6

42.5

22038

53082

   11

Locked

QAM256

10

735.0

4.6

42.3

22504

55605

   12

Locked

QAM256

11

741.0

4.6

42.5

21889

54873

   13

Locked

QAM256

12

747.0

4.5

41.8

25795

66973

   14

Locked

QAM256

13

753.0

4.9

42.5

25418

64216

   15

Locked

QAM256

14

759.0

4.8

42.5

26050

63289

   16

Locked

QAM256

15

765.0

4.5

42.3

25158

59648

   17

Locked

QAM256

16

771.0

4.3

42.2

25623

57677

   18

Locked

QAM256

33

357.0

7.8

44.7

14396

45188

   19

Locked

QAM256

34

363.0

7.8

44.7

52520

177925

   20

Locked

QAM256

35

369.0

8.1

45.0

32937

108602

   21

Locked

QAM256

36

375.0

8.3

45.3

22930

74822

   22

Locked

QAM256

38

387.0

8.1

45.4

19901

47780

   23

Locked

QAM256

39

393.0

8.4

45.4

30608

93284

   24

Locked

QAM256

40

399.0

8.3

45.5

65058

214457

   25

Locked

QAM256

41

405.0

8.1

45.8

38570

122556

   26

Locked

QAM256

42

411.0

8.1

45.5

37540

109817

   27

Locked

QAM256

43

417.0

8.2

45.5

61588

195018

   28

Locked

QAM256

44

423.0

7.9

45.3

43187

136936

   29

Locked

QAM256

45

429.0

7.7

45.2

38070

121799

   30

Locked

QAM256

46

435.0

7.6

45.2

23827

68551

   31

Locked

QAM256

47

441.0

7.4

45.0

26101

79029

   32

Locked

QAM256

48

447.0

7.2

44.9

32013

104582

   33

Locked

OFDM PLC

159

300.0

7.8

43.4

4992219

76932

 

   Upstream Bonded Channels

 


  

   Channel

Lock Status

Channel Type

Channel ID

Symb. Rate (Ksym/sec)

Freq. (MHz)

Pwr (dBmV)

   1

Locked

SC-QAM

1

5120

36.8

38.0

   2

Locked

SC-QAM

2

5120

30.4

38.0

   3

Locked

SC-QAM

3

5120

24.0

37.5

   4

Locked

SC-QAM

4

5120

17.6

37.5

   5

Locked

SC-QAM

5

5120

60.0

39.3

   6

Locked

SC-QAM

6

5120

67.0

39.8

   7

Locked

SC-QAM

7

5120

74.0

40.3

   8

Locked

SC-QAM

8

5120

81.0

40.3

 

   Downstream Frequency Setting

 

 

   Downstream Frequency Select

  


  

Bottom of Form

Event Log

Top of Form

   Event Log

 


  

   

Time 

 

Priority 

 

Description 

   

15:19:53
Thu Jan 6 2022

 

Notice (6)

 

Honoring MDD; IP provisioning mode = IPv4

   

15:19:57
Thu Jan 6 2022

 

Warning (5)

 

DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:19:57
Thu Jan 6 2022

 

Notice (6)

 

TLV-11 - unrecognized OID;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:02
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

15:20:03
Thu Jan 6 2022

 

Critical (3)

 

No Ranging Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:03
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:20:03
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

15:20:04
Thu Jan 6 2022

 

Critical (3)

 

No Ranging Response received - T3 time-out;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:28:13
Thu Jan 6 2022

 

Warning (5)

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:28:13
Thu Jan 6 2022

 

Warning (5)

 

Dynamic Range Window violation

   

15:29:14
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:29:35
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:29:49
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:29:49
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:31:21
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:31:21
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:31:45
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:31:45
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:32:20
Thu Jan 6 2022

 

Critical (3)

 

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:32:23
Thu Jan 6 2022

 

Warning (5)

 

DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:32:27
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

   

15:32:27
Thu Jan 6 2022

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:85:32:8e;CMTS-MAC=d4:ad:71:0c:69:62;CM-QOS=1.1;CM-VER=3.1;

Bottom of Form

 

Like

Reply

0

B
Bruce

+4 more

Honored Contributor III

 • 

5.7K Messages

Ok...4 hours later your signal still looks in specs.

Correctable and Uncorrectable identify packet loss.  You will always have some errors unless you live next door to Cox.  Correctable is the number of packets corrected.  Uncorrectable is the number of packets so corrupt your modem had to request a resend from Cox.

Uncorrectable are your most concerning.  You'll typically see 1 or 2 channels with high Uncorrectables due to interference from specific frequencies.

You, however, have Uncorrectables on all frequencies, so something is causing interference.

Since a couple months ago, did you install new electronic devices in your home?  Hammer any nails into a wall?  Has anybody inspected the 4-foot segment of coax flapping in the breeze outside your house for wear, tear, chaffing?

When you or your husband were in the attic and aside from the 4 segments of coaxial cable and 2 splitters, did you notice any other electronic components, such as an amplifier, filter or tap?

Like

Reply

0

J
JillPill

New Contributor

 • 

9 Messages

Ok. Hubby says he did not see any electrical components in the attic.  There's really no new devices in the home either.  Only a smart plug that I only use during Christmas for the tree, but I did a whole device elimination test even prior to the plug since I was already having issues. I actually did some wifi device moving the other week because the tech that was out here said maybe I had too many devices on one channel. (I laughed because I had a total of 9 devices spread across 3 channels at the time, but I removed them and added 1 at a time anyway to be sure)

I believe the tech today took a quick look at the 4 ft section of cable outside but I know hubby did as well and he didn't see anything that stood out.

Hubby is going to try and make a run to home depot tonight or tomorrow to get the high performance splitter like Mouth suggested cuz it looks like from Amazon it wouldn't get here until next week.  Hopefully that will fix one of my issues.

I am trying not to get too frustrated with all this. It's just crazy to think everything just blew up all at once, when everything was working all good a couple months ago.

I really appreciate all the time yall have taken trying to help me, so please let me know when I have worn out my welcome lol.

Like

Reply

0

B
Bruce

+4 more

Honored Contributor III

 • 

5.7K Messages

Ugh...I'm so sick of you.  Just kidding.

You have 1 router but 3 channels?  What do you mean by channel?  Do you use 3 frequencies:  2.4, 5, 6 or 60 GHz?  A channel would be a specific center-frequency on any of these frequency bands.  In the US, there are 1-11 channels on 2.4 GHz.

You could disconnect the router from the DOCSIS again, reconnect laptop to DOCSIS and let it set overnight or another 4 hours to observe the Uncorrectables.

If the uncorrectable were okay with only a laptop connected but then kinda spiked with the router, you could just monitor with only the laptop connected again for a good sampling of time.  Maybe even unplug the router.  Then again, this would have to be some whacked router to interfere with a modem.  Did husband celebrate Thanksgiving by bouncing the router?

i wouldn't go overboard on a "high performance splitter."  I wouldn't get gold-plated nor would I go cheap.  Home Depot?  Does Home Depot sell splitters?  I mean, it's a weird place to shop for electronics.  I'd think Best B, WallyWorld maybe even a Solution Store.  No Dollar Stores!

(1) 4-way splitter rated 5-1000 MHz (1 GHz) with (1) 3.5 dB output and (3) 7 dB outputs.  Splitters rated 2000+ MHz (2 GHz) are for satellite signals.

If you use MoCA, look for a MoCA 2.0 or whatever version you're using, if applicable.

Others would need to opine but I think 1 splitter as opposed to daisy-chaining 2 would be better...especially if TV screens are pixelating.

I've had an Extreme (brand) 2-Way (BDS102H) for about 10 years.  It's been flawless.  It's my Thanksgiving bouncy tradition.

Like

Reply

0

J
JillPill

New Contributor

 • 

9 Messages

Lol I meant the bands on the router, yes frequency. 2.4GHz, 5GHz, and another 5GHz

The router is brand new, literally a few weeks.  These issues were happening before this router which is why I started by replacing my old Netgear Nighthawk XR500 to a new Netgear Nighthawk RAX70. Then I realized maybe it wasn't the router. Then called tech support. That tech wasn't much help but said maybe new modem. So I replaced my Motorola MB8600 with this MB8611.  I like to stick with what normally works good for me lol.

Mouth suggested the Extreme brand that you are referring to. I was just calling it high performace cuz thats what it says in the picture lol.  I thought I did see splitters sold at home depot but maybe I didn't.  If I say Home Depot, he has no issues going lol. We might just order and wait for that "Extreme" one.  January 12 just seems like a long wait to get a splitter through Amazon when I have prime.  I'm impatient!  🙂  I will definitely try the router disconnect and hook the laptop to modem to see what happens.

Like

Reply

0

V

VeronicaDrew

New Contributor

 • 

3 Messages

I had the exact same issue a few months ago (89134) right after they did work to "improve area bandwidth."  Suddenly everything (browsing, watching Netflix and Hulu) was way slower and at the same time I began getting "data overage" for the first time EVER - I have been here 3 years.  It took an FCC complaint to get them to respond and I ended up with their modum and a 2 year contract for a higher speed plan that is not noticeably faster than before, still slower than before their area work to increase bandwidth.  In addition, I continue to hit "approaching data max" and going over  - despite nothing whatsoever changing in what I've always done.  This is really maddening and I know it's not something I'm doing, it's something they've done to drive up profit.  Sorry, I have no solution but you are not alone.

0

0