Packet Loss Southern California (Fortnite)
I've had a technician come in he did nothing, then he said he'd send out a field expert. Of course this did nothing as well. I have been wrestling with this issue for almost 3 months now please help!...
Forum Discussion
Hi Cox User Who Needs Help. Do you only have this issue with Fortnite? - Lisa - Cox Support Forums Moderator
I only see it visibly with Fortnite, but I believe it is associated with a bundle of websites.
I believe it is connected with AWS, here is a tracert to AWS west (52.42.109.244)
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 9 ms 10 ms 10.71.32.1
3 18 ms 9 ms 9 ms 100.120.104.132
4 11 ms 12 ms 25 ms 100.120.104.12
5 36 ms 12 ms 19 ms 68.1.1.167
6 10 ms 11 ms 14 ms 52.95.218.216
7 36 ms 20 ms 25 ms 54.239.102.66
8 10 ms 19 ms 13 ms 54.239.102.73
9 36 ms 35 ms 39 ms 54.239.42.118
10 * * * Request timed out.
11 48 ms 53 ms 38 ms 52.93.13.6
12 35 ms 44 ms 49 ms 52.93.12.249
13 58 ms 60 ms 75 ms 52.93.12.248
14 38 ms 36 ms 37 ms 52.93.13.25
15 37 ms 54 ms 36 ms 52.93.240.77
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.- I duplicated this trace, and I also see a slight increase in latency at 68.1.1.167 (your hop 5). This is due to normal ICMP deprioritization. Your traceroute hits the Amazon Web Services (AWS) servers at hop 6. The timeouts once the traceroute reaches the AWS server are expected. Not all AWS servers return ping requests; they block ICMP packets for network security reasons. -Becky, Cox Support Forums Moderator
So you can't fix this problem cox?
