It actually is a problem with AWS. I literally talked to a AWS lead network engineer for 4 months to diagnose this stuff, as well as a network engineer at COX. It absolutely is the problem.
To clarify, COX is the perpetrator here - they own faulty hardware which reorders UDP packets to AWS, and then AWS drops them, causing what seems to be "packet loss". Order matters for video games. When the order isn't perfect, fortnite detects this and drops the packets. This is the issue. It is entirely COX's fault.
I have the same issue with packet loss on Google Cloud Server, not just AWS, in fact it happens with any server.
I read your post and I don't fully agree that's the problem, here's why:
If you research this issue, people have been reporting major packet loss in games for over a year with cox. Most of the threads will all say the same thing, like they had been using cox for awhile and no problems, then all of a sudden they start getting hit with major packet loss. Then they will report they have the issue everyday and nothing can be done to fix it.
If it was as simple as the way they reorder packets, then why aren't people having this issue from day one when they sign up for cox? Why are people reporting it starting a much different time frames (1 year ago, 6 months ago, 2 months ago)?
Why did I have perfect ping the first 4 months I had cox (30-40 stable ping), now the last two months I have had major packet loss every single day and my in game ping won't go below 80?
Your telling me they switched internal equipment in the last two months? I don't buy it.
I'm not saying there may be some truth to what you say, but there is no way thats the main issue for most people. The time frames don't support this theory.
To further this, when I play a game thats hosted on AWS and get packet loss, I will also have packet loss on Discord at the exact time. That's two different servers having packet loss at the exact same time, AWS/Google cloud.
The packet loss is real and it's a cox issue.
I completely agree with this.
