Read the forum guidelines
UPDATE - I suspect this packet loss issue may be fixed very soon. Maybe within the next week. That's all I'll say for now - I'll update again soon
Yep, another AWS packet loss post. Have none of the past customers with this issue had their problems actually resolved?
I'm consistently getting 0-10% packet loss to Amazon web services (both west and east servers) making fortnite unplayable. No, I do not have this problem with other games I play as they do not use Amazon web services to host their servers. This seems to be an issue with the path cox routing takes to AWS servers.
my cox tracert to AWS west (oregon): https://textuploader.com/dzw7o
my cox tracert to AWS west (188.8.131.52) :https://textuploader.com/dzw7g
my cox tracert to AWS east: https://textuploader.com/dzw70
my tethered AT&T iphone to AWS west: https://textuploader.com/dzw76 - interesting how AT&T LTE is a legitimately better connection to AWS than vegas's "best" ISP
No I'm not using a puma 6 modem. I have the cisco DPQ3212.
puma 6 test anyway: https://imgur.com/a/iKR9PYY
I've already troubleshot by hardwiring to modem directly with the same results. I've unplugged the power on router and modem (although it stays on) numerous times, as well as coax.
Here's a tracert of another cox customer with the same exact problems: https://pastebin.com/index/ehaQBYEd
and another: https://pastebin.com/Qqfxa5UN (there are many more tracerts exactly like these; it also seems like we're all dropping packets at the exact same servers)
now here's a tracert of a cox customer in phoenix (to AWS west) who has 0% packet loss: https://pastebin.com/MX1GfGPC
A reddit thread furthering the evidence that this is explicitly a cox issue and not a personal one: www.reddit.com/.../
I would appreciate real effort in getting this resolved - I know I'm going to be told this is a personal issue when it obviously simply is not. Thanks in advance
I HAVE COME TO THE END OF ROADS WITH COX AND THEIR SUPPORT...
It is a verifiable problem that many cox users experience data loss at 1% or more on their favorite and most popular game FORTNITE!
After speaking to the highest corporate level of escalation as in nothing can GO further than that....
THEY SAID THIS AND I ASKED IF I COULD QUOTE:
"WE DONT COVER ONLINE GAMES TO CLOUD BASED SERVICES"
UMM EXCUSE ME ONE OF THE ONLY REASONS PEOPLE GET INTERNET IS FOR ONLINE GAMING...IS THIS A JOKE?
THEY THEN INSTRUCTED ME TO REACH OUT TO AWS AS THEY AREN'T COGNITIVE ENOUGH TO HAVE THEIR BILLION DOLLAR CONNECTIONS DO IT FOR US!
SHE PRETTY MUCH TOLD ME THERE ISN'T ANYTHING THEY WANT TO DO AND THAT IM OUT TO FEND FOR MYSELF ON THE ISSUE.
This is after thousands of cox customers posts around the internet and many verifiable and documented instances of packet loss using default pathways to AWS applications.
AN ISSUE THOUSANDS OF COX CUSTOMERS ARE EXPERIENCING ALL AROUND THE NATION ON THE MOST POPULAR GAME IN THE WORLD AT THE MOMENT!
AS OF 12/26/2018 MANY COX CUSTOMERS ARE EXPERIENCING ISSUES WITH AWS PLATFORM SERVICES AND COX ISN'T THE TYPE OF COMPANY TO FIX SOMETHING THEY HAVE A DEGREE APART OF.
ANOTHER TAKE AWAY IS THAT COX AS OF 2018 DOESN'T HAVE A SYSTEM TO TROUBLESHOOT PROBLEMS IN AN ACCORDINGLY FASHION AND DUMP MANY OF THEIR OWN NETWORK ISSUES ON TO CUSTOMERS WHO INDEED DONT HAVE THE RESOURCES TO TRULY GET TO THE BOTTOM OF IT. Its literally a real life scenario of finding a needle in the haystack which in return decreases performance in diagnostic measure and spawns an atmosphere of a company that can't even troubleshoot themselves.
SPEEDIFY AS of 12/26/2018 FIXED MY PACKET LOSS PROVING IN PHYSICAL REALITY THAT THE DEFAULT PATH SERVED TO ME DOES INCUR DATA LOSS.
Executive Summary of entire problem:
-4+ techs to apartment who all said onsite problems were resolved
-BLANKET OF PACKET LOSS @ 1% - 5% ON FORTNITE STILL PREVALENT
-Speedify fixed packet loss and proves default path incurs data loss or there is an apparent problem
-lots of posts around the web that also share the same symptoms on the most popular game at the moment
AS IT SHOULD....WHEN A NEW USER GETS COX THEY SHOULD HAVE NO PACKET LOSS TO ANY SERVICE....right now you're executive escalation team even reassured me that you don't want to give a helping hand and that this issue isn't to a degree related to your service when indeed you do have a play in this problem
The problem is the way you handle power users who are more educated then 90% of your employees. You act in a condescending way that paints a Utopian side for you that in all universes Cox won't be the one to blame when it actually hurts your stance even further. A company that wishes to not acknowledge and leave many customers unanswered is one that needs a different managing team altogether. Maybe your board should be voted upon and have people that do understand the need for online gaming.
A company that fails to acknowledge abnormalities and decides to ignore creates a resenting base of consumers who know they have true issues with the services they're served.
And the sad thing is this is over a free to play video game...they literally will keep you in a nonstop loop of diagnosing when in reality it is out of LAN's
Unfortunately as this issue isn't resolved and all I use my connection for is online gaming specifically using fornite I'm going to have to document all of the findings around the internet and create a video to solidify our stance as consumers being forced into default paths that incur data loss.
At this point I feel as if cox will get this fixed behind the scene and one day ill wake with no packet loss and all of these posts would be considered irrelevant right. Wrong as of 12/26/2018 I have been experiencing packet loss on fortnite for months now !
The fact is is that the cox executive level stated they CANNOT BE COUNTED ON TO PROVIDE A DEPENDABLE CONNECTION FREE OF PACKET LOSS TO FORNite...if you're a fortnite player and you hear this that's more than enough to turn you away! or sure the service will work for many but if your in those select few we could give a hoot about you because are revenues allow us that! If you're one of those few we can't do anything more and you go contact the server platform we serve millions of connections to as we don't want to be bother with this. Your pr is just not cognitive enough to understand this 2018...