T3 Timeout Disconnects on the hour. Dead-end problem?

It all began when I registered for Cox service. Having jumped ship from AT&T's DSL, the speeds were out of this world, but the consistency left something to be desired. And it got worse, day by day. Eventually push came to shove and I decided that tech support was necessary. The tech, as most techs do, took a look at the signal levels, concluded they were fine, and insisted that the error lied between the modem and the device - that is, in the router. So at his behest, I replaced my router, and of course, it didn't do anything. Although I will admit that the constant timeouts started happening much more frequently in the day, and almost never by night. Not a complete loss - those closest to me would describe me as a vampire anyways (sparkles and all).

But waking up at 1800 hours, streaming on twitch until the crack of dawn, it takes a bit of a toll on your body. But my own visceral health was less of a concern than the ailing condition of my cable modem connection, which too began to shift.

Let's talk a bit about the previous cable modem I had from Cox. Make: Cisco. Model: DPQ3212. A modest chunk of black molded plastic, very innocuous-looking. Looks can deceive, of course; and I suspected that this black box was the source of my woes. To further fuel my half-enraged, half-annoyed psyche, the DPQ3212 did not come with any sort of diagnostics logs. So goes the adage, "it's always the quiet ones," and if the DPQ3212 didn't want to talk, it had to go.

I instated a new modem - a Netgear CM500. After following the steps with a Cox rep to formally induct the CM500 into Connectory Office, I trembled with anticipation at the consistency I would soon embrace. No more being dumped to Low Priority Queue or ripping to Standard League because Cox decided that now would be a good time to take a five minute breather. Oh, how naive I was, how full of ecstatic hope I was. The truth was that the new modem didn't do much.

Well, I have diagnostic logs now at least to back up my claims.

Armed with new information, I decided to call up yet another tech. I demonstrated the logs, the T3 timeout errors, every little piece of data I could scour. Still, the tech claimed the "signal levels are fine" and took a look at the junction box. A few minutes later, he came back with some startling news - the cable had been slightly crimped, and could be causing the intermittent errors. What's more, it seemed to be the solution - the problems didn't manifest! Haha, just kidding. Two hours after the tech left I started having the same problems again.

I've searched the World Wide Web (and by that, I mean the first few pages of Google results on "Started Unicast Maintenance Ranging - No Response received - T3 time-out"), and despite finding many people with this very same issue, it seems like 98% of the cases are unresolved, or their quandary was somehow solved and they never came back to report how. It's seriously frustrating me to no end. As a Twitch streamer/YT content producer, these constant timeouts are taking huge cuts into my productivity, not to mention my sanity. If there's any more information you require, please ask. I just want this problem to go away. And if it won't, then I will, back to AT&T.