CAN'T FIND THE ACTUAL ISSUE

You need to rule out problems one at a time:

• Troubleshooting your own equipment is on you but it sounds like you've done that.
• Next you need to determine if your physical connection is working properly. That involves signals and logs.
• Then, only if you have determined that the physical connection is working, you can explore the possibility of node saturation.

It sounds like your physical connection still has some issues. Noise and "hum" will cause problems. "Hum" is just a name for a certain type of noise. You will also hear names like "ingress" or "backfeed". These are different names for the same general problem. Understanding these words won't help you solve your problem. Knowing precisely which one it is won't help you solve your problem. There's no question you can ask about these words that will help you solve the problem.

If you have uncorrectables on your downstream signal screen, that's a sign of high frequency noise and/or ingress. You can't fix this and you can't ask any questions that will help you fix it. Only Cox can fix this. But you can show them the signal screen to help them know what frequencies to look for the noise on. For example, look at my signals:

My connection works perfectly because I have no uncorrectables after over a week of uptime. IMHO, a continually increasing number of uncorrectables always indicates a major connection problem. Every now and then (less than twice a month) you might see a brief spike when something is disconnected for maintenance overnight. But if uncorrectables are growing and growing, your connection is no good. Cox probably considers a certain number of uncorrectables to be acceptable because no ISP can afford to keep all connections 100% perfect all the time. But to me, uncorrectables are never acceptable.

You can learn a bit about my connection from these signals. For example, you see some correctable errors on all of the mid-frequency (700-900 MHz) channels. That means that the connection isn't quite perfect in that band. Something is letting in a tiny bit of noise in that whole frequency band but it's not causing me any problems at all. However I will keep an eye on this because if those numbers start growing at a faster rate it means the connection is degrading and might go bad eventually.

On the lower-frequency channels, you see it's almost perfect with one exception. You can see that right around 381 MHz, there was an incident where a small amount of noise came in on that frequency range. It was definitely caused by something outside my home, but it didn't cause me any real problems. Like before, I can keep an eye on it to see if it starts getting worse or if it starts to cause uncorrectables.

You can analyze your downstream signals in the same way to determine if you're getting noise all across the band or if it's isolated to a small frequency band. Let your modem run for at least 3 days without resetting it so you can get a proper picture of the error rate. But learning this won't help you solve the problem. There's nothing you can do to solve the problem.

If you have Dynamic Range Window violations in your modem logs, it means you have some noise on the low-frequency upstream channels but it's mostly harmless.

If you have T3 timeouts in your modem logs, it means there is problematic noise on the low-frequency upstream channels and you will have packet loss. You can't get as much detail about this as you can on the downstream. All you can do is know that the noise is on the upstream. You can't fix this problem.

The possible causes of noise, ingress, and backfeed are too long to list. It could be any of hundreds of different things. No matter how many questions you ask, you won't be able to figure out what it is. Only Cox can figure it out. And it might be very hard for them to figure it out since it could be hundreds of different things.

Once you get your connection so that it has no uncorrectables and no T3 timeouts, only then should you use PingPlotter to isolate potential node congestion. But even if you determine that the problem is node congestion, there's nothing you can do to fix it. Only Cox can fix that.