pd91's profile

New Contributor III

 • 

17 Messages

Closed

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

New Contributor II

 • 

3 Messages

The only two games I play online, Fortnite and Player Unknown's Battlegrounds have constant packet loss. They both use AWS as far as I know. Not sure who is at fault but you guys should work with AWS, Epic Games (Fortnite) and Player Unknown's Battlegrounds to resolve this mess.

I setup an AWS EC2 Linux instance just to test UDP with iperf3. Here are the results: 21% packet loss.

-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 68.x.x.x, port 55263
[ 6] local x.x.x.x port 5201 connected to 68.x.x.x port 62720
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 6] 0.00-1.00 sec 88.0 KBytes 721 Kbits/sec 17.420 ms 4/15 (27%)
[ 6] 1.00-2.00 sec 96.0 KBytes 786 Kbits/sec 9.554 ms 4/16 (25%)
[ 6] 2.00-3.00 sec 112 KBytes 917 Kbits/sec 5.416 ms 2/16 (12%)
[ 6] 3.00-4.00 sec 112 KBytes 918 Kbits/sec 3.207 ms 2/16 (12%)
[ 6] 4.00-5.00 sec 96.0 KBytes 786 Kbits/sec 2.406 ms 5/17 (29%)
[ 6] 5.00-6.00 sec 72.0 KBytes 590 Kbits/sec 2.627 ms 6/15 (40%)
[ 6] 6.00-7.00 sec 96.0 KBytes 786 Kbits/sec 2.518 ms 4/16 (25%)
[ 6] 7.00-8.00 sec 104 KBytes 852 Kbits/sec 2.797 ms 3/16 (19%)
[ 6] 8.00-9.00 sec 64.0 KBytes 524 Kbits/sec 3.988 ms 8/16 (50%)
[ 6] 9.00-10.00 sec 48.0 KBytes 393 Kbits/sec 3.271 ms 8/14 (57%)
[ 6] 10.00-11.00 sec 72.0 KBytes 590 Kbits/sec 2.750 ms 9/18 (50%)
[ 6] 11.00-12.00 sec 88.0 KBytes 721 Kbits/sec 2.615 ms 4/15 (27%)
[ 6] 12.00-13.00 sec 72.0 KBytes 590 Kbits/sec 2.800 ms 7/16 (44%)
[ 6] 13.00-14.00 sec 88.0 KBytes 721 Kbits/sec 2.964 ms 6/17 (35%)
[ 6] 14.00-15.00 sec 104 KBytes 852 Kbits/sec 2.846 ms 3/16 (19%)
[ 6] 15.00-16.00 sec 88.0 KBytes 721 Kbits/sec 2.035 ms 5/16 (31%)
[ 6] 16.00-17.00 sec 104 KBytes 852 Kbits/sec 2.137 ms 2/15 (13%)
[ 6] 17.00-18.00 sec 112 KBytes 918 Kbits/sec 2.919 ms 3/17 (18%)
[ 6] 18.00-19.00 sec 120 KBytes 983 Kbits/sec 3.075 ms 1/16 (6.2%)
[ 6] 19.00-20.00 sec 120 KBytes 983 Kbits/sec 3.002 ms 1/16 (6.2%)
[ 6] 20.00-21.00 sec 128 KBytes 1.05 Mbits/sec 3.422 ms 0/16 (0%)
[ 6] 21.00-22.00 sec 120 KBytes 983 Kbits/sec 2.645 ms 1/16 (6.2%)
[ 6] 22.00-23.00 sec 112 KBytes 918 Kbits/sec 3.005 ms 2/16 (12%)
[ 6] 23.00-24.00 sec 128 KBytes 1.05 Mbits/sec 2.907 ms 1/17 (5.9%)
[ 6] 24.00-25.00 sec 112 KBytes 917 Kbits/sec 3.063 ms 1/15 (6.7%)
[ 6] 25.00-26.00 sec 128 KBytes 1.05 Mbits/sec 2.634 ms 0/16 (0%)
[ 6] 26.00-27.00 sec 112 KBytes 917 Kbits/sec 2.444 ms 3/17 (18%)
[ 6] 27.00-28.00 sec 112 KBytes 918 Kbits/sec 3.426 ms 1/15 (6.7%)
[ 6] 28.00-29.00 sec 128 KBytes 1.05 Mbits/sec 3.109 ms 0/16 (0%)
[ 6] 29.00-30.00 sec 120 KBytes 983 Kbits/sec 2.962 ms 1/16 (6.2%)
[ 6] 30.00-31.00 sec 112 KBytes 917 Kbits/sec 3.048 ms 2/16 (12%)
[ 6] 31.00-32.00 sec 128 KBytes 1.05 Mbits/sec 3.492 ms 0/16 (0%)
[ 6] 32.00-33.00 sec 104 KBytes 852 Kbits/sec 3.251 ms 2/15 (13%)
[ 6] 33.00-34.00 sec 104 KBytes 852 Kbits/sec 2.271 ms 4/17 (24%)
[ 6] 34.00-35.00 sec 112 KBytes 917 Kbits/sec 2.034 ms 2/16 (12%)
[ 6] 35.00-36.00 sec 112 KBytes 918 Kbits/sec 2.483 ms 2/16 (12%)
[ 6] 36.00-37.00 sec 112 KBytes 917 Kbits/sec 2.645 ms 2/16 (12%)
[ 6] 37.00-38.00 sec 112 KBytes 917 Kbits/sec 2.536 ms 2/16 (12%)
[ 6] 38.00-39.00 sec 128 KBytes 1.05 Mbits/sec 2.528 ms 0/16 (0%)
[ 6] 39.00-40.00 sec 104 KBytes 852 Kbits/sec 2.638 ms 2/15 (13%)
[ 6] 40.00-41.00 sec 104 KBytes 852 Kbits/sec 2.698 ms 4/17 (24%)
[ 6] 41.00-42.00 sec 104 KBytes 852 Kbits/sec 3.032 ms 3/16 (19%)
[ 6] 42.00-43.00 sec 96.0 KBytes 786 Kbits/sec 2.152 ms 4/16 (25%)
[ 6] 43.00-44.00 sec 120 KBytes 983 Kbits/sec 1.542 ms 1/16 (6.2%)
[ 6] 44.00-45.00 sec 112 KBytes 917 Kbits/sec 2.382 ms 3/17 (18%)
[ 6] 45.00-46.00 sec 72.0 KBytes 590 Kbits/sec 2.276 ms 6/15 (40%)
[ 6] 46.00-47.00 sec 120 KBytes 983 Kbits/sec 2.426 ms 1/16 (6.2%)
[ 6] 47.00-48.00 sec 120 KBytes 983 Kbits/sec 2.867 ms 1/16 (6.2%)
[ 6] 48.00-49.00 sec 96.0 KBytes 786 Kbits/sec 3.072 ms 3/15 (20%)
[ 6] 49.00-50.00 sec 112 KBytes 917 Kbits/sec 2.655 ms 3/17 (18%)
[ 6] 50.00-51.00 sec 96.0 KBytes 787 Kbits/sec 2.251 ms 4/16 (25%)
[ 6] 51.00-52.00 sec 64.0 KBytes 524 Kbits/sec 3.056 ms 8/16 (50%)
[ 6] 52.00-53.00 sec 80.0 KBytes 655 Kbits/sec 2.864 ms 5/15 (33%)
[ 6] 53.00-54.00 sec 112 KBytes 918 Kbits/sec 2.456 ms 4/18 (22%)
[ 6] 54.00-55.00 sec 88.0 KBytes 721 Kbits/sec 2.957 ms 4/15 (27%)
[ 6] 55.00-56.00 sec 72.0 KBytes 590 Kbits/sec 2.581 ms 7/16 (44%)
[ 6] 56.00-57.00 sec 72.0 KBytes 590 Kbits/sec 2.722 ms 8/17 (47%)
[ 6] 57.00-58.00 sec 40.0 KBytes 328 Kbits/sec 2.656 ms 11/16 (69%)
[ 6] 58.00-59.00 sec 72.0 KBytes 590 Kbits/sec 2.980 ms 5/14 (36%)
[ 6] 59.00-60.00 sec 80.0 KBytes 655 Kbits/sec 3.039 ms 7/17 (41%)
[ 6] 60.00-61.00 sec 64.0 KBytes 524 Kbits/sec 2.866 ms 9/17 (53%)
[ 6] 61.00-62.00 sec 40.0 KBytes 328 Kbits/sec 3.395 ms 10/15 (67%)
[ 6] 62.00-63.00 sec 96.0 KBytes 786 Kbits/sec 2.760 ms 4/16 (25%)
[ 6] 63.00-64.00 sec 120 KBytes 983 Kbits/sec 2.528 ms 1/16 (6.2%)
[ 6] 64.00-65.00 sec 120 KBytes 983 Kbits/sec 2.819 ms 1/16 (6.2%)
[ 6] 65.00-66.00 sec 128 KBytes 1.05 Mbits/sec 2.580 ms 0/16 (0%)
[ 6] 66.00-67.00 sec 128 KBytes 1.05 Mbits/sec 2.338 ms 0/16 (0%)
[ 6] 67.00-68.00 sec 128 KBytes 1.05 Mbits/sec 3.216 ms 0/16 (0%)
[ 6] 68.00-69.00 sec 120 KBytes 983 Kbits/sec 3.406 ms 1/16 (6.2%)
[ 6] 69.00-70.00 sec 120 KBytes 983 Kbits/sec 3.222 ms 2/17 (12%)
[ 6] 70.00-71.00 sec 96.0 KBytes 786 Kbits/sec 2.446 ms 3/15 (20%)
[ 6] 71.00-72.00 sec 112 KBytes 918 Kbits/sec 2.335 ms 2/16 (12%)
[ 6] 72.00-73.00 sec 112 KBytes 917 Kbits/sec 2.272 ms 1/15 (6.7%)
[ 6] 73.00-74.00 sec 112 KBytes 918 Kbits/sec 2.429 ms 3/17 (18%)
[ 6] 74.00-75.00 sec 96.0 KBytes 786 Kbits/sec 2.136 ms 4/16 (25%)
[ 6] 75.00-76.00 sec 104 KBytes 852 Kbits/sec 1.990 ms 3/16 (19%)
[ 6] 76.00-77.00 sec 112 KBytes 918 Kbits/sec 2.740 ms 2/16 (12%)
[ 6] 77.00-78.00 sec 112 KBytes 918 Kbits/sec 2.549 ms 2/16 (12%)
[ 6] 78.00-79.00 sec 104 KBytes 852 Kbits/sec 2.237 ms 2/15 (13%)
[ 6] 79.00-80.00 sec 96.0 KBytes 786 Kbits/sec 4.430 ms 4/16 (25%)
[ 6] 80.00-81.00 sec 96.0 KBytes 786 Kbits/sec 3.335 ms 5/17 (29%)
[ 6] 81.00-82.00 sec 104 KBytes 852 Kbits/sec 3.003 ms 2/15 (13%)
[ 6] 82.00-83.00 sec 80.0 KBytes 655 Kbits/sec 4.371 ms 6/16 (38%)
[ 6] 83.00-84.00 sec 96.0 KBytes 786 Kbits/sec 3.812 ms 3/15 (20%)
[ 6] 84.00-85.00 sec 112 KBytes 918 Kbits/sec 2.792 ms 3/17 (18%)
[ 6] 85.00-86.00 sec 112 KBytes 918 Kbits/sec 2.377 ms 3/17 (18%)
[ 6] 86.00-87.00 sec 96.0 KBytes 786 Kbits/sec 2.668 ms 4/16 (25%)
[ 6] 87.00-88.00 sec 112 KBytes 918 Kbits/sec 2.592 ms 2/16 (12%)
[ 6] 88.00-89.00 sec 104 KBytes 852 Kbits/sec 2.643 ms 3/16 (19%)
[ 6] 89.00-90.00 sec 96.0 KBytes 786 Kbits/sec 2.411 ms 4/16 (25%)
[ 6] 90.00-91.00 sec 112 KBytes 918 Kbits/sec 2.253 ms 3/17 (18%)
[ 6] 91.00-92.00 sec 112 KBytes 917 Kbits/sec 3.056 ms 1/15 (6.7%)
[ 6] 92.00-93.00 sec 104 KBytes 852 Kbits/sec 5.049 ms 3/16 (19%)
[ 6] 93.00-94.00 sec 112 KBytes 918 Kbits/sec 2.995 ms 3/17 (18%)
[ 6] 94.00-95.00 sec 96.0 KBytes 786 Kbits/sec 2.978 ms 3/15 (20%)
[ 6] 95.00-96.00 sec 96.0 KBytes 786 Kbits/sec 3.705 ms 3/15 (20%)
[ 6] 96.00-97.00 sec 112 KBytes 918 Kbits/sec 3.610 ms 4/18 (22%)
[ 6] 97.00-98.00 sec 96.0 KBytes 786 Kbits/sec 3.086 ms 4/16 (25%)
[ 6] 98.00-99.00 sec 80.0 KBytes 655 Kbits/sec 3.046 ms 4/14 (29%)
[ 6] 99.00-100.00 sec 104 KBytes 852 Kbits/sec 2.643 ms 5/18 (28%)
[ 6] 100.00-100.08 sec 0.00 Bytes 0.00 bits/sec 2.643 ms 0/0 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 6] 0.00-100.08 sec 0.00 Bytes 0.00 bits/sec 2.643 ms 329/1600 (21%)
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------

