Forum Discussion
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
As of 10:45 pm PST 9/04/2018
- MarkM17 years agoFormer ModeratorHi Juices,
The link you provide is not opening for us. Would you paste a screen shot in your post so we can send that to our network team?
Mark M.
Cox Support Forums Moderator- dylan123noe7 years agoNew Contributor III
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.
- GregP17 years agoModeratorHi Dnoe,
Thanks for providing the trace route.
Greg
Cox Support Forums Moderator
- OCWinks7 years agoNew Contributor II
Mark, here's one of ours
over a maximum of 30 hops:2 13 ms 10 ms 7 ms 10.75.0.13 17 ms 7 ms 8 ms 100.120.104.924 6 ms 7 ms 7 ms 100.120.104.245 10 ms 10 ms 10 ms 68.1.1.16713 147 ms 154 ms 152 ms 82.112.115.16214 170 ms 156 ms 163 ms 54.239.100.815 158 ms 154 ms 165 ms 54.239.100.2516 173 ms 169 ms 160 ms 54.239.42.10917 164 ms 174 ms 164 ms 54.239.42.17718 * * * Request timed out.19 195 ms 174 ms 209 ms 52.93.6.13620 167 ms 165 ms 168 ms 52.93.101.3521 165 ms 164 ms 166 ms 52.93.101.1022 165 ms 165 ms 164 ms 52.93.7.13123 169 ms 164 ms 164 ms 178.236.0.8924 * * * 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. - OCWinks7 years agoNew Contributor II
Would more tracing routes be helpful? If so, we have others. Thanks so much!
- BrianM7 years agoModerator
Looking more closely at your specific issue, I see that a field escalation was put in and a node split is needed as your node has high utilization at peak hours.
Brian
Cox Support Forum Moderator
Related Content
- 7 years ago
- 12 years ago
- 11 months ago