Read the forum guidelines
My original thread about this was locked with no reason, and after multiple Cox technicians and calls I am still receiving extremely bad packet loss on the upload side only. Mainly to games that use Amazon AWS servers. Anybody from Cox or community members able to help me?
Original thread -
Hello, I have been a Cox Customer for 17 years and a few years ago I started having very bad packet loss issues. I have spent hundreds of hours trying to fix this issue but it still happens even years later. I am only receiving packet loss (upload), 0% download packet loss. I am receiving low ping (for the most part) (30-40ms) and high packet loss (10-120%) in games such as Fortnite, Overwatch, Rocket league and more. It is happening on my PC & PS4. I have tried pretty much every solution you can think of.
(I am hardwired directly to the modem with Ethernet as well)
This is a Cox issue as I used a TMobile hotspot and received 0% packet loss so it can't be anything on my end. At least I don't think so.
Hey, I have this same issue. Have had 2 techs out and they have been unable to resolve the issue. I am on the westside of Arizona
Perhaps you could try running a traceroute to the IP of the server. Then, with that information returned from the trace route, start pinging the closest hop with about 100 pings using 512-byte packets and then continue to the next hop, etc until you start to see packet loss. Maybe, this could help to identify where the bottleneck is. Good luck.
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, 126.96.36.199. 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?