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.
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
Based on the traceroutes and ping results, both of you provided, it appears that Cox is peering directly with Amazon. Therefore, the issue likely lies with Cox and/or Amazon.
silverapple42, are you indicating that you have enough speed through your T-Mobile hotspot to play these online games without issue? If so, would you share the traceroute when using the hotspot?
I also have T-Mobile and when I use a hotspot there is no packet loss. Unfortunately, that comes at the cost of higher ping. The route is completely different https://imgur.com/a/CUeH8tG .