Former Moderator

 • 

267 Messages

Hi there, we'll gladly take a look at your modem regarding your packet loss if you'll send us either a Facebook private message, Twitter direct message, or email to cox.help@cox.com and attach this link. We'll need your complete address and account name. -Thanks, Carol

Contributor

 • 

50 Messages

Stop Replying with this and fix the issue Carol.

New Contributor

 • 

1 Message

I am having the same issues, running tracert to AWS continues to show packet loss. I just to 2% every few seconds, and sometimes as high as 6. Fortnite and PUBG performing exactly the same (poorly) due to packet loss. I've had a tech and his boss both out to help on the same day. Everything looked good for them, but these issues with AWS continue to plague me.

Moderator

 • 

4.3K Messages

Hi Toomuchbob, please post your traceroutes to the AWS server(s) that show packet loss. -Becky, Cox Support Forums Moderator

New Contributor

 • 

2 Messages

Becky,

it is pretty clear at this point this a systematic issue with Cox.  This clearly isn't an isolated issue by customer.  This has been ongoing for months and we have yet to see any resolution.  I have had packet loss frequently playing the same games as many of your other customers have.  This was occurring not only at my current residence but the one prior to this.  Many of us have had techs out etc.  While I understand that you have a chain of command to follow, its unbelievable Cox hasn't resolved this or at least made a statement that they are aware of the issue.

