Forum Discussion
Here is a tracert to the AWS West :
Tracing route to ec2-52-42-109-244.us-west-2.compute.amazonaws.com [52.42.109.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms 10.169.0.1
3 18 ms 14 ms 13 ms 68.6.14.54
4 22 ms 7 ms 8 ms 100.120.108.26
5 14 ms 12 ms 12 ms 68.1.1.167
6 12 ms 21 ms 11 ms 52.95.218.216
7 35 ms 20 ms 32 ms 54.239.102.18
8 46 ms 15 ms 15 ms 54.239.102.27
9 37 ms 36 ms 36 ms 54.239.42.122
10 * * * Request timed out.
11 66 ms 72 ms 53 ms 52.93.12.162
12 36 ms 37 ms 41 ms 52.93.12.145
13 54 ms 55 ms 76 ms 52.93.12.36
14 36 ms 39 ms 36 ms 52.93.12.59
15 38 ms 42 ms 42 ms 52.93.240.59
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Look sketchy or anything lmk?
- Becky6 years agoModeratorHi RomanPat, your PingPlotter video and traceroute seem to show normal ICMP deprioritization. Some servers may specifically block or down-prioritize ICMP echo requests. Corresponding traceroute hops might show 100% packet loss, or high packet loss and latency. You can tell it is just a case of the server in question taking its time to respond because true packet loss would impact all the remaining hops. The only hop that matters is the final hop. If the final hop is showing 0% packet loss and acceptable latency, then all the hops before that can show all kinds of errors and it doesn't matter. We know that some AWS servers block ICMP requests for security reasons, so the timeouts once the trace reaches the AWS network are to be expected. Your traceroute hits the AWS network at hop 6 (52.95.218.216). The traceroutes show no issues on the Cox network. -Becky, Cox Support Forums Moderator