Extreme Packet Loss Recently
Me, and many others have been receiving excessive packet loss in Fortnite servers located in US-West which I believe is hosted on Amazon EC2.
I've contacted Gigablast multiple times and they are of...
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.
Hi Jrdn, thanks for posting these. Your results seem to follow normal ICMP prioritization protocols. The timeouts once the traceroute reaches the AWS server are expected. Amazon Web Services servers don't return ping requests; they block ICMP packets for network security reasons. We request trace routes because we're looking for issues along the path to the AWS server that may indicate an issue on the Cox network. Our investigation is ongoing. -Becky, Cox Support Forums Moderator
Please fix this asap, it's been going on for months and only now are people bringing light to it.
You're ruining the experience for soo many people
The connection issue also occurs in Playground mode in which you do not connect to any other people, just the server. Just putting this in so you guys don't think the issue is a connection between the players.
- Hi Cox User, please post several traceroutes to the specific game server so we can take a closer look at what's happening. -Becky, Cox Support Forums Moderator
Hello. These traces were to IP's I saw online. I just ran wireshark to get the server ip and was getting 20-40% packet loss on this instance:
1 2 ms 4 ms 2 ms 192.168.1.1
2 8 ms 9 ms 8 ms 10.162.0.1
3 9 ms 8 ms 8 ms 68.6.14.78
4 8 ms 8 ms 13 ms 100.120.108.8
5 15 ms 12 ms 12 ms 68.1.1.167
6 * 40 ms 49 ms 52.95.218.216
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 20 ms 21 ms 20 ms 52.93.70.180
14 21 ms 19 ms 21 ms 54.240.242.63
15 43 ms 43 ms 48 ms 72.21.222.222
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 46 ms 47 ms 49 ms ec2-54-219-187-166.us-west-1.compute.amazonaws.com [54.219.187.166]According to PingPlotter with this IP, at over 125 tests, Google.com gets 19.4% packet loss, and the Fortnite server is around 18%. akamai.com , cox,com, yahoo.com , pingplotter.com , twitter.com , Level3 all get 0 packet loss:
Ping Plotter Summary of the Fortnite Server:
Target Name: 54.219.187.166
IP: 54.219.187.166
Date/Time: 9/8/2018 10:04:06 PM - 9/8/2018 10:14:06 PMHop Sent PL% Min Max Avg Host Name / [IP]
1 146 78 0.18 1.03 0.55 192.168.1.1 [192.168.1.1]
2 151 0 3.85 34.86 8.71 10.162.0.1 [10.162.0.1]
3 151 0 6.63 18.40 9.42 68.6.14.78 [68.6.14.78]
4 151 0 6.27 74.75 12.02 100.120.108.8 [100.120.108.8]
5 151 0 8.07 69.45 15.27 68.1.1.167 [68.1.1.167]
6 151 13 27.05 59.25 40.21 52.95.218.216 [52.95.218.216]
7 150 100 0 0 0 [-]
8 150 100 0 0 0 [-]
9 14 7 20.09 26.02 21.32 54.239.42.143 [54.239.42.143]
10 150 100 0 0 0 [-]
11 14 7 19.76 29.42 21.74 54.240.242.58 [54.240.242.58]
12 150 100 0 0 0 [-]
13 12 25 35.51 41.98 37.43 52.93.47.131 [52.93.47.131]
14 13 0 19.75 32.53 22.04 54.240.242.43 [54.240.242.43]
15 151 0 16.70 52.39 22.27 72.21.222.222 [72.21.222.222]
16 150 100 0 0 0 [-]
17 150 100 0 0 0 [-]
18 150 100 0 0 0 [-]
19 150 100 0 0 0 [-]
20 150 100 0 0 0 [-]
21 150 100 0 0 0 [-]
22 150 100 0 0 0 [-]
23 150 100 0 0 0 [-]
24 151 17 20.10 112.25 41.53 54.219.187.166 [54.219.187.166]Can you take a look into my trace routes (or forward them to the investigation team)? I just got them yesterday while making sure I was connected to a Fortnite server that was suffering from severe packet loss.
Tracing route to ec2-52-71-66-128.compute-1.amazonaws.com [52.71.66.128]
over a maximum of 30 hops:1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms ip68-107-57-129.sd.sd.cox.net [68.107.57.129]
3 1 ms 2 ms 1 ms ip68-101-129-110.sd.sd.cox.net [68.101.129.110]
4 3 ms 2 ms 2 ms visthbrc01-get0702.sd.sd.cox.net [68.6.8.119]
5 32 ms 32 ms 32 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 32 ms 31 ms 31 ms 52.46.167.212
7 39 ms 43 ms 32 ms 54.239.105.121
8 32 ms 32 ms 32 ms 176.32.125.191
9 * * * Request timed out.
10 70 ms 81 ms 69 ms 54.239.46.0
11 66 ms 66 ms 66 ms 54.240.229.189
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 85 ms 106 ms 89 ms 54.239.110.247
16 68 ms 67 ms 67 ms 52.93.26.62
17 83 ms 98 ms 79 ms 52.93.27.205
18 66 ms 65 ms 66 ms 52.93.25.11
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.
Tracing route to ec2-34-235-172-107.compute-1.amazonaws.com [34.235.172.107]
over a maximum of 30 hops:1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms ip68-107-57-129.sd.sd.cox.net [68.107.57.129]
3 1 ms 1 ms 1 ms ip68-101-129-110.sd.sd.cox.net [68.101.129.110]
4 3 ms 2 ms 5 ms visthbrc01-get0702.sd.sd.cox.net [68.6.8.119]
5 32 ms 32 ms 32 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134]
6 31 ms 31 ms 33 ms 72.21.221.202
7 48 ms 51 ms 36 ms 176.32.125.150
8 32 ms 32 ms 31 ms 176.32.125.159
9 * * * Request timed out.
10 70 ms 77 ms 72 ms 54.239.43.206
11 65 ms 64 ms 64 ms 54.239.43.96
12 * * * Request timed out.
13 82 ms 92 ms 78 ms 54.239.111.166
14 63 ms 62 ms 62 ms 54.239.110.182
15 80 ms 87 ms 87 ms 54.239.110.187
16 72 ms 68 ms 70 ms 52.93.25.114
17 * * * Request timed out.
18 66 ms 65 ms 65 ms 52.93.24.127
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.
Tracing route to ec2-34-237-197-55.compute-1.amazonaws.com [34.237.197.55]
over a maximum of 30 hops:1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms ip68-107-57-129.sd.sd.cox.net [68.107.57.129]
3 1 ms 1 ms 1 ms ip68-101-129-110.sd.sd.cox.net [68.101.129.110]
4 3 ms 2 ms 2 ms visthbrc01-get0702.sd.sd.cox.net [68.6.8.119]
5 32 ms 32 ms 32 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134]
6 32 ms 31 ms 37 ms 52.46.167.210
7 48 ms 43 ms 47 ms 54.239.105.99
8 32 ms 32 ms 31 ms 176.32.125.157
9 * * * Request timed out.
10 69 ms 80 ms 73 ms 54.239.46.4
11 66 ms 66 ms 67 ms 54.240.229.217
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 86 ms 78 ms 86 ms 54.239.110.227
16 66 ms 66 ms 66 ms 52.93.26.74
17 69 ms 81 ms 109 ms 52.93.27.221
18 66 ms 65 ms 66 ms 72.21.197.243
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.
- Hi Juices, these traceroutes show normal ICMP deprioritization. The timeouts once the trace reaches Amazon's network are expected, as some AWS servers don't return ping requests for network security reasons. We request traceroutes because we're looking for issues along the path to the AWS server that may indicate an issue on the Cox network. -Becky, Cox Support Forums Moderator