New Contributor III

 • 

34 Messages

Amen. 

Contributor

 • 

50 Messages

Fix this, you guys are literally doing nothing

New Contributor II

 • 

4 Messages

I have Cox and ATT at my home now. I've had both for just over a month. I routinely switch back and forth to check to see if there is packet loss on my Cox internet to amazon and Fortnite servers.. There still is packet loss that kills the gameplay.. This is just Cox not doing there job and fixing issues that are affecting their customers. Amazon wont be forced to pay "handling fee's" to Cox so this problem will always exist. Just switch to ATT like I did. Cox is not worth it.

New Contributor III

 • 

11 Messages

It has been months that this thread has been open. This is the only real solution that I can offer anyone. Cox will not even acknowledge this problem, yet this post has 5500 views....

Contributor

 • 

72 Messages

Replying with another thread I just created - same issues of packet loss in Phoenix/Arizona. 


forums.cox.com/.../internet-issues---consistent-lost-packets-north-phoenix-arizona

Contributor

 • 

72 Messages

In addition, anyone with data to support their claims of packet loss and inactivity by Cox should consider filing an informal complaint with the FCC:  https://consumercomplaints.fcc.gov/hc/en-us

New Contributor

 • 

8 Messages

I used to have the consistent packet loss issues on Fortnite and I just changed all the coax splitters and I have 0% packet loss both up and down. The only thing is that I sometimes will get ping spikes that last like 30 seconds and it reaches 1,100 ping

Contributor

 • 

72 Messages

My entire run to the closest node has been entirely replaced by Cox.  It's definitely not old/shoddy wiring or connectors. 

Contributor

 • 

50 Messages

"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"

Becky said this it means nothing to me please fix my issue or tell me what to do because you guys have been avoiding this issue for months and I'm down with this trash.

Contributor

 • 

72 Messages

This is the same run around I've gotten on my thread.  Not sure if this has been attempted, but Cox tech support loves to use the "ICMP deprioritization" excuse.  Here's a way around that:

Download Ping Plotter - https://www.pingplotter.com/download - and change the packet type to either UDP or TCP.  Servers will not deprioritize those packets.  

Do set to UDP, in Ping Plotter go to "Edit" --> "Options" --> "Packet" - change the "Packet Type" option to "UDP Packets".  

For TCP, you need an extra piece of free software that can be found here:  https://nmap.org/npcap/dist/npcap-0.99-r7.exe

Server will not deprioritize UDP or TCP packets as they are used in normal internet communication as opposed to ping (ICMP) which is used primarily for diagnostics and can be dropped as low priority.  

I'd use UDP as I've seen the exact same behavior with UDP or TCP packets in Ping Plotter.  Funny enough, a normal trace route using ping produces the same exact levels of packet loss and latency, but because ping can be considered "low priority" by hops, it can be easily waved off as expected behavior.  

New Contributor II

 • 

4 Messages

same problem, PLEASE FIX THIS !!!

Moderator

 • 

4.3K Messages

Hi Teddy, your modem metrics are outside of our preferred specifications, and your modem log shows multiple timeouts. These are often caused by faulty connectors or intermittent noise (ingress) affecting your connection. Are there any splitters on the coax connection to the modem? You might try replacing or temporarily bypassing the splitter to see if connectivity improves. If not, I suggest a service call so an on-site technician can resolve this for you. If you'd like my team to schedule your appointment, email your full name, address, and a link to this thread to cox.help@cox.com. -Becky, Cox Support Forums Moderator

New Contributor II

 • 

4 Messages

if you look at my account, ive had technicians come out many times with no fix. and it doesn't happen in everything I play, ONLY fortnite to AWS servers. 

New Contributor II

 • 

4 Messages

I also spent 500$ on top of the line equipment and still same problems :(

Contributor

 • 

42 Messages

Hello Cox,

I'm a fellow gigablast internet subscriber that is having the same exact issues as A LOT OF people in the southern California region. I'm in San Diego and I have amazing download speeds reaching that of 950+ consistently.

Speedtest results: www.speedtest.net/.../7867448045

Networking Equipment:

Tried 2 different Docsis 3.1's and both encountered same issue thus not LAN

Cat 7 cables

Multiple devices tested: Xbox X, 2,000$ PC (Both experience the same packet loss symptoms)

^The only reason I listed the above is to give you a sense that my equipment is top of the line equipment. The data loss isn't coming from the equipment nor the LAN

Now the huge problem which degrades the entire service is this constant packet loss while using upstream towards AWS servers. I have diagnosed this through using ping plotter and viewing packet loss in between hubs passing data. The intensive upstream applications that I have experienced packet loss with are twitch (while streaming) and Fortnite. The Fortnite lag is so unbearable. All throughout the day 24/7 there is a constant nonstop packet loss ranging from 1%-6% then sporadic jumps up to 32% or so. It literally makes the game impossible to play as gunfights within the game are losing frames and data causing me to be essentially at a disadvantage 24/7.

I understand sending out Techs is the first option and step to resolving this, however, by the looks of this issue it seems systematic. We as customers pay for our service to dependable and up to date as this is 2018. We want to play this game while it's popular and not 4 months from now when you deserve to believe this is a huge problem.There is in reality data loss on the upstream end of things causing Fortnite to be unplayable. The only game I play right now is Fortnite thus me having to be subjected and forced into packet loss by an incompetent ISP who either is over utilizing nodes or using incompetent hubs that incur data loss is petty in 2018.

I have had 3 techs and the most recent one(DEC7) said there was data loss and they would have maintenance crews out there and if by Sunday the packet loss is till there notify someone.

One condensed sentence that sums up the entire problem: When cox users go to utilize there upstream while connecting to services on AWS such as playing FORTNITE or streaming to TWITCH their incurring packet loss causing online gaming to be impossible or degraded services. 

I need this fixed please! I want to play fornite and knowing that every single gunfight is utterly affected by ISP issues makes it useless and a waste to play.

New Contributor III

 • 

34 Messages

We've all been through that song and dance before, brother. I'm coming back to this thread after 4 months and my problems were never fixed, best of luck!

Contributor

 • 

42 Messages

DEC 12/10/18 UPDATE: Called in for a follow-up in which I was notified that the maintenance crews were in the area running diagnostic tests.

New Contributor III

 • 

16 Messages

unfortunately you won't get any positive results from cox. I've dealt with packet loss from aws since around may- june i believe? I've used VPN's, tethered phone AT&T, Tethered Verizon phone, and neighbor next door has AT&T internet and has no issues. Soon as i get back on the cox network i get packet loss. The problem is no one wants to contact anyone to resolve the issue, but just say "they see inconsistencies with your modem" when they can't just admit they're at fault. What's pathetic is that for well over 6 months this has been an issue proven in probably 50+ posts to be on cox's end, but they will not budge and get into contact with AWS and expect their paying customers to do it for them. If AT&T wasn't my only option i would leave cox because it's just depressing how long this issue has been around with no resolve. I'm in Oklahoma by the way not even in San Francisco or phoenix where is see a large number of posts and I still get continuous packet loss.

New Contributor II

 • 

4 Messages

OK, so I may have a solution! Just to let everyone who reads this post know I am in no part or affiliated with the program that I am going to recommend so don't take this the wrong way. I've been dealing with constant packet loss for months now and almost gave up on solutions after upgrading to cox gigablast internet and spending a fortune on my modem/router combination (with no fix).

Tonight I decided to test out a program called Speedify. It has a free trial so I figured what the hey. Played two games and had ZERO PACKET LOSS! I almost thought it was to good to be true, so I closed out the program and tried again, no packet loss at first but after about 3 minutes it started and got up to its normal 5-10% consistent. I played the game through and it never went away (I was thinking todays patch may have been the fix). Opened the program up and ZERO PACKET LOSS AGAIN!!!!

The only reason Im posting this is because I, like many of you have been dealing with this and let me tell you its worth a try, FREE TRIAL. 

I would like someone to do a test of this or maybe a few people and post how it works for them (I will be checking the forum daily as I have been). Please test the packet loss in fortnite BEFORE you download Speedify, confirm that you are getting upload packet loss like normal. Then after you have seen packet loss download it and run the trial and see what happens. Post your results! 

Hope this can help some of you... This is my first night with it so hope it sticks

Good night!

P.S. Also if anyone can figure out what this program actually does that would be awesome for an explanation as to why it fixes it, maybe theres a free solution. I know some of you are pretty smart with this kind of stuff :)

New Contributor III

 • 

16 Messages

speedify is a VPN service it gives you a different IP address which I'm assuming does something with how the internet communicates with AWS servers (not a huge internet guru so may be wrong as to why it makes it work). Most use it for illegal pirating of movies and what have you, but when used for fortnite it takes away the packet loss but comes at the cost of a sometimes higher ping. It's been noted multiple times that a VPN fixes the issue, the problem is we shouldn't have to use alternative methods to make our internet work as it should, considering this issue has been going on close to 6 months +. I used hotspot shield, but then came to the realization that it's crazy i'm spending money to play a game that's free while paying $100 a month for gigablast. So i quit fortnite and played other games.

New Contributor

 • 

2 Messages

Put me on the list of people who are experiencing packet loss. 3-5% stable in game jumping to up to 30% while fighting. Ive changed all connections, NICs, and modem/router. Ive reset, reset, and reset. I call Cox and they tell me everything is fine. Using ping plotter im able to see on my 3rd hop is when packet loss sets in. Ive also had this issue at my mothers house before moving out. Im in west phoenix where this is clearly an ongoing issue. 

New Contributor

 • 

2 Messages

Being as cox is the only provider i can use in my apt complex, my only solution is to go with a cheaper plan until this is fixed. I recommend everyone do this, maybe then will cox budge.

Former Moderator

 • 

1.5K Messages

Hi Sm31ly and Dnoe, I am unable to detect any signals issues on your modem at this time, and after pinging your modem, have found 0% packet loss. Can you please send us an email at cox.help@cox.com with a screenshot of your traceroutes? If possible, please run the traceroute while hard-wired to the modem, so we may see if any issues are detected on our end. Any assistance you can provide would be greatly appreciated. -Kevin M. Cox Forums Support Moderator


New Contributor III

 • 

16 Messages

I’ve already posted trace routes months ago, and you’ll just say “it’s out of our network” which leads me back to what I was talking about earlier of cox won’t work with aws to resolve the issue that only they have and no other internet provider does, but leaves the burden to it’s customers. Ive had multiple techs out lines re-ran,multiple tests, & trace routes. Still cox doesn’t budge. The easiest most simplest test was me using my phone internet AT&T and work phone internet Verizon and getting no packet loss or while on VPN I get no packet loss but soon as I’m back on cox network, there’s packet loss. Don’t have to be a internet wizard to know that it’s on cox’s End. Not trying to be rude just fed up with the run around for 6 months. 

New Contributor

 • 

5 Messages

im having and have been having the same *** issues in WOW and even just general video streaming

its even more frustrating now that i know this has been going on for months with no fix

Contributor

 • 

42 Messages

I HAVE COME TO THE END OF ROADS WITH COX AND THEIR SUPPORT...

It is a verifiable problem that many cox users experience data loss at 1% or more on their favorite and most popular game FORTNITE!

After speaking to the highest corporate level of escalation as in nothing can GO further than that....

THEY SAID THIS AND I ASKED IF I COULD QUOTE:

"WE DONT COVER ONLINE GAMES TO CLOUD BASED SERVICES"

UMM EXCUSE ME ONE OF THE ONLY REASONS PEOPLE GET INTERNET IS FOR ONLINE GAMING...IS THIS A JOKE?

THEY THEN INSTRUCTED ME TO REACH OUT TO AWS AS THEY AREN'T COGNITIVE ENOUGH TO HAVE THEIR BILLION DOLLAR CONNECTIONS DO IT FOR US!

SHE PRETTY MUCH TOLD ME THERE ISN'T ANYTHING THEY WANT TO DO AND THAT IM OUT TO FEND FOR MYSELF ON THE ISSUE.

This is after thousands of cox customers posts around the internet and many verifiable and documented instances of packet loss using default pathways to AWS applications. 

AN ISSUE THOUSANDS OF COX CUSTOMERS ARE EXPERIENCING ALL AROUND THE NATION ON THE MOST POPULAR GAME IN THE WORLD AT THE MOMENT!

AS OF 12/26/2018 MANY COX CUSTOMERS ARE EXPERIENCING ISSUES WITH AWS PLATFORM SERVICES AND COX ISN'T THE TYPE OF COMPANY TO FIX SOMETHING THEY HAVE A DEGREE APART OF.

ANOTHER TAKE AWAY IS THAT COX AS OF 2018 DOESN'T HAVE A SYSTEM TO TROUBLESHOOT PROBLEMS IN AN ACCORDINGLY FASHION AND DUMP MANY OF THEIR OWN NETWORK ISSUES ON TO CUSTOMERS WHO INDEED DONT HAVE THE RESOURCES TO TRULY GET TO THE BOTTOM OF IT. Its literally a real life scenario of finding a needle in the haystack which in return decreases performance in diagnostic measure and spawns an atmosphere of a company that can't even troubleshoot themselves.

SPEEDIFY AS of 12/26/2018 FIXED MY PACKET LOSS PROVING IN PHYSICAL REALITY THAT THE DEFAULT PATH SERVED TO ME DOES INCUR DATA LOSS.

Executive Summary of entire problem:

-4+ techs to apartment who all said onsite problems were resolved

-BLANKET OF PACKET LOSS @ 1% - 5% ON FORTNITE STILL PREVALENT

-Speedify fixed packet loss and proves default path incurs data loss or there is an apparent problem

-lots of posts around the web that also share the same symptoms on the most popular game at the moment

AS IT SHOULD....WHEN A NEW USER GETS COX THEY SHOULD HAVE NO PACKET LOSS TO ANY SERVICE....right now you're executive escalation team even reassured me that you don't want to give a helping hand and that this issue isn't to a degree related to your service when indeed you do have a play in this problem

The problem is the way you handle power users who are more educated then 90% of your employees. You act in a condescending way that paints a Utopian side for you that in all universes Cox won't be the one to blame when it actually hurts your stance even further. A company that wishes to not acknowledge and leave many customers unanswered is one that needs a different managing team altogether. Maybe your board should be voted upon and have people that do understand the need for online gaming.

A company that fails to acknowledge abnormalities and decides to ignore creates a resenting base of consumers who know they have true issues with the services they're served.

And the sad thing is this is over a free to play video game...they literally will keep you in a nonstop loop of diagnosing when in reality it is out of LAN's

Unfortunately as this issue isn't resolved and all I use my connection for is online gaming specifically using fornite I'm going to have to document all of the findings around the internet and create a video to solidify our stance as consumers being forced into default paths that incur data loss.

At this point I feel as if cox will get this fixed behind the scene and one day ill wake with no packet loss and all of these posts would be considered irrelevant right. Wrong as of 12/26/2018 I have been experiencing packet loss on fortnite for months now !

The fact is is that the cox executive level stated they CANNOT BE COUNTED ON TO PROVIDE A DEPENDABLE CONNECTION FREE OF PACKET LOSS TO FORNite...if you're a fortnite player and you hear this that's more than enough to turn you away! or sure the service will work for many but if your in those select few we could give a hoot about you because are revenues allow us that! If you're one of those few we can't do anything more and you go contact the server platform we serve millions of connections to as we don't want to be bother with this. Your pr is just not cognitive enough to understand this 2018...

