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 (220.127.116.11) :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 duplicated this trace, and I also see a slight increase in latency at 18.104.22.168 (your hop 5). This is due to normal ICMP deprioritization. Your traceroute hits the Amazon Web Services (AWS) servers at hop 6. The timeouts once the traceroute reaches the AWS server are expected. Not all AWS servers return ping requests; they block ICMP packets for network security reasons. -Becky, Cox Support Forums Moderator"
Becky said this it means nothing to me please fix my issue or tell me what to do because you guys have been avoiding this issue for months and I'm down with this trash.
This is the same run around I've gotten on my thread. Not sure if this has been attempted, but Cox tech support loves to use the "ICMP deprioritization" excuse. Here's a way around that:
Download Ping Plotter - https://www.pingplotter.com/download - and change the packet type to either UDP or TCP. Servers will not deprioritize those packets.
Do set to UDP, in Ping Plotter go to "Edit" --> "Options" --> "Packet" - change the "Packet Type" option to "UDP Packets".
For TCP, you need an extra piece of free software that can be found here: https://nmap.org/npcap/dist/npcap-0.99-r7.exe
Server will not deprioritize UDP or TCP packets as they are used in normal internet communication as opposed to ping (ICMP) which is used primarily for diagnostics and can be dropped as low priority.
I'd use UDP as I've seen the exact same behavior with UDP or TCP packets in Ping Plotter. Funny enough, a normal trace route using ping produces the same exact levels of packet loss and latency, but because ping can be considered "low priority" by hops, it can be easily waved off as expected behavior.
same problem, PLEASE FIX THIS !!!
if you look at my account, ive had technicians come out many times with no fix. and it doesn't happen in everything I play, ONLY fortnite to AWS servers.
I also spent 500$ on top of the line equipment and still same problems :(