Packet loss, latency on gigablast in Scottsdale, AZ for the last few months

Response from the cox.help e-mail: 

"At this time, our techs are currently aware of a noise issue that is causing packet loss in your general area. Our techs are working on resolving this issue as quickly as possible"

I asked for more info but all I really got was 

" This is a recent issue that was reported. I show we made some changes on the outside to help fix this issue. The escalation is currently still open and there are no updates showing at this time."

and

"For plant-related issues, we do have to get a tech out to verify the service from the home to our plant. They usually escalate the issue over to the plant group. We do have a group that monitors the plant as well and may open a ticket if they do see an issue going on in the area. Sometimes if the issue is intermittent, it may be hard to find as well."

I'm not sure what they mean when they refer to a "plant", but I'm guessing it's referring to a node or a set of nodes

It's not just AZ its in So Cal as well. I've sent a couple of emails to cox.help with detailed trace routes with other info and game logs but have not got a reply. Just a bunch of lip service on the forums.

I'm in what seems like the same boat (at Scottsdale/101.)

Could be worse.  I had support asking me whether I was on 2.4ghz or 5ghz after clearly stating, twice, that my computer was plugged directly into the cable modem for testing.  =)

I haven't had many issues in the last few years, if any really, but over the last week I noticed that there was sufficient packet loss that the monitoring/auto-reboot functions of my Ubiquiti network were triggering cable modem reboots to try and fix itself.  I initially chalked it up to Ubiquiti's latest gizmo being a bit buggy, but it still triggered on the 20th, 21st, 22nd, and multiple times on the 25th.  Simple video streaming of Youtube TV became a buffer nightmare, remote access to my home network got sluggish, and I noticed packet loss on continuous pings to google.com and 8.8.8.8.  (Losing about 4-8% now.)

There have been zero changes to anything between the cable modem and the outside world (barring anything out at the street, who knows) and it's just been a gradual downward slope into oblivion.  Today, I can still hammer out almost 700mbit down, but upstream is 2.41mbit.  That's a kinda massive problem.

Just for giggles, I even did a full reset on the SB8200 (little reset button + paperclip) and let it do it's thing.  Still managed to bring downstream online at docsis 3.1 (blue light) but upstream remains 3.0 (green light.)  I honestly have no idea if thats always been that color scheme, or if upstream should also run blue/3.1 (maybe not since it's only supposed to be 35mbit anyway?)  Regardless, the service is pretty much unusable at this point.

After dealing with the *** in chat who couldn't figure out that hardlining via ethernet used neither of the common wifi bands, and trying to sell me on 'advanced support' for $10/mo, I did speak with a support rep on the phone (is it bad that I still have 623-594-1000 memorized from back in the Cox@Home days?) and they actually did show an outage/issue in my area.  The Cox app and ensuing sms alerts just before that corroborated the story.  Unfortunately that has since cleared and things continue to degrade.

I also took a look at the modem's status page and while I deal with networks and IT for a living, the channels and signal levels it reports might as well be Greek to me.  Nothing pops out as an obvious issue, other than the lo screen showing something about some 'dynamic range window violation' repeating a few times.  (Lots to see about that on google, but nothing useful so far.)

In any case, packet loss begins immediately after leaving my network, so the issue would appear to be between the cable modem and the upstream connection at Cox.  No luck getting past the script-reading support types to actually take action on any of this though.

Update since I noticed a ton of packet loss during my latest game of Rocket League tonight around 845pm. The overall issues started earlier, around 815, but really spiked just now.

https://drive.google.com/file/d/1le6wom285a8v4y6hUM5cVp4dAflpdv7u/view?usp=sharing
https://drive.google.com/file/d/1WcfRKabdOwHEPcGC_8L2JTbS2S6OW-o7/view?usp=sharing

I have been experiencing this same exact issue over the last several months in Mesa, AZ. I have had 5 techs come out and they did various things but still the issue persists.

All the traceroutes I run are garbage and show incredibly high spikes on local cox nodes. Problem also tends to get worse around 5pm AZ time.

It is impacting work for me and my wife and there does not seem to be any solution in sight. Gaming is nearly impossible with the high packet loss all day long. I don't know what else to do at this point. 

One last update since it's happening right now: stream quality on Twitch with "auto" quality, i.e. the setting that downgrades the picture if your Internet isn't handling the traffic for higher qualities
 https://drive.google.com/file/d/15f2FELVzqs1V6YzD2ti0iYjugW2NudDY/view?usp=sharing

I should note that this causes problems for me beyond just gaming. I've seen huge drops in quality from streams [1], and I often drop in and out of voice meetings for work (and working from home means that's a problem)

[1] drive.google.com/.../view

Just took a quick sample from my latest Rocket League logs for a server from the west coast:https://drive.google.com/file/d/1-NMfPxBlck3ojUE9KdaWpx3krXlI3rBe/view?usp=sharing

That 68.1.0.191 IP sure seems bad, let's see who owns it via WHOIS IP Lookup Tool | UltraTools...