Forum Discussion
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
- BooPacketLoss7 years agoNew Contributor III
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.
Related Content
- 7 years ago