Read the forum guidelines
Hey all, for those unaware, explanation of issue at end of post.
Many of us are struggling with extreme amounts of packet loss through COX, we need to come up with some sort of plan for action.
Some ideas (And I’m completely serious here):
Coordinate time to peacefully protest at their corporate office
As a group, continually post on their forum
Anytime a COX truck is seen, pull up and chat with the techs to remind them of the issue (individual rather than group task)
Coordinate FCC complaint for viral effect
Class action lawsuit (Does anyone know if we can sue considering repeal of net neutrality laws? It is clear that COX is violating their own prerogative of following the old rules)
I’m sure there are many competitive gamers on COX who would coordinate with us. Any Amazon AWS game experiences this packet loss. Additionally, many of us don’t have the option of switching ISPs.
This issue has been ongoing for roughly a year with no signs of being solved. This issue is affecting MANY players.
Very interested to hear your thoughts
Explanation of issue: Most COX Com subscribers experience massive amounts of upstream packet loss while playing games that use Amazon’s AWS servers. One of the most notable effects is (in Fortnite) often times your first shot with any shotgun does not register, however, you see the hit marks. Roughly ~1/8 of shots don’t register. The issue has been ongoing for a year, and COX has shown no effort to solve. They’ll charge you $70 for a tech to come out who can’t diagnose the problem (as the problem is deep within COXs routing mechanisms). Competitive gaming on COX is extremely discouraging, and many of us can’t switch ISPs for whatever reason (bandwidth etc).
Epic has found what the issue is!!! Spread the word, they are looking to have it fixed with the 8.1v update. Fingers crossed
Happy about this.Will say though, kinda sad Epic is having to change their coding because COX can't provide a stable connection to Amazon EC2
I was excited for this recent uldate but it was 8.01v not the 8.1v we are waiting for! Ill be back here when that update gets pushed out