Contributor

 • 

42 Messages

as of 12/28/2018 this is still an issue for me...

New Contributor III

 • 

21 Messages

Me as well. This is horrible, horrible service. I get 1-2% 24-7 and at times it goes to 5-10% for hours on end. I've had two techs out and signal strength is perfect.

Contributor

 • 

42 Messages

as of 12/30/2018 this is still a problem

New Contributor III

 • 

20 Messages

This is still an ongoing issue for me and I also live in Oklahoma and playing on the AWS East coast servers and have been experiencing this for about 7 months now. It all started back in the summer of 2018. I have also attempted all the troubleshooting steps in this forum and its unbelievable this issue is still unresolved.

New Contributor III

 • 

16 Messages

You can literally hook up your same equipment to any other form of internet whether it be phone tethering with Verizon, AT&T, or etc or use a vpn and get no issues but as soon as you go back to cox’s Network you have issues, but they are 100% sure it’s not their fault. Give me a break. Just by those troubleshooting steps you can determine that the issue is on cox’s End. Cox treats it’s customers like they’re still morons stuck in the 90’s on Dial up. Problem is people can easily research their issues online and find fixes and others that have similar issues it’s not just word of mouth anymore. This issue will eventually smack them in the face one day. I hope the NPC employees will actually do something about it sometime this year.

New Contributor III

 • 

20 Messages

I literally online chatted with 3 different techs and called last night and explained what was going on and referenced this forum and the last tech I spoke to said they would have someone look into the issue further I have the full transcript of the conversation. I also asked if it was really true they don't support online gaming to cloud based services and was reasured this was indeed not true. If anyone want to call the support line and ask about the issue reference "fortnite AWS server issues". If they can't fix this issue it's a definite good bye to Cox.

New Contributor III

 • 

20 Messages

Also ask for a CAG tech not just a help desk teir 1 agent.

New Contributor III

 • 

20 Messages

They will not take the initiative to fix this problem plain and simple. They will refer you to talk with Fortnite and say they must put in a request for AWS to have the issue resolved. Only problem Fortnite does not have a phone number for support and their support team is really horrid. Next best thing would be to attempt to contact ASW support, but you must have an account to get any support help and that is for your own service not someone else's. It's unbelievable you pay money to your ISP and they can not take the initiative to make sure their service is excellent and have a problem fixed that so many customer's are experiencing. If you plan on gaming any further into the future leave cox now, because their support is just to blame someone else and take your money.

Contributor II

 • 

103 Messages

New Contributor II

 • 

4 Messages

This problem also affects Battlefield 5, who also runs off AWS EC2. 3-5% packet loss ALL DAY, and as bad as 11% reported in game during peak traffic hours in the region.  My tethered 4G LTE phone plays the game better than Cox which is sad but true.

Contributor

 • 

42 Messages

As of 1/14/2019 I cant play a single game without packet loss! I can't even play at all because the stutters in the gunfights put me at a disadvantage by far. 

It's so annoying playing with friends today who have the lowest packages of internet from all of their providers and dont experience anything yet the one whos pays close to 200$ a month for gigablast with great equipment gets nothing but nonstop packet loss!

New Contributor III

 • 

20 Messages

As of 1/15/2019 I have noticed the packet loss for my upload has almost completely dissapeared it will once in awhile show 1%, but for the most part shows 0%. I did create a support ticket with epic games to have the issue looked into and haven't heard anything back, but as the op said about a week ago about something being done (not sure what) I think it's being worked on.

Contributor

 • 

42 Messages

but its that 1%-3% that is not suppose to happen! That 1%-3% messes up gunfights and warps the game due to server upload packet loss. When you watch every huge streamer or video on youtube you see no fluctuation on the packet loss. That 1%-3% happening throughout the game removes competitiveness and keeps players at a disadvantage

New Contributor III

 • 

20 Messages

I agree it shouldn't be there at all because it wasn't before, but it definitely is a little bit more bare able at the moment

New Contributor III

 • 

20 Messages

And it's back to a constant 1-3% loss on upload.

Related Content

  • Closed

    1

    0

  • Closed

    2

    0

  • Closed

    8

  • Accepted Solution

    Closed

    15

    0

  • Closed

    1

    0

Recent Discussions

View More

Loading...