Extreme Packet Loss Recently

Me, and many others have been receiving excessive packet loss in Fortnite servers located in US-West which I believe is hosted on Amazon EC2.

I've contacted Gigablast multiple times and they are of no help. I've tried two different modems and two different computers and problem exists. There are tones of other people experiencing this same issue. There are also issues people are having regarding packet loss on Netflix services (which are also hosted on Amazon?) . So I'm not sure if something routing related has happened with Cox & Amazon EC2 West

Here's a forum post with many people in my location with this issue (https://www.epicgames.com/fortnite/forums/bug-reports/battle-royale-aa/681327-fortnite-packet-loss-and-ping-lag-spikes-as-of-recently-9-04-2018)

A recap of it all is:

- This is a recent issue in NA-West on Cox Communications (mostly Southern CA / San Diego)
- If we switch to NA-East, packet loss goes away (but high pings)
- It's intermittent, meaning, most games have excessive packet loss, but sometimes some servers give 0.
- It's not hardware related. I tested two computers, two modems (directly connected) and the problem still exists.
- Last night around 11 PM PST, I was consistently getting lower to no packet loss, so the issue seems to be 5pm-10/11pm PST.
- Internet speed tests show 1gbps down / 30mbps up, low Fortnite ping, but 30-50% packet loss constantly.

I ran packet tests for 20 minutes while I was experiencing this issue on ~20 other IP/Websites and received no packet loss on any of them (besides google.com).

Please look into this and help the community! Thanks

Gigablast

internet

BrianM
Moderator
7 years ago
Hi Jrdn, we are looking into this. Please provide a trace route to the Fornite/AWS server and post it here so that we can relay it to our network operations team. Thanks!

Brian
Cox Support Forum Moderator
- jrdn
  New Contributor II
  7 years ago
  brianm 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.
  - Becky
    Moderator
    7 years ago
    Hi Jrdn, thanks for posting these. Your results seem to follow normal ICMP prioritization protocols. The timeouts once the traceroute reaches the AWS server are expected. Amazon Web Services servers don't return ping requests; they block ICMP packets for network security reasons. We request trace routes because we're looking for issues along the path to the AWS server that may indicate an issue on the Cox network. Our investigation is ongoing. -Becky, Cox Support Forums Moderator
Tikerz
New Contributor II
7 years ago
same issue. Severe packet loss to ae-1-51.ear1.LosAngeles6.Level3.net and lag-103.bear2.Phoenix1.Level3.net
JoshieA
New Contributor II
7 years ago
Im having the exact same issues......

defeats the purpose of buying the "Ultimate Internet Service"...... LOL
- JoshieA
  New Contributor II
  7 years ago
  C:\Users\Joshie>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 28 ms 1 ms 3 ms 192.168.0.1
  2 25 ms 18 ms 20 ms 10.151.0.1
  3 14 ms 19 ms 20 ms 68.6.14.100
  4 25 ms 28 ms 28 ms 100.120.108.12
  5 23 ms 25 ms 31 ms 68.1.1.167
  6 * * 46 ms 52.95.218.216
  7 48 ms 53 ms 58 ms 54.239.102.54
  8 55 ms 59 ms 48 ms 54.239.102.63
  9 73 ms 66 ms 90 ms 54.239.42.122
  10 * * * Request timed out.
  11 63 ms * 65 ms 52.93.12.52
  12 69 ms 78 ms 70 ms 52.93.12.35
  13 108 ms 108 ms 67 ms 52.93.12.106
  14 66 ms 68 ms 68 ms 52.93.12.137
  15 66 ms 68 ms * 52.93.15.223
  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.
  - 402PrimeTime
    New Contributor III
    7 years ago
    Same issue. COX Ultimate Customer in Gilbert, AZ. Been happening for a couple of months. See video.
    
    www.youtube.com/watch