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."
www.youtube.com/watch
I wish I could sue this terrible ISP.
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
Microsoft Windows [Version 10.0.17134.285](c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\Kyle>tracert 52.42.109.244 -- WITH COX CONNECTION (MY CONNECTION)
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 7 ms 6 ms 8 ms 10.53.128.1 3 7 ms 8 ms 9 ms 100.127.74.46 4 18 ms 7 ms 14 ms 100.120.100.16 5 19 ms 18 ms 25 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14] 6 30 ms 20 ms 39 ms 52.95.218.216 7 21 ms 33 ms 42 ms 54.239.102.18 8 20 ms 21 ms 22 ms 54.239.102.27 9 45 ms 55 ms 66 ms 54.239.42.120 10 * * * Request timed out. 11 61 ms 46 ms 46 ms 52.93.13.46 12 44 ms 53 ms 44 ms 52.93.13.35 13 49 ms * 72 ms 52.93.12.74 14 42 ms 52 ms 42 ms 52.93.12.93 15 43 ms 44 ms 48 ms 54.239.48.183 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.
C:\Users\Kyle>tracert 52.42.109.244 -- WITH LTE CONNECTION (VERIZON)
1 2 ms 2 ms 2 ms 172.20.10.1 2 67 ms 31 ms 17 ms 5.sub-66-174-32.myvzw.com [66.174.32.5] 3 * * * Request timed out. 4 * * * Request timed out. 5 29 ms 31 ms 28 ms 178.sub-69-83-173.myvzw.com [69.83.173.178] 6 32 ms 19 ms 18 ms 194.sub-69-83-173.myvzw.com [69.83.173.194] 7 43 ms 22 ms 30 ms 84.sub-69-83-162.myvzw.com [69.83.162.84] 8 252 ms 140 ms 28 ms 73.sub-66-174-29.myvzw.com [66.174.29.73] 9 33 ms 18 ms 18 ms 205.158.30.5.ptr.us.xo.net [205.158.30.5] 10 61 ms 40 ms 39 ms 207.88.14.132.ptr.us.xo.net [207.88.14.132] 11 55 ms 38 ms 39 ms 207.88.12.222.ptr.us.xo.net [207.88.12.222] 12 53 ms 39 ms 37 ms te0-12-1-0.rar3.chicago-il.us.xo.net [207.88.12.141] 13 43 ms 41 ms 36 ms 207.88.12.142.ptr.us.xo.net [207.88.12.142] 14 57 ms 37 ms 38 ms 207.88.13.225.ptr.us.xo.net [207.88.13.225] 15 51 ms 37 ms 39 ms 72.21.221.152 16 57 ms 42 ms 37 ms 54.240.243.48 17 64 ms 41 ms 39 ms 54.240.243.57 18 * * * Request timed out. 19 68 ms 59 ms 86 ms 52.93.128.22 20 100 ms 69 ms 70 ms 54.239.44.105 21 * * * Request timed out. 22 108 ms 79 ms 85 ms 52.93.15.50 23 97 ms 96 ms 108 ms 52.93.14.254 24 105 ms 87 ms 69 ms 52.93.15.17 25 91 ms 69 ms 81 ms 52.93.240.47 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
Trace complete.
C:\Users\Owner>tracert 52.42.109.244 -- WITH CENTURYLINK CONNECTION
1 <1 ms <1 ms <1 ms 192.168.1.1 2 <1 ms <1 ms <1 ms modem.domain [192.168.0.1] 3 23 ms 20 ms 6 ms 97-124-100-254.phnx.qwest.net [97.124.100.254] 4 5 ms 6 ms 5 ms phnx-agw1.inet.qwest.net [75.160.238.249] 5 37 ms 53 ms 37 ms tuk-edge-13.inet.qwest.net [67.14.4.206] 6 39 ms 47 ms 43 ms 65-122-235-174.dia.static.centurylink.net [65.122.235.174] 7 52 ms 52 ms 51 ms 52.95.54.180 8 38 ms 38 ms 41 ms 52.95.54.195 9 * * * Request timed out. 10 48 ms 45 ms 46 ms 54.239.43.5 11 * * * Request timed out. 12 46 ms 47 ms 47 ms 52.93.15.42 13 56 ms 44 ms 44 ms 52.93.15.35 14 57 ms 49 ms 49 ms 52.93.14.110 15 44 ms 44 ms 44 ms 52.93.14.135 16 45 ms 43 ms 44 ms 52.93.240.41 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.
Microsoft Windows [Version 10.0.17134.286](c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\Michael>tracert 52.42.109.244 -- WITH COX CONNECTION (USER IN CHANDLER)
1 3 ms 3 ms 2 ms router.asus.com [192.168.1.1] 2 10 ms 9 ms 8 ms 10.35.148.1 3 18 ms 14 ms 10 ms 100.127.73.168 4 8 ms 10 ms 11 ms 100.120.100.6 5 32 ms 22 ms 23 ms 68.1.4.252 6 22 ms 22 ms 22 ms 52.95.218.214 7 35 ms 29 ms 37 ms 54.239.102.16 8 21 ms 23 ms 22 ms 54.239.102.23 9 46 ms 49 ms 44 ms 54.239.42.116 10 * * * Request timed out. 11 49 ms 49 ms 48 ms 52.93.12.162 12 47 ms 45 ms 49 ms 52.93.12.141 13 61 ms 85 ms 50 ms 52.93.12.32 14 46 ms 46 ms 46 ms 52.93.12.57 15 46 ms 49 ms 45 ms 52.93.13.65 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.
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.