Forum Discussion

pd91's avatar
pd91
New Contributor III
7 years ago

Severe packet loss (Upload) to amazon web services (Fortnite) - UPDATE 1/9

UPDATE - I suspect this packet loss issue may be fixed very soon. Maybe within the next week. That's all I'll say for now - I'll update again soon

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

    • Morgan1982's avatar
      Morgan1982
      Contributor II

      Hey Janet you seem tech savy. Do you play on pc? If so my friend has a theory about it being an mtu size issue causing fragmentation then discard. Is there a way you can test using different mtu size settings. If so let us know how in game stats look. My pc is down so i cant test it, also my cox rented equipment doesnt even allow me to change it 😞 here is a link he shared with me to try it out

      www.dslreports.com/.../MTU

      • Janet01's avatar
        Janet01
        New Contributor III

        I tried changing the MTU size earlier on when I saw something about PS4 and their MTU size having issues from a post like 2 years ago. I gave it a shot, but it did not resolve the packet loss. I will say as of right now I was running more traceroutes and the the time outs that normally would occur at specific spots once inside the Amazon network are not showing anymore. For example.

        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 4 ms 3 ms 3 ms 192.168.0.1
        2 11 ms 11 ms 10 ms 10.3.64.1
        3 13 ms 11 ms 10 ms 100.126.4.106
        4 19 ms 12 ms 10 ms 100.126.4.100
        5 48 ms 49 ms 48 ms 68.1.1.167
        6 52 ms 50 ms 48 ms 52.95.218.216
        7 62 ms 70 ms 65 ms 54.239.102.42
        8 51 ms 51 ms 47 ms 54.239.102.47
        9 79 ms 78 ms 77 ms 54.239.42.116

        Usually you would see time outs around 6 and like 8 like in the earlier posts, but as of right now that is not happening.

        At the same time though I still get a 1% packet loss in upload on Fortnite, but I have not had any blank shots yet that I have noticed in game. So I think it is starting to be fixed.

    • Morgan1982's avatar
      Morgan1982
      Contributor II

      I was going to switch to centurylink but they never showed for the appointment, so here i am praying cox or epic finds a solution!!

  • So I had CenturyLink come out and install their internet at my place. It's DSL but I'm getting 100 download and 20 upload, so the speeds are good enough. And the best thing of all, no packet loss! I'd honestly just stick with CenturyLink at this point if their speeds were a little better in my area and they offered an unlimited plan like Cox does. Gonna keep up with this forum though, hopefully Cox figures out whats wrong and actually takes the time to fix it. 

  • slimfetz's avatar
    slimfetz
    New Contributor

    Here is another tracert as I am also a victim of the packet loss on AWS servers.  Ever since day 1 I have had this issue.  Yes I've had techs out and the whole 9 yards.  I really can't stand not being able to play the way I want to

    Tracing route to ec2-54-165-218-226.compute-1.amazonaws.com [54.165.218.226]
    over a maximum of 30 hops:

    1 <1 ms 1 ms <1 ms 192.168.0.1
    2 9 ms 11 ms 8 ms 10.75.0.1
    3 9 ms 8 ms 10 ms 100.127.5.32
    4 10 ms 9 ms 11 ms 100.120.102.30
    5 42 ms 46 ms 44 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
    6 44 ms 49 ms 43 ms 52.46.167.212
    7 75 ms 77 ms 80 ms 54.239.105.127
    8 76 ms 76 ms 76 ms 176.32.125.227
    9 * * * Request timed out.
    10 106 ms 79 ms 75 ms 52.93.129.243
    11 75 ms 73 ms 73 ms 72.21.222.249
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 71 ms 73 ms 71 ms 52.93.28.240
    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.

  • Battlefieldpack's avatar
    Battlefieldpack
    New Contributor II

    1 am, not even peak hours and I still have 27% packet loss average in game.  Seriously about to drop Cox over this.

    • LisaH's avatar
      LisaH
      Moderator
      Hi Battlefieldpacketloss. Are you only experiencing an issue with your internet when playing games that go through Amazon servers? If you would to get assistance with your issue, please send this information along with your complete address and name on the account to cox.help@cox.com. This will allow us to assist you in real time. Thanks, Lisa - Cox Support Forums Moderator
      • Battlefieldpack's avatar
        Battlefieldpack
        New Contributor II

        Yes, to Amazon.  I tether my 4G phone and play on wi-fi when I want to play Battlefield V.

  • slimfetz's avatar
    slimfetz
    New Contributor

    New modem.  New trace

    Tracing route to ec2-54-165-218-226.compute-1.amazonaws.com [54.165.218.226]
    over a maximum of 30 hops:

    1 <1 ms 2 ms <1 ms 192.168.0.1
    2 6 ms 7 ms 8 ms 10.75.0.1
    3 8 ms 7 ms 9 ms 100.127.5.32
    4 13 ms 14 ms 11 ms 100.120.102.30
    5 41 ms 41 ms 40 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134]
    6 40 ms 41 ms 42 ms 99.82.176.104
    7 77 ms 75 ms 75 ms 176.32.125.174
    8 72 ms 74 ms 74 ms 176.32.125.181
    9 * * * Request timed out.
    10 95 ms 84 ms 85 ms 52.93.129.241
    11 78 ms 78 ms 72 ms 54.240.229.217
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 77 ms 72 ms 74 ms 52.93.28.218
    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.

  • kgsikora1's avatar
    kgsikora1
    New Contributor

    I'm having the exact same issue. How can I test for my packet loss? I know how to test using cmd for windows to websites but I have no idea how to test for servers

  • Sauromayne's avatar
    Sauromayne
    New Contributor

    Throwing myself in the mix of this nonsense. Here is my Trace route, not that it does any good:

    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     8 ms     8 ms     8 ms  10.128.0.1
      3     8 ms     8 ms     9 ms  100.127.76.8
      4    12 ms    11 ms    12 ms  68.1.0.187
      5     9 ms    20 ms    11 ms  52.95.219.142
      6    13 ms    20 ms    11 ms  52.93.94.116
      7    11 ms     8 ms     7 ms  52.93.94.125
      8    48 ms    47 ms    48 ms  54.240.229.221
      9    47 ms    46 ms    47 ms  54.239.42.122
     10     *        *        *     Request timed out.
     11    75 ms    93 ms    95 ms  52.93.12.120
     12    46 ms    47 ms    47 ms  52.93.12.107
     13    60 ms    79 ms    71 ms  52.93.12.178
     14    48 ms    47 ms    47 ms  52.93.12.203
     15    64 ms    48 ms    73 ms  52.93.13.73
     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.

    DSLReports speedtest1: http://www.dslreports.com/speedtest/46073516

    DSLReports speedtest2: http://www.dslreports.com/speedtest/46073556

    Modem = Netgear CM600

    Router = Ubiquiti EdgeRouter X

    My PC is connected to the router via a Cat6 ethernet cable.

  • Michael_Evancoe's avatar
    Michael_Evancoe
    New Contributor III

    Just a a COX tech out to my house who rewired the coaxial cable, however the problem persists. 

    He was with me in my office watching the packet loss % stat on Fortnite, consistent 1-5% packet loss. 

    He told me he would talk to his superiors once he's back to the office.  He also said he has personally not seen this issue yet, however I suspect this is due to not many gamers being the one in charge of their COX account, parents of kids in most cases.


    Will continue to update

    • Morgan1982's avatar
      Morgan1982
      Contributor II

      Trust me it will go nowhere, my tech said the exact same thing and had a "field ops" come take a look and here we are months and months later plagued by this issue. Im so freaking sick of coming back here to see if they have found a fix. 

      • lawrenceb07's avatar
        lawrenceb07
        New Contributor II

        Same honesty this is horrible.  For me it works fine on the morning and the packet loss starts every day at 5 pm.  I’ve switched modems, drivers, had cox replace all the wires ect even the one running to the street ect....i think i need to find a new provider.  Any recommendations? 

    • lawrenceb07's avatar
      lawrenceb07
      New Contributor II

      I have the same issue let me know if i can support the cause in anyways because we NEED to get this fixed 😞

      • lawrenceb07's avatar
        lawrenceb07
        New Contributor II

        Update I installed a program called haste from haste.net they give me a two week free trial and I did not have to put any credit card information in and it has fixed my leg problem for the time being it’s not 100% perfect but there’s been a dramatic increase in performance I highly recommend it to anybody having this issue with the AWS servers