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

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

BooPacketLoss
New Contributor III
7 years ago
Yes, this is real, yes I just contacted Cox about it for the thousandth time. Packet loss to Amazon Web Services servers is just absolutely brutal for me in the Phoenix area. I forwarded your Reddit post to them and sent my own PingPlotter tracert of the packet loss, there had better be some serious steps taken by COX soon.
- GoblinPackets
  New Contributor
  7 years ago
  BooPacketLoss,
  
  I'm in the same boat but with all upload streaming services. A year ago everything was fine, sometime in the past few months I've experienced a baseline 2%-10% or higher packet loss while streaming to twitch, mixer, YouTube. You name it, I drop packets. Tried streaming through Streamlabs OBS, OBS studio, Xsplit. Tried my computer, tried my laptop, tried moving across the country. Replaced my 200 dollar modem and router with new 200 dollar gigabit certified modems and routers. Replaced cabling. Had techs come out. Talked to tech support.
  
  I build networks (RF/data) for my career full time and have gone to great lengths to ensure it wasn't something on my side. All my equipment is very high end and I've conducted so many tests at this point I'm not sure what to do anymore. It's gotten so frustrating that I'd almost switch to another provider who gives a reliable upload and horrible sub 100 download just to get back to business. Let me know if you get any traction because my wheels are still spinning.
  
  💖
pd91
New Contributor III
7 years ago
I've gotten in touch with an employee at Epic Games with access to fortnite servers and he was kind enough to run a traceroute to my IP address.

"This is from a NAW FNBR server that's located in northern California. All the traceroutes I ran stopped at that last gateway and then timed out after that.

Hope this helps - I can say with some certainty that the issue is on Cox's end, not ours." - https://pastebin.com/rM03cvBq (removed my personal IP)

Finally, my reddit thread showing quite a few more people with the exact same issue - www.reddit.com/.../
gjett1
New Contributor III
7 years ago
Same Problem. Cox fix this!

BUMP.
Battlefieldpack
New Contributor II
7 years ago
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.
Janet01
New Contributor III
7 years ago
This is still an ongoing issue just FYI if keeping up with this thread. I have a thought to why this is happening, but I think I am close to finding proof to my idea.

I believe this is solely on C.O.X to fix.

So I have both a Mac and Windows computer I can run some tracert/traceroutes from to the servers and the reason C.O.X will push this issue off as not their problem is because they say once the data leaves their server it is not their problem any more, but the only data you can really provide from Windows is a simply tracert which will use ICMP data. If you run these tracert using ICMP data there is no data loss from you to the servers and this is what C.O.X gets sent by most people experiencing this issue and they will just dismiss it. If you have a Mac or a Linux machine though you can run a traceroute with the specified data type as UDP. If ran in succession with the amount of data being 60 packets per second and with UDP after running the command about 4x you will see in one of those a dropped packet or no response for the latency of how long the data took to send. These drops are happening BEFORE they reach the C.O.X server that is sending the data off to Amazons servers. This is after testing this just a little bit ago and want to run some more tests. If this is the case it will be on C.O.X to fix this issue. A couple of thoughts to why this is happening now and did not happen before June of 2018. Cox is has probably changed the way they treat UDP data possibly, only problem is no other online games ex. COD BOPS4 seem to have this packet loss issue unless they are, but you can not actually tell or you do not get that information from the network information section of COD BOPS4. It could be possible that the game itself is set to only send out so much information going up that the data is under the capped rate C.O.X is setting on their networks to have going out. If you notice when you connect to a VPN service and run the game through this your packets per second going up change to a much lower number and you receive no loss, just higher ping. Also if you notice streamers pushing over 100 packets per second going up to the Fortnite servers have no problem with packet loss, so I do not believe this is an issue on Amazon's servers.

In conclusion, back in June of 2018 C.O.X probably changed something to how UDP data is being handled when going out.

If that is not the case then I believe around that time Fortnite went from 30mhz to 60mhz on their servers and I m not sure if that means at what rate data is being sent out, but I believe it does and that would explain why this is when this all started to happen. I also think around that time is when we received the ability to see the network debugging statistics on Fortnite and it could have been happening before this, but I doubt it since the blank shotgun hits were not always happening.

Anyways that's the ideas I have came up with after looking from all the different forums from C.O.X and Fortnite. I will be running some more tests to see if I can nail it down to only Amazon servers receiving the packet loss on upload or if it is any other online games or sites. If its any site receiving packet loss like this and the results still show the drops happening before C.O.X server it is on them and I will be giving their techs all this information which if they try denying that then it is to the FCC to file claims.

If anyone else has a mac or linux machine they can run some tests with also, and come up with the same findings please call C.O.X tech support and lay into them to have the issue fixed and if they do not file FCC complaints.

It is time this is fixed.
- esv16
  New Contributor
  7 years ago
  I noticed this began around the same time you mentioned. I moved in June and assumed it was my new address. I've moved again since then and its still an issue so i believe you're onto something with that June date. Game is horrible you can't even play. Cox is garbage for allowing this and dodging the problem.
