JUST ORDERED CENTURYLINK - Goodbye Cox and Packet Loss Issues
Cox Team - You're officially being fired! This move is a direct result of your failure to remedy gross packet loss issues. I and many others did our part to help solve the problem - actually far beyond what's normally expected of customers. I've spent countless hours of my personal time on the phone, forums, running tests, talking to techs, swapping equipment, etc. all because I wanted to help fix the issue and remain a customer, after all I've been a loyal one for 12+ years. Most depressing thing about this situation is Cox's response - "It's not on our end." You see, regardless of what the true technical issue may be or where it truly resides, Cox ISthe "internet" to the end user. The technical components you leverage to provide services are not your customers concerns. Fact of the matter is your service, and it's been proven, is part of the problem, thus is your responsibility to work to correct, through whatever means necessary. I'm a manager in IT and this concept is not rocket science. I hope this continues to be a thorn in your side and I strongly urge customers who are experiencing this issue to jump ship and impress upon Cox's upper management that this IS a problem and it's not going away. I've included below a ton of documentation to illustrate how rampant this issue is for everyone out there. Forum Posts: https://forums.cox.com/forum_home/internet_forum/f/internet-forum/21713/cox-fortnite-packet-loss---customers-please-read- MY PERSONAL RECAP http://www.dslreports.com/forum/r32118471-CA-Fortnite-Packet-Loss-on-West-Coast-Servers-Southern-California http://www.dslreports.com/forum/r32113456-Horrible-packet-loss-for-games-like-Fortnite-COX-Communications http://www.dslreports.com/forum/r32136875-What-is-acceptable-packet-loss http://www.dslreports.com/forum/r32135334-Gigablast-Evening-packet-loss-after-Gigablast-upgrade http://www.dslreports.com/forum/r32093285-AZ-Packet-Loss-in-First-and-Second-Hops http://www.dslreports.com/forum/r32087813-OK-weird-packet-loss-issues-techs-say-there-is-nothing-wrong http://www.dslreports.com/forum/r32108838-PHX-Packet-Loss-via-Level-3 www.dslreports.com/.../r32045842-AZ-Packet-loss-Chandler forums.cox.com/.../high-ping-spikes-and-packet-loss https://www.reddit.com/r/CoxCommunications/comments/8y2eci/upstream_packet_loss_phoenix/ https://www.reddit.com/r/FortNiteBR/comments/94cw0p/packet_loss_information_and_how_to_fix_lag/ https://forums.cox.com/forum_home/internet_forum/f/internet-forum/19622/consistent-packet-loss https://forums.cox.com/forum_home/internet_forum/f/internet-forum/21756/fortnite-packet-loss---cox-vs-verizon-lte https://forums.cox.com/forum_home/internet_forum/f/internet-forum/21288/severe-packet-loss-upload-to-amazon-web-services-fortnite https://forums.cox.com/forum_home/internet_forum/f/internet-forum/21209/cox-ruining-fortnite-and-live-streaming-experience-with-packet-loss https://forums.cox.com/forum_home/internet_forum/f/internet-forum/21794/packet-loss-gaming-and-cloud-connections forums.cox.com/.../packet-loss-with-current-route-to-lotro-gls https://forums.cox.com/forum_home/internet_forum/f/internet-forum/21455/santa-barbara-ca---significant-packet-loss-in-route-to-netflix https://forums.cox.com/forum_home/internet_forum/f/internet-forum/21663/fortnite-packet-loss twitter.com/search Video Evidence: https://www.youtube.com/watch?v=5Tx9MO2aAsQ https://www.youtube.com/watch?v=itzhCKiqpkQ&t=362s https://www.youtube.com/watch?v=MPs3LaQgFhk&t=57s https://www.youtube.com/watch?v=3vLLSYGzsB8&t=43s https://www.youtube.com/watch?v=uLv0beSLdD8&t=3s https://www.youtube.com/watch?v=iaqDq1IlQVs&t=531s https://www.youtube.com/watch?v=loG2tLRw4CE www.youtube.com/watch
Unable to play Fortnite on AWS West Coast Servers - Southern California
From San Diego, California Approximately 10 days ago, My brother and I started experiencing extreme packet loss and constant ping/lag spikes in Fortnite that appears throughout the day but gets worse during peak hours (5pm - thoughout the night). My speeds are perfectly fine, I'm getting around 400mpbs download and 100mbps upload, yet when I'm in-game, I get major packet loss and ping spikes making the game unplayable.Note:My internet is fine, I can stream HD videos, surf the web, download and upload files at lightning speed. Variables that I have ruled out: - Router. I've tried multiple routers, made sure they were using the latest firmwares, tried QoS and still had an issue on both. I only use hardwired so it not wireless signal issue. We've tried using cat-5e and cat6 ethernet cables too and still no success. - PC issues. I factory resetted both our PC's and reinstalled Windows/ drivers and made sure my drivers are up to date. I don't have any anti-viruses programs so that's ruled out. It is also not a Fortnite server issue as I play with multiple friends from California in the same lobby as me and they do not have any issues. But they have different ISP's.Both PC builds have a GTX 1060 6gb, i7-8700k, 16gb drr4 RAM. All video settings are on low. It is 100% not a performance issue. After 10 days of troubleshooting and dealing with this demon, I have actually pinpointed the problem. It is how COX interacts with the Fortnite West Coast AWS servers. I played 20 games on east coast servers. Paying very close attention to the in-game Net Debug stats,20/20games on east coast servers, were flawless bearing 0% packet loss and no lag spikes or fluctuations in ping. I played 20 games on west coast servers. Paying very close attention to the in-game Net Debug stats, only4/20games on west coast servers yielded no problems. The other16, however, had major packet loss (stats showed mostly download packet loss and some upload packet loss) and unstable ping. Please escalate this issue to someone who specializes in networking and can fix this serious problem. I am a streamer who streams this game as a source of income and there are no other ISP's in my area and moving somewhere else is not an option for me. So I am stuck with this unfortunate issue. Evidence that it's not just my hardware: Cox forum post about members having same issue: https://forums.cox.com/forum_home/internet_forum/f/internet-forum/21209/cox-ruining-fortnite-and-live-streaming-experience-with-packet-loss/80372#80372 Fortnite forum post about members having same issue: https://www.epicgames.com/fortnite/forums/bug-reports/battle-royale-aa/681327-fortnite-packet-loss-and-ping-lag-spikes-as-of-recently-9-04-2018 Common Denominator: Our ISP is COX and are from Southern California. Here are some trace routes while connected to a AWS west coast server with heavy packet loss (up to 40% download packet loss | up to 12% upload packet loss): Tracing route toec2-52-71-66-128.compute-1.amazonaws.com[52.71.66.128] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 2 ms 1 ms 1 msip68-107-57-129.sd.sd.cox.net[68.107.57.129] 3 1 ms 2 ms 1 msip68-101-129-110.sd.sd.cox.net[68.101.129.110] 4 3 ms 2 ms 2 msvisthbrc01-get0702.sd.sd.cox.net[68.6.8.119] 5 32 ms 32 ms 32 msdalsbprj02-ae2.0.rd.dl.cox.net[68.1.2.121] 6 32 ms 31 ms 31 ms 52.46.167.212 7 39 ms 43 ms 32 ms 54.239.105.121 8 32 ms 32 ms 32 ms 176.32.125.191 9 * * * Request timed out. 10 70 ms 81 ms 69 ms 54.239.46.0 11 66 ms 66 ms 66 ms 54.240.229.189 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 85 ms 106 ms 89 ms 54.239.110.247 16 68 ms 67 ms 67 ms 52.93.26.62 17 83 ms 98 ms 79 ms 52.93.27.205 18 66 ms 65 ms 66 ms 52.93.25.11 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. Tracing route toec2-34-235-172-107.compute-1.amazonaws.com[34.235.172.107] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 2 ms 1 ms 1 msip68-107-57-129.sd.sd.cox.net[68.107.57.129] 3 1 ms 1 ms 1 msip68-101-129-110.sd.sd.cox.net[68.101.129.110] 4 3 ms 2 ms 5 msvisthbrc01-get0702.sd.sd.cox.net[68.6.8.119] 5 32 ms 32 ms 32 msdalsbbrj02-ae3.0.rd.dl.cox.net[68.1.5.134] 6 31 ms 31 ms 33 ms 72.21.221.202 7 48 ms 51 ms 36 ms 176.32.125.150 8 32 ms 32 ms 31 ms 176.32.125.159 9 * * * Request timed out. 10 70 ms 77 ms 72 ms 54.239.43.206 11 65 ms 64 ms 64 ms 54.239.43.96 12 * * * Request timed out. 13 82 ms 92 ms 78 ms 54.239.111.166 14 63 ms 62 ms 62 ms 54.239.110.182 15 80 ms 87 ms 87 ms 54.239.110.187 16 72 ms 68 ms 70 ms 52.93.25.114 17 * * * Request timed out. 18 66 ms 65 ms 65 ms 52.93.24.127 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. Tracing route toec2-34-237-197-55.compute-1.amazonaws.com[34.237.197.55] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 1 ms 1 ms 1 msip68-107-57-129.sd.sd.cox.net[68.107.57.129] 3 1 ms 1 ms 1 msip68-101-129-110.sd.sd.cox.net[68.101.129.110] 4 3 ms 2 ms 2 msvisthbrc01-get0702.sd.sd.cox.net[68.6.8.119] 5 32 ms 32 ms 32 msdalsbbrj02-ae3.0.rd.dl.cox.net[68.1.5.134] 6 32 ms 31 ms 37 ms 52.46.167.210 7 48 ms 43 ms 47 ms 54.239.105.99 8 32 ms 32 ms 31 ms 176.32.125.157 9 * * * Request timed out. 10 69 ms 80 ms 73 ms 54.239.46.4 11 66 ms 66 ms 67 ms 54.240.229.217 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 86 ms 78 ms 86 ms 54.239.110.227 16 66 ms 66 ms 66 ms 52.93.26.74 17 69 ms 81 ms 109 ms 52.93.27.221 18 66 ms 65 ms 66 ms 72.21.197.243 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. Thanks for your time.HIGH PING SPIKES AND PACKET LOSS
I am using a ARRIS DG2460 router and always get packet loss for both up and down ranging from 4-60% packet loss playing Fortnite. I also get ping spikes that last for minutes and they reach up to 1,100 ms. 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 5 ms 12 ms 8 ms 192.168.0.1 2 14 ms 19 ms 19 ms 10.156.20.1 3 16 ms 20 ms 18 ms 68.6.9.234 4 15 ms 29 ms 19 ms 100.120.108.20 5 27 ms 29 ms 29 ms 68.1.1.167 6 22 ms 23 ms 28 ms 52.95.218.216 7 39 ms 107 ms 37 ms 54.239.102.102 8 26 ms * 23 ms 54.239.102.111 9 61 ms 49 ms 62 ms 54.239.42.120 10 * * * Request timed out. 11 53 ms 52 ms 46 ms 52.93.13.14 12 43 ms 49 ms 59 ms 52.93.12.255 13 66 ms 68 ms 59 ms 52.93.12.254 14 46 ms 49 ms 49 ms 52.93.13.25 15 48 ms 48 ms 49 ms 52.93.15.217 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.
