Extremely bad packet loss and service outages

Technician came early and I presented him with the information you guys pointed out to me. While testing the line he could not see any problem at that particular moment however he did acknowledge the antiquated NIU, the horrible wiring job, and the unnecessary splitters. He cut down a lot of the old wiring and replaced them, replaced the entire NIU and replaced the fittings on every cable. He mentioned that having the ground exposed is not really ideal but typically wouldn't be causing the issue I'm experiencing so he left that alone.

Whoever installed all of this wiring originally seems to have not cared about it "being up to code" and just installed it however they liked.

He also came inside and tested the line from the inside at my desk. He could not get a signal at all through my indoor coaxial cable so he replaced that as well. Before he did so though he also tested straight through the cable jack and that seemed to indicate things were fine. He did say that if the problem reoccurred to check the attic (where the cables pass through) to see if there were any more unnecessary splitters leading to my jack and he gave me a piece to replace said splitter with instead. If the problem reoccurs and there is no splitter or replacing the piece doesn't work, I was advised to call back and they would probably just run new lines.

Overall, he couldn't explain to me why the outside wiring was done the way it was outside of the person who originally did it being lazy or not caring, especially when it came to running the cables directly along the power lines from the junction box into the house, which he also fixed so they are no longer in contact with each other.

The SNR  for the OFDM PLC on the modem signals page is apparently a false reading. The current firmware I'm using is apparently notorious for showing the SNR on that channel as much lower than it actually is. I know there are newer firmware versions available but so far cox has not pushed an update to my modem which is presently on 8600-18.2.9.

In any case I left WinMTR run again for a good long while and took another snapshot of my signals pages. The odd (false?) reading on the OFDM channel aside, everything seems to be working perfectly now. If things go awry again later this evening, I will update this post again just for reference and in hopes of helping other people figure out what might be happening with their connections as well.

Tremendous thank yous to WiderMouthOpen and Bruce for helping me figure out what was happening here and how it should be addressed! Thank you to the Cox Technician Mel who went above and beyond to try to help remedy the problem in the field!

Here are my readings as of now, let's hope it stays this way: