12/12/2018 UPDATE: COX did send out an engineer aka bucket truck, which I visibly saw doing something, so that's confirmed. I called in later that night and talked to a supervisor, who was awesome, however notified me that the engineer said the problem was resolved.
As I talked to the supervisor on the phone I notified her that I would attempt to load a few games of fortnite to see if the issue was resolved. When i loaded into the games I noticed the constant 1% -3% packet loss.
AND sorry for the caps of exclamation, but the funny thing is that there is a 1% packet loss and then specifically when in moments of high action(high impact on servers) such as in a gunfight it literally in reality lags on the screen just before a player rolls up on you then in game registers that 1% or X % of data loss occurred in the fortnite net debug settings.
So, I explained to the awesome rep who was understanding of the issue that it was still occurring. She then actually told me that the modem levels and cable box levels to my unit specially weren't reading the right numbers.
So, as of 12/12/2018 @ 11;46 PM I'm waiting upon a new tech who will see if he can remedy thy issue as apparently the node work didn't resolve it.
This is my theory: If the new tech fixes all the issues that he's reading and seems to remedy the onsite red flags and I start a game of fortnite up and that weird packet loss is still there, then it HAS to be a systematic issue via AWS services which I recommend as a business student you should remedy before it becomes apparent that you can't even route to a simple free game in 2018 as of 12/12/2018 for over thousands of paying subscribers. If anything many that pay the highest tier you offer.
The above theory obviously could be incorrect as we 're just trying to find the needle in the haystack but if this is system wide for subscribers start acting now.
AND to think back to it, I don't think I had packet loss before I switched to gigablast in JUNE 2018.
IF the tech fixes the issue then I will report the solution as applied to my situation and retract that theory.
I’ve had essentially everything replaced at my home. Trucks out to work on lines and nodes and it never resolved my issue. Cox will just say it’s out of their network and cease to help any further. The problem is Jeff a customer from California doesn’t have as large a voice as Tim in the IT engineering team at cox when trying to contact AWS to resolve the issue wherever it may be. We are literally stuck at a stare down with cox on who’s fault it is and who should fix it when it could’ve been fixed months ago.
