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 (184.108.40.206) :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
This is still an ongoing issue just FYI if keeping up with this thread. I have a thought to why this is happening, but I think I am close to finding proof to my idea.
I believe this is solely on C.O.X to fix.
So I have both a Mac and Windows computer I can run some tracert/traceroutes from to the servers and the reason C.O.X will push this issue off as not their problem is because they say once the data leaves their server it is not their problem any more, but the only data you can really provide from Windows is a simply tracert which will use ICMP data. If you run these tracert using ICMP data there is no data loss from you to the servers and this is what C.O.X gets sent by most people experiencing this issue and they will just dismiss it. If you have a Mac or a Linux machine though you can run a traceroute with the specified data type as UDP. If ran in succession with the amount of data being 60 packets per second and with UDP after running the command about 4x you will see in one of those a dropped packet or no response for the latency of how long the data took to send. These drops are happening BEFORE they reach the C.O.X server that is sending the data off to Amazons servers. This is after testing this just a little bit ago and want to run some more tests. If this is the case it will be on C.O.X to fix this issue. A couple of thoughts to why this is happening now and did not happen before June of 2018. Cox is has probably changed the way they treat UDP data possibly, only problem is no other online games ex. COD BOPS4 seem to have this packet loss issue unless they are, but you can not actually tell or you do not get that information from the network information section of COD BOPS4. It could be possible that the game itself is set to only send out so much information going up that the data is under the capped rate C.O.X is setting on their networks to have going out. If you notice when you connect to a VPN service and run the game through this your packets per second going up change to a much lower number and you receive no loss, just higher ping. Also if you notice streamers pushing over 100 packets per second going up to the Fortnite servers have no problem with packet loss, so I do not believe this is an issue on Amazon's servers.
In conclusion, back in June of 2018 C.O.X probably changed something to how UDP data is being handled when going out.
If that is not the case then I believe around that time Fortnite went from 30mhz to 60mhz on their servers and I m not sure if that means at what rate data is being sent out, but I believe it does and that would explain why this is when this all started to happen. I also think around that time is when we received the ability to see the network debugging statistics on Fortnite and it could have been happening before this, but I doubt it since the blank shotgun hits were not always happening.
Anyways that's the ideas I have came up with after looking from all the different forums from C.O.X and Fortnite. I will be running some more tests to see if I can nail it down to only Amazon servers receiving the packet loss on upload or if it is any other online games or sites. If its any site receiving packet loss like this and the results still show the drops happening before C.O.X server it is on them and I will be giving their techs all this information which if they try denying that then it is to the FCC to file claims.
If anyone else has a mac or linux machine they can run some tests with also, and come up with the same findings please call C.O.X tech support and lay into them to have the issue fixed and if they do not file FCC complaints.
It is time this is fixed.
I noticed this began around the same time you mentioned. I moved in June and assumed it was my new address. I've moved again since then and its still an issue so i believe you're onto something with that June date. Game is horrible you can't even play. Cox is garbage for allowing this and dodging the problem.