Read the forum guidelines
Here's a nice video showing the differences myself and many others are experiencing -- yet this is not a "COX problem."
Hello 402PrimeTime, Are you able to run a traceroute or ping plotter to the Fortnite server? This will allow us to see where the issue is originating. Tiffany R. Cox Support Forum Moderator
Tiffany i have the exact same problem and so do 6(east valley) other cox subscribers i know. Also 2 (west valley)cox subscribers who dont have any packet loss while playing fortnite. My home has had 3 visits along with 3 different routers with new cables all the way to the tap and still this problem continues. I have also ran my connection through 4g tethering and the game runs as it is designed with no packet loss. Just to make sure i took my xbox that i use at home to the 2 people that dont experience packet loss and I had no issues with packet loss at their location. I would love to have you guys figure this out so i dont have to switch ISP. I enjoy having you guys as my ISP but i pay $100 a month and have constant frustration over this issue that just seems to keep having the same response from Cox. You guys tell me when you ping my router you see packet loss, my signals look weak, my ds and us signals are off. Every time a tech comes out they say things look fine and swap modems. The last tech Joe was awesome, he was extremely thorough and replaced everything on my end that could cause the issues im experiencing. But the problem still happens every single time i try to play. I really believe the problem is "down the line". All the people I know that have this issue are located near me. Im at lindsay and elliot, my friend is at lindsay and guadalupe, my nephew is at higley and elliot, and some posters and youtube people are around these areas. I can send you tracert from multiple locations if needed from both packet loss and nonpacket loss locations.
im aware of how a traceroute works. Im just curious if this problem is being reviewed on a higher level. Say it is ouside the cox network but its still somewhere you are directing your traffic, we dont have the influence to have that fixed but cox sure does. Here is where the problem starts and ends, you are our provider and we only experience this issue through your service. Other ISP and 4g tethering do not have this issue connecting to the AWS so obviously this issue is with Cox. Internal or external it is on "your network" and we as consumers of your product suffer from that. It is not the AWS, if it was then all of the millions of gamers would be experiencing this on their connection. 402primetime has shown exactly what happens when you use a connection to AWS that is not provided by Cox. 0 packet loss. Every single game every single second is packet loss from 1% to 40% and higher using your service. Once cox is removed from the equation the problem goes away completely. I have followed through these post for over 2 months on this issue hoping for it to be fixed. How many traceroutes from how many people do we need to figure it out. I can run pingplotter,smokeping, and wireshark but this doesnt allow uploads or links. I can email to you and who ever would review it all the information and data collected from those programs. Please lets find out how to get this fixed, you guys have great customer service and are always willing to try to solve these issues. Lets get this one fixed and we can all take pride that we figured this out!
P.s. im playing right now and having constant spikes of up to 30% upload packetloss
Oh, Becky knows all too well. She likely won't respond, but I don't blame her. She has zero clue or ability to fix this issue. These people on here are proving themselves to be more and more incompetent or low level worker bees.
Playing on LTE right now...smh! Packet loss so bad tonight had too switch over before I lost it. I literally feel like I'm throwing money away!
Here is from another user using udp, i am trying to reply to widermouthopen but it will not post a response.
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] 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%)