STILL Packet Loss For Over a year in games (Fortnite, Overwatch, Rocket League, etc)

I am on the East, but yeah multiple people are having this issue unfortunately.

Amazon Web Services servers don't return ping requests due to them blocking ICMP packets to prevent DDoS attacks, so that testing is unreliable. COX denies that this is their problem because there is no packet loss up to the point of the Phoenix server, 68.1.1.14. The packet loss occurs somewhere after that point. But this happens to so many COX customers in the Southwest, and has been happening to me for nearly a year. From my limited knowledge, I have to say that the "routing tables," or whatever controls the path our connections take to these AWS servers, is completely messed up.

Yes, I wouldn't be at all surprised that ICMP requests are blocked from the AWS Servers for the very reason you mentioned.  However, that doesn't negate the validity of isolating the point of network congestion which likely occurs en route to the servers (i.e. Level 3 backbone).  Hence, my suggestion for performing a traceroute, then perform pings to the visible hops seems feasible in trying to get a handle on where the packet loss seems to be occurring.   Would you not agree?

With enough people performing this type of testing, a consensus could likely be formed as to the point(s) of failure.  For example, is the bottleneck between the Cox backbone and the Internet backbone or is the problem somewhere out on the Internet backbone (i.e. Level 3)?  I hope I'm making sense.

Going to be honest, not really sure what you guys are talking about since I am not a networking genius but I have tried I feel like everything in the book. Here is a tracert to Amazon AWS servers though (Fortnite) - https://imgur.com/0h1rSqE

The last COX technician I had out suggested that I get in contact with Amazon Web Services after replacing my line had no effect on the packet loss. I paid AWS $30 to access their tech support, but they ended up being no help either and said that my ping tests didn't show where the problem was occuring. Here is a PingPlotter test from today, https://imgur.com/a/0zZasP3 . Taking it at face value, I thought something was happening before hop 9, 54.239.42.118. When I told that to AWS support, they said that they couldn't help me any further.

The CEOs should be concerned? https://www.reddit.com/r/FortNiteBR/comments/931lrl/attempt_2_at_getting_visibility_most_cox_isp/ The company knows about it, they don't care. As you can see, a member of the company commented on this thread and the developer eventually concluded that the problem is on COX's end. The first place I went to try and address this problem was to the game's forums and through their support system. I didn't receive a single response in 8 months. It's a free game with over 125 million players, they aren't going to address the problems of one ISP.

Are the CEOs and/or upper management present in the discussion you provided the link to?  Has anyone offered more definitive data than ours? The testing you and I performed strongly suggest the problem lies within the 54.239 network at AWS.  Someone is paying AWS to host those games for "over 125 million players".   I seriously doubt the for-profit AWS is providing those system and network resources simply because they feel like being charitable.  The fact that Cox directly peers with the AWS network gives insight into the amount of traffic originating from the Cox network.   We're not talking "small potatoes" here.

I don't play those games, yet I took the time to assist fellow Cox customers in helping to isolate the problem.  It is disappointing that, apparently, you guys are giving up without even attempting to present our demonstrable findings to upper management.  If upper management won't listen, take your case to an arbitrator (i.e. BBB).  For someone who began working in IT WANs when the size of a 19.2 Kbps (not 19.2 Mbps) long-haul modem was the size of a microwave oven, this is disappointing.

Yeah let me just @ the CEO on Twitter really quick. I think I'll stick with filing FCC claims against COX. I like doing that a LOT more.

boopacketloss Just so we're perfectly clear, your reference to contacting CEOs with relevant network troubleshooting data via Twitter and henceforth knowingly filing false FCC claims against Cox when our own testing, together, has shown the problem to be within the AWS network (not even at the point where Cox peers with AWS) in no way reflects my recommendations or suggestions.  My apologies for having wasted your time with mine while selflessly and fervently troubleshooting your problem.   It won't knowingly happen again.

 I already paid $30 to contact Amazon Web Services months ago with the same screenshots, the same tests, and nothing came of it. This information has already been presented to the game company and continues to be ignored. So, if I have to file GENUINE FCC claims that will force COX to lobby on my behalf to the game company, I will. Or switch to CenturyLink as soon as physically possible. It's insane that any individual subscriber has to waste their time on these forums at all, period.

I am still having issues with up stream packet loss in games.  Hard wired, and have verified the problem is not between my computer and router.  However, I suspect the problem might be with a neighbor/node and not with routing, but you can check my previous post for more info.

I had the same thing [If variable rate is on turn that off] that was my proplem no packet loss on fortnite

Variable refresh rate turn that off

Variable refresh rate is a setting for the response time of your TV/Monitor, so that wouldn't help with internet problems at all. I am also still receiving upstream packet loss even after having my personal line replaced and buying a $300 separate modem and router setup after many tech visits. So, I am left to assume that a node split is the only option left for people like us.

nope still getting packet loss even tried turning off variable refresh rate. 

i know the server i was connecting to and getting packet loss on when i did the ping plotter test was located in boca raton FL strange you have it being in same state

https://imgur.com/a/tHHGL0q

Here is an example I'm obviously having an issue with my new modem too but I got the new modem because I was having an issue before 

https://imgur.com/a/xj4ReW7

getting same here still and actual packet loss on cox's end too which wasn't there before