Severe packet loss (Upload) to amazon web services (Fortnite)

Yep, another AWS packet loss post. Have none of the past customers with this issue had their problems actually resolved?

I'm consistently getting 0-10% packet loss to Amazon web services (both west and east servers) making fortnite unplayable. No, I do not have this problem with other games I play as they do not use Amazon web services to host their servers. This seems to be an issue with the path cox routing takes to AWS servers.

my cox tracert to AWS west (oregon): https://textuploader.com/dzw7o

my cox tracert to AWS west (52.42.109.244) :https://textuploader.com/dzw7g

my cox tracert to AWS east: https://textuploader.com/dzw70

my tethered AT&T iphone to AWS west: https://textuploader.com/dzw76     - interesting how AT&T LTE is a legitimately better connection to AWS than vegas's "best" ISP

No I'm not using a puma 6 modem. I have the cisco DPQ3212.

puma 6 test anyway: https://imgur.com/a/iKR9PYY

I've already troubleshot by hardwiring to modem directly with the same results. I've unplugged the power on router and modem (although it stays on) numerous times, as well as coax.

Here's a tracert of another cox customer with the same exact problems: https://pastebin.com/index/ehaQBYEd

and another: https://pastebin.com/Qqfxa5UN      (there are many more tracerts exactly like these; it also seems like we're all dropping packets at the exact same servers)

now here's a tracert of a cox customer in phoenix (to AWS west) who has 0% packet loss: https://pastebin.com/MX1GfGPC

A reddit thread furthering the evidence that this is explicitly a cox issue and not a personal one: www.reddit.com/.../

I would appreciate real effort in getting this resolved - I know I'm going to be told this is a personal issue when it obviously simply is not. Thanks in advance

Parents
  • 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.

Reply Children