Packet_Loss_Ass
New Contributor
7 years ago
Funny, I'm here for the exact same issue that I've been researching for over a month now and it's odd I stumble across the same reddit post that I commented in.

I had a Cox tech come out last week. He 'reset' everything in my house and when he was done he said he fixed my issue. He handed me a small metal device that he called a packet capture and said it was used to provision data for uplink. I bought it for about a day and a half since it seemed to fix my issue. Before he left I verified my uplink had 4 locked channels instead of 1 and I played a few games of Fortnite throughout the day with almost 0 packet loss. It was glorious! There was 1-2 instances where I saw packet loss go to 2% but only for a second or 2. Next day, internet went out, I cycled the modem and the packet loss was back with a vengeance.

Pretty safe to say the tech gave me some nonsense and went about his day. If there were another ISP alternative in my area I'd have already switched but Cox is just short of a monopoly in my area and apparently that entitles them to sell a 'premium' service built on a sub-par infrastructure.

I'd post my tracert output as well but it's nearly identical to what's already linked above.
- pd91
  New Contributor III
  7 years ago
  hm yeah after barely skimming over what a packet capture device is, it seems the improved connection might have just been coincidental. I'm 99% sure the issue resides within cox's routing to amazon's servers. it seems this issue is getting really bad as of the past couple days though, so I'm sure more will show up. Hopefully we can figure out how to get their attention
megamatt0
New Contributor
7 years ago
Hello, I have been having the same exact issue at my home for the past 2 months as well. Southeast Arizona area. It has been very frustrating and I do not want to switch to CenturyLink as they only offer 40Mbps. I had a tech come out earlier this week and he said my speeds and signal levels are fine. I hope this can get figured out very soon.
BrianM
Moderator
7 years ago
If anyone is still having trouble, please provide a current trace route in this thread and we will forward to our network operations team for further review. Thanks!

Brian
Cox Support Forum Moderator
- Cox_User_Who_Ne
  Contributor
  7 years ago
  C:\Users\mbubl>tracert google.com
  
  Tracing route to google.com [216.58.193.142]
  over a maximum of 30 hops:
  
  1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
  2 10 ms 8 ms 9 ms 10.71.32.1
  3 9 ms 9 ms 9 ms 100.120.104.132
  4 16 ms 13 ms 26 ms 100.120.104.12
  5 12 ms 13 ms 10 ms 68.1.1.167
  6 14 ms 13 ms 19 ms 72.14.196.240
  7 34 ms 25 ms 33 ms 108.170.247.243
  8 13 ms 17 ms 16 ms 108.170.234.41
  9 80 ms 79 ms 79 ms 209.85.251.136
  10 83 ms 79 ms 87 ms 216.239.59.169
  11 77 ms 78 ms 76 ms 108.170.240.193
  12 87 ms 77 ms 78 ms 209.85.244.85
  13 85 ms 77 ms 83 ms atl14s08-in-f142.1e100.net [216.58.193.142]
  
  Trace complete.
  
  C:\Users\mbubl>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 www.routerlogin.com [192.168.1.1]
  2 9 ms 9 ms 11 ms 10.71.32.1
  3 13 ms 8 ms 16 ms 100.120.104.134
  4 12 ms 13 ms 10 ms 100.120.104.14
  5 11 ms 11 ms 15 ms 68.1.1.61
  6 12 ms 11 ms 28 ms ip70-167-151-86.at.at.cox.net [70.167.151.86]
  7 16 ms 17 ms 15 ms 54.239.102.90
  8 54 ms 64 ms 12 ms 54.239.102.99
  9 39 ms 37 ms 35 ms 54.239.42.120
  10 * * * Request timed out.
  11 62 ms 64 ms 53 ms 52.93.12.50
  12 41 ms 35 ms 41 ms 52.93.12.37
  13 39 ms 39 ms 41 ms 52.93.12.108
  14 38 ms 37 ms 44 ms 52.93.12.131
  15 36 ms 38 ms 36 ms 205.251.232.255
  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.
- Cox_User_Who_Ne
  Contributor
  7 years ago
  Here's another one thanks.
  
  C:\Users\mbubl>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 www.routerlogin.com [192.168.1.1]
  2 9 ms 9 ms 11 ms 10.71.32.1
  3 13 ms 8 ms 16 ms 100.120.104.134
  4 12 ms 13 ms 10 ms 100.120.104.14
  5 11 ms 11 ms 15 ms 68.1.1.61
  6 12 ms 11 ms 28 ms ip70-167-151-86.at.at.cox.net [70.167.151.86]
  7 16 ms 17 ms 15 ms 54.239.102.90
  8 54 ms 64 ms 12 ms 54.239.102.99
  9 39 ms 37 ms 35 ms 54.239.42.120
  10 * * * Request timed out.
  11 62 ms 64 ms 53 ms 52.93.12.50
  12 41 ms 35 ms 41 ms 52.93.12.37
  13 39 ms 39 ms 41 ms 52.93.12.108
  14 38 ms 37 ms 44 ms 52.93.12.131
  15 36 ms 38 ms 36 ms 205.251.232.255
  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.
  
  C:\Users\mbubl>52.76.29.199
  '52.76.29.199' is not recognized as an internal or external command,
  operable program or batch file.
  
  C:\Users\mbubl>tracert 52.76.29.199
  
  Tracing route to ec2-52-76-29-199.ap-southeast-1.compute.amazonaws.com [52.76.29.199]
  over a maximum of 30 hops:
  
  1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
  2 13 ms 9 ms 12 ms 10.71.32.1
  3 9 ms 9 ms 9 ms 100.120.104.132
  4 10 ms 16 ms 9 ms 100.120.104.12
  5 12 ms 12 ms 12 ms 68.1.1.171
  6 11 ms 13 ms 13 ms 68.105.30.159
  7 184 ms 183 ms 186 ms TenGE0-0-0-16.br02.hkg15.pccwbtn.net [63.223.17.6]
  8 184 ms 200 ms 184 ms 63-217-17-42.static.pccwglobal.net [63.217.17.42]
  9 215 ms 193 ms 199 ms 52.93.35.68
  10 185 ms 184 ms 194 ms 52.93.35.77
  11 224 ms 227 ms 235 ms 54.239.43.164
  12 202 ms 209 ms 203 ms 54.240.241.119
  13 201 ms 203 ms 202 ms 52.93.8.128
  14 199 ms 215 ms 203 ms 52.93.11.43
  15 211 ms 210 ms 210 ms 52.93.11.42
  16 217 ms 225 ms 216 ms 52.93.8.139
  17 201 ms 201 ms 201 ms 203.83.223.31
  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.
  - BrianM
    Moderator
    7 years ago
    Thanks!
    
    Brian
    Cox Support Forum Moderator
- jrdn
  New Contributor II
  7 years ago
  Do you mind giving us destinations to traceroute to for testing?
  - BooPacketLoss
    New Contributor III
    7 years ago
    52.42.109.244 is the Fortnite AWS server based in Oregon that I use for testing. When I ping Google's DNS of 8.8.8.8 I get no packet loss, but whenever I play Fortnite, Rocket League or any game that uses AWS servers, I get 50%+ upstream packet loss. I'm also pretty sure that it affects Twitch live streaming by causing dropped frames because Twitch is owned by Amazon.
RomanPat
Contributor
7 years ago
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.
- RomanPat
  Contributor
  7 years ago
  NOV 12/9 UPDATE: Supervisor reassured me and maintenance crews are on there way Monday or Tuesday. I'll let everyone know how this possible solution goes
  - BooPacketLoss
    New Contributor III
    7 years ago
    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!
- RomanPat
  Contributor
  7 years ago
  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.
  - dylan123noe
    New Contributor III
    7 years ago
    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.
- RomanPat
  Contributor
  7 years ago
  12/12/2018 UPDATE: COX did send out an engineer aka bucket truck, which I visibly saw doing something, so that's confirmed. I called in later that night and talked to a supervisor, who was awesome, however notified me that the engineer said the problem was resolved.
  
  As I talked to the supervisor on the phone I notified her that I would attempt to load a few games of fortnite to see if the issue was resolved. When i loaded into the games I noticed the constant 1% -3% packet loss.
  
  AND sorry for the caps of exclamation, but the funny thing is that there is a 1% packet loss and then specifically when in moments of high action(high impact on servers) such as in a gunfight it literally in reality lags on the screen just before a player rolls up on you then in game registers that 1% or X % of data loss occurred in the fortnite net debug settings.
  
  So, I explained to the awesome rep who was understanding of the issue that it was still occurring. She then actually told me that the modem levels and cable box levels to my unit specially weren't reading the right numbers.
  
  So, as of 12/12/2018 @ 11;46 PM I'm waiting upon a new tech who will see if he can remedy thy issue as apparently the node work didn't resolve it.
  
  This is my theory: If the new tech fixes all the issues that he's reading and seems to remedy the onsite red flags and I start a game of fortnite up and that weird packet loss is still there, then it HAS to be a systematic issue via AWS services which I recommend as a business student you should remedy before it becomes apparent that you can't even route to a simple free game in 2018 as of 12/12/2018 for over thousands of paying subscribers. If anything many that pay the highest tier you offer.
  
  The above theory obviously could be incorrect as we 're just trying to find the needle in the haystack but if this is system wide for subscribers start acting now.
  
  AND to think back to it, I don't think I had packet loss before I switched to gigablast in JUNE 2018.
  
  IF the tech fixes the issue then I will report the solution as applied to my situation and retract that theory.
  - dylan123noe
    New Contributor III
    7 years ago
    I’ve had essentially everything replaced at my home. Trucks out to work on lines and nodes and it never resolved my issue. Cox will just say it’s out of their network and cease to help any further. The problem is Jeff a customer from California doesn’t have as large a voice as Tim in the IT engineering team at cox when trying to contact AWS to resolve the issue wherever it may be. We are literally stuck at a stare down with cox on who’s fault it is and who should fix it when it could’ve been fixed months ago.
RomanPat
Contributor
7 years ago
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...