Forum Discussion
brianm Here are 3 trace routes for various locations:
1. tracert 52.42.109.244
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 5 ms 7 ms 10.162.0.1
3 7 ms 8 ms 7 ms 68.6.14.76
4 7 ms 7 ms 8 ms 100.120.108.6
5 13 ms 12 ms 13 ms 68.1.1.167
6 11 ms 11 ms 12 ms ip70-167-151-90.at.at.cox.net [70.167.151.90]
7 14 ms 31 ms 21 ms 54.239.102.20
8 12 ms 11 ms 12 ms 54.239.102.27
9 37 ms 45 ms 37 ms 54.239.42.120
10 * * * Request timed out.
11 61 ms 72 ms 47 ms 52.93.12.124
12 36 ms 36 ms 35 ms 52.93.12.111
13 39 ms 37 ms 39 ms 52.93.12.182
14 38 ms 36 ms 36 ms 52.93.12.209
15 61 ms 37 ms 38 ms 52.93.15.217
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.
2. tracert 52.15.247.160
Tracing route to ec2-52-15-247-160.us-east-2.compute.amazonaws.com [52.15.247.160]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 6 ms 7 ms 10.162.0.1
3 6 ms 8 ms 9 ms 68.6.14.78
4 7 ms 8 ms 8 ms 100.120.108.8
5 37 ms 37 ms 36 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 38 ms 40 ms 39 ms 72.21.221.204
7 93 ms 88 ms 103 ms 176.32.125.200
8 79 ms 89 ms 77 ms 176.32.125.243
9 * * * Request timed out.
10 76 ms 81 ms 79 ms 178.236.3.187
11 77 ms 79 ms 98 ms 52.93.128.186
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 83 ms 86 ms 85 ms 52.95.1.150
16 76 ms 76 ms 77 ms 52.95.1.161
17 82 ms 83 ms 79 ms 52.95.1.244
18 77 ms 78 ms 77 ms 52.95.1.225
19 77 ms 77 ms 76 ms 52.95.3.138
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.
3. tracert ec2-54-70-204-128.us-west-2.compute.amazonaws.com
Tracing route to ec2-54-70-204-128.us-west-2.compute.amazonaws.com [54.70.204.128]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 10.162.0.1
3 8 ms 7 ms 13 ms 68.6.14.76
4 7 ms 7 ms 21 ms 100.120.108.6
5 12 ms 12 ms 11 ms 68.1.1.167
6 12 ms 11 ms 13 ms ip70-167-151-90.at.at.cox.net [70.167.151.90]
7 * 43 ms 29 ms 54.239.102.56
8 12 ms 10 ms 12 ms 54.239.102.63
9 36 ms 37 ms 36 ms 54.239.42.120
10 * * * Request timed out.
11 54 ms 54 ms 54 ms 52.93.12.88
12 35 ms 38 ms 41 ms 52.93.12.75
13 38 ms 48 ms 39 ms 52.93.12.182
14 56 ms 53 ms * 52.93.12.203
15 37 ms 35 ms 39 ms 52.93.240.51
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.
- jrdn7 years agoNew Contributor II
Sounds good becky. I just ran the traceroutes on the same IPs from the ones in this thread. Last night, I played for about two hours and had two to three games with packet loss which is the opposite of what happened prior. I'm not sure how to get the IP of the server I'm experiencing packet loss on.
- Cox_User_Who_Ne7 years agoContributor
Can we get an update on to how many more months it's going to take to fix this.
- 402PrimeTime7 years agoNew Contributor III
Great Becky! Bet you don't game! Bet that investigations going well! Bet you can't provide any real updates! Bet you can't explain why I get zero packet loss hot spotting through my phone but the minute I plug your service in it all comes right back! Bet you can't help the cause much! Please, prove me wrong! Escalate the issue, write an internal email, make an actual difference!
- Becky7 years agoModeratorHi Everyone, we have been in constant communication with our network administrators since folks began posting about latency and packet loss issues when playing games hosted by AWS. The issue was initially traced to a line card. The line card was being overloaded during peak hours, resulting in packet loss. The line card was replaced on 9/3/18. Since then, our network administrators have reviewed routing protocols and run hundreds of traceroutes, MTRs, pathpings, and looking glass routing queries. They have found no route anomalies or increased latency at the hand-off point to Amazon. -Becky, Cox Support Forums Moderator
- 402PrimeTime7 years agoNew Contributor III
Well I'd get another team together and go back to work, because the dates and outcomes you mentioned are not consistent with what we continue to experience as customers. Last night my connection was all over the place and that remained unchanged until I hotspot to my phone.
Related Content
- 7 years ago
- 6 years ago
- 4 years ago