New Contributor III
•
17 Messages
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
Related Content
Closed
1
0
Closed
2
0
Closed
8
Accepted Solution
Closed
15
0
Closed
1
0

SufferingFromPa
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
-----------------------------------------------------------
2
0
Toomuchbob
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.
4
0
RayR
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.
1
sjo102784
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
0
0
sjo102784
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
2
0
Cox_User_Who_Ne
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.
5
RomanPat
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.
15
Sm31ly
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.
4
0
RomanPat
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...
0
RomanPat
Contributor
•
42 Messages
as of 12/28/2018 this is still an issue for me...
1
RomanPat
Contributor
•
42 Messages
as of 12/30/2018 this is still a problem
11
0
Janet01
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.
6
0
Battlefieldpack
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.
0
RomanPat
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!
0
0
Janet01
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.
3
0