Forum Discussion

JamesM_'s avatar
JamesM_
New Contributor II
7 years ago

Fortnite Packet Loss

It started happening a week ago, before that it was totally fine but playing Fortnite gives me a ping of 15-35 ms but ping spikes to 60 with packet loss of 20-60% per instance which happens multiple ...
  • JamesM_'s avatar
    JamesM_
    7 years ago

    Tracing route to ec2-52-42-109-244.us-west-2.compute.amazonaws.com [52.42.109.24
    4]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 
    2 8 ms 7 ms 7 ms 10.64.96.1
    3 8 ms 7 ms 7 ms 100.127.3.130
    4 8 ms 18 ms 8 ms 100.120.102.10
    5 13 ms 14 ms 14 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
    6 15 ms 14 ms 14 ms 52.95.218.214
    7 28 ms 31 ms 30 ms 54.239.102.76
    8 * 14 ms 13 ms 54.239.102.83
    9 38 ms 37 ms 38 ms 54.239.42.116
    10 * * * Request timed out.
    11 40 ms 40 ms 39 ms 52.93.13.46
    12 36 ms 37 ms 38 ms 52.93.13.35
    13 54 ms 39 ms 41 ms 52.93.12.182
    14 38 ms 38 ms 40 ms 52.93.12.203
    15 39 ms 39 ms 43 ms 52.93.240.75
    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.

  • JamesM_'s avatar
    JamesM_
    7 years ago

    I am noticing that before 12:00 pm I would have less packet loss and sometimes none for 10+ minutes at a time. Then suddenly 12:00 pm hits and I start to get 15-25% packet losses and it just goes downhill from there. Any explanations? I have tried plugging my PC straight to the modem, I have tried running fortnite on my laptop through wifi and the problem still persists. 

    Note that I played Fortnite for a solid 2 months with no issues, 0 packet loss and suddenly this.

    My tracert to Cox:

    1 <1 ms <1 ms <1 ms [192.168.1.1]
    2 7 ms 6 ms 8 ms 10.64.96.1
    3 8 ms 8 ms 8 ms 100.127.3.128
    4 * 8 ms 8 ms 100.120.102.6
    5 8 ms 7 ms 7 ms ae54.bar2.LasVegas1.Level3.net [205.129.18.109]

    6 * * * Request timed out.
    7 * 22 ms 22 ms 4.7.26.34
    8 37 ms 30 ms * 45.60.45.167
    9 25 ms 21 ms 20 ms 45.60.45.167

    To Google.com

    1 <1 ms <1 ms <1 ms [192.168.1.1]
    2 7 ms 6 ms 8 ms 10.64.96.1
    3 8 ms 8 ms 8 ms 100.127.3.128
    4 * 8 ms 8 ms 100.120.102.6
    5 8 ms 7 ms 7 ms ae54.bar2.LasVegas1.Level3.net [205.129.18.109]

    6 * * * Request timed out.
    7 * 22 ms 22 ms 4.7.26.34
    8 37 ms 30 ms * 45.60.45.167
    9 25 ms 21 ms 20 ms 45.60.45.167

     

JamesM_'s avatar
JamesM_
New Contributor II
7 years ago

Tracing route to ec2-52-42-109-244.us-west-2.compute.amazonaws.com [52.42.109.24
4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 
2 8 ms 7 ms 7 ms 10.64.96.1
3 8 ms 7 ms 7 ms 100.127.3.130
4 8 ms 18 ms 8 ms 100.120.102.10
5 13 ms 14 ms 14 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 15 ms 14 ms 14 ms 52.95.218.214
7 28 ms 31 ms 30 ms 54.239.102.76
8 * 14 ms 13 ms 54.239.102.83
9 38 ms 37 ms 38 ms 54.239.42.116
10 * * * Request timed out.
11 40 ms 40 ms 39 ms 52.93.13.46
12 36 ms 37 ms 38 ms 52.93.13.35
13 54 ms 39 ms 41 ms 52.93.12.182
14 38 ms 38 ms 40 ms 52.93.12.203
15 39 ms 39 ms 43 ms 52.93.240.75
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.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    7 years ago
    @JamesM

    Looking at your results it appears you're getting a good connection to AWS. I'm not sure why you're seeing so many AWS hosts in that trace however. I'd suggest reaching out to them with this data and see if they have any additional feedback.

    -Chris