I have the info you requested. What is the best way to send it to you?
Hi everyone, this is still being looked into to see if this is an issue on our end. We recently replaced a piece of equipment on our network that could have possibly caused packet loss between our network and AWS servers that Fortnite uses (for California, Arizona & Nevada customers). Please provide any current trace routes to Fortnite servers and we will forward them to our network operations team for further investigation. Thanks!
Brian
Cox Support Forum Moderator
I have the info you requested. What is the best way to send it to you?
Also, wanted to thank you, Brian, for being the first Cox employee I've encountered who seems to be taking this issue seriously. Could you put us in touch directly with the engineering tech who is working to resolve this problem? That way, you wouldn't need to be our go-between. Thanks again!
As of 10:45 pm PST 9/04/2018
Tracing route to ec2-52-1-4-124.compute-1.amazonaws.com [52.1.4.124]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms noe- Wifi [192.168.1.1]
2 6 ms 9 ms 7 ms 10.34.192.1
3 8 ms 6 ms 7 ms COX-68-12-9-162-static.coxinet.net [68.12.9.162]
4 7 ms 8 ms 7 ms COX-68-12-9-162-static.coxinet.net [68.12.9.162]
5 14 ms 14 ms 13 ms dalsbprj02-ae1.0.rd.dl.cox.net [68.1.5.140]
6 13 ms 13 ms 14 ms 52.95.218.94
7 33 ms 16 ms 33 ms 176.32.124.215
8 14 ms 13 ms 14 ms 176.32.125.231
9 * * * Request timed out.
10 55 ms 51 ms 51 ms 54.239.43.206
11 46 ms 48 ms 47 ms 72.21.222.251
12 * * * Request timed out.
13 60 ms 65 ms 61 ms 54.239.108.188
14 49 ms 47 ms 48 ms 54.239.110.184
15 64 ms 87 ms 66 ms 54.239.110.181
16 45 ms 48 ms 48 ms 54.239.108.131
17 47 ms 47 ms 47 ms 52.93.24.22
18 47 ms 47 ms 47 ms 52.93.24.17
19 * * * Request timed out.
20 * * * Request timed out.
say this is a location in virginia, about a month ago it was only connecting to boca raton florida, don't know what that ip is anymore or if it's even in use anymore.
https://pastebin.com/AMFuwwQV Here are two tests from this morning. I am looking forward to hearing more responses to this problem in the coming days.
I already posted these results in another thread, but here they are again just in case.
Traceroute has started…
traceroute to 52.42.109.244 (52.42.109.244), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 0.566 ms 0.226 ms 0.181 ms
2 10.117.0.1 (10.117.0.1) 6.738 ms 7.038 ms 7.817 ms
3 100.127.73.40 (100.127.73.40) 7.602 ms 7.865 ms 8.311 ms
4 100.120.100.0 (100.120.100.0) 7.664 ms 10.149 ms 8.829 ms
5 langbprj02-ae1.0.rd.la.cox.net (68.1.1.14) 25.165 ms 21.159 ms 21.711 ms
6 52.95.218.216 (52.95.218.216) 20.384 ms 20.269 ms 26.351 ms
7 54.239.102.102 (54.239.102.102) 39.988 ms 29.250 ms 43.874 ms
8 54.239.102.109 (54.239.102.109) 18.713 ms 21.932 ms 24.331 ms
9 54.239.42.118 (54.239.42.118) 49.365 ms 45.187 ms 45.627 ms
10 * * *
11 52.93.12.114 (52.93.12.114) 47.041 ms 57.170 ms 49.561 ms
12 52.93.12.109 (52.93.12.109) 44.979 ms 45.581 ms 45.404 ms
13 52.93.12.144 (52.93.12.144) 87.528 ms 65.235 ms 78.519 ms
14 52.93.12.167 (52.93.12.167) 45.233 ms 45.136 ms 46.575 ms
15 52.93.240.59 (52.93.240.59) 50.181 ms 52.409 ms 54.057 ms
16 * * *
17 * * *
18 * * *
Traceroute has started…
traceroute to 52.42.109.244 (52.42.109.244), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 0.745 ms 0.248 ms 0.190 ms
2 10.117.0.1 (10.117.0.1) 8.593 ms 7.539 ms 7.268 ms
3 100.127.73.40 (100.127.73.40) 8.429 ms 7.939 ms 8.259 ms
4 100.120.100.0 (100.120.100.0) 8.116 ms 8.752 ms 9.041 ms
5 langbprj02-ae1.0.rd.la.cox.net (68.1.1.14) 19.563 ms 21.153 ms 19.961 ms
6 52.95.218.216 (52.95.218.216) 21.581 ms 21.402 ms 21.162 ms
7 54.239.102.102 (54.239.102.102) 35.866 ms 46.345 ms *
8 54.239.102.109 (54.239.102.109) 36.819 ms 20.812 ms 23.031 ms
9 54.239.42.118 (54.239.42.118) 47.760 ms 46.451 ms 46.458 ms
10 * * *
11 52.93.12.114 (52.93.12.114) 75.515 ms 63.136 ms 66.644 ms
12 52.93.12.109 (52.93.12.109) 44.347 ms 52.249 ms 44.491 ms
13 52.93.12.144 (52.93.12.144) 76.781 ms 63.742 ms 101.767 ms
14 52.93.12.167 (52.93.12.167) 45.891 ms 45.936 ms 45.258 ms
15 52.93.240.59 (52.93.240.59) 49.745 ms 51.219 ms 46.678 ms
16 * * *
17 * * *
18 * * *
Here is a traceroute from me, packet loss ranges from minor to unplayable depending on time of day.
Tracing route to ec2-34-199-96-60.compute-1.amazonaws.com [34.199.96.60]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [10.10.21.1]
2 14 ms 76 ms 9 ms 10.82.0.1
3 13 ms 14 ms 11 ms 100.127.76.136
4 15 ms 11 ms 13 ms 100.120.100.30
5 37 ms 37 ms 39 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 37 ms 108 ms 55 ms 72.21.221.204
7 54 ms 47 ms 60 ms 176.32.125.188
8 68 ms 122 ms 80 ms 176.32.125.241
9 * * * Request timed out.
10 87 ms 84 ms 80 ms 54.239.46.2
11 70 ms 76 ms 72 ms 72.21.222.255
12 * * * Request timed out.
13 111 ms 164 ms 87 ms 54.239.108.188
14 * * * Request timed out.
15 89 ms 108 ms 83 ms 52.93.27.43
16 69 ms 75 ms 83 ms 54.239.111.11
17 73 ms 89 ms 86 ms 52.93.24.116
18 72 ms 67 ms 87 ms 205.251.244.59
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
Really appreciate an update on this comment. There is ZERO doubt something has happened to users in my area. It's starting to creep its way out to everyone.
