Packet loss in Fortnite and Twitch/Youtube Live Streaming Very UNSTABLE
I have been a cox customer for the last 5-6 Months I have the 300/30 plan and I had little problems with live streaming to youtubewith 9000kpbs. It used to drop a little frames here and there. Now the problem is horrible it started happening like 3 weeks ago. Ive been ripping my hair out testing different things on my end. I upgraded to the Gigablast thinking docsis 3.1 would help with upload but I got 35mb upload now. My download is perfectly fine. But now I cant stream at all. I tried even using 2500kbps bitrate and I STILL DROP FRAMES. What is up with my upload now? I never seen fortnite losing packets. I avg now 5% packet loss only on my UPLOAD!. Its uplayable. I KNOW FOR A FACT ITS NOT MY HARDWARE. Its on COX end. I Tried using modem directly and both problems happens independently I have a expensive setup. SPEEDTESTS ARE LYING TO ME! I GET MY RATED SPEEDS ON SPEEDTEST.NET My hardware: Arris SB8200 Cat 7 to Router Netgear XR500 Cat 7 TO PC'S Gaming PC Ryzen 2700x, GTX 1080ti, MSI x470 Gaming Pro Carbon 16GB 3200mhz, 500GB Samsung 970 Streaming PC Ryzen 2700x GTX 1070 MSI b450 Tomahawk 16GB 3200mhz 1TB Samsung 970 Heres my modem stats Procedure Status Comment Acquire Downstream Channel 855000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables 30 Locked QAM256 855000000 Hz 5.9 dBmV 40.0 dB 0 0 1 Locked QAM256 681000000 Hz 5.7 dBmV 39.7 dB 0 0 2 Locked QAM256 687000000 Hz 5.8 dBmV 39.8 dB 0 0 3 Locked QAM256 693000000 Hz 5.9 dBmV 39.7 dB 0 0 4 Locked QAM256 699000000 Hz 6.5 dBmV 40.0 dB 0 0 9 Locked QAM256 729000000 Hz 6.1 dBmV 39.7 dB 0 0 10 Locked QAM256 735000000 Hz 6.3 dBmV 39.7 dB 0 0 11 Locked QAM256 741000000 Hz 6.1 dBmV 39.7 dB 0 0 12 Locked QAM256 747000000 Hz 6.1 dBmV 39.7 dB 0 0 17 Locked QAM256 777000000 Hz 7.5 dBmV 40.2 dB 0 0 18 Locked QAM256 783000000 Hz 7.4 dBmV 40.4 dB 0 0 19 Locked QAM256 789000000 Hz 8.0 dBmV 40.7 dB 0 0 20 Locked QAM256 795000000 Hz 8.0 dBmV 40.5 dB 0 0 21 Locked QAM256 801000000 Hz 7.7 dBmV 40.6 dB 0 0 22 Locked QAM256 807000000 Hz 7.5 dBmV 40.7 dB 0 0 25 Locked QAM256 825000000 Hz 6.9 dBmV 40.4 dB 0 0 26 Locked QAM256 831000000 Hz 6.7 dBmV 40.1 dB 0 0 27 Locked QAM256 837000000 Hz 6.3 dBmV 40.0 dB 0 0 28 Locked QAM256 843000000 Hz 6.2 dBmV 40.1 dB 0 0 29 Locked QAM256 849000000 Hz 6.1 dBmV 40.0 dB 0 0 33 Locked QAM256 357000000 Hz 5.4 dBmV 39.8 dB 0 0 34 Locked QAM256 363000000 Hz 5.5 dBmV 40.2 dB 0 0 35 Locked QAM256 369000000 Hz 5.6 dBmV 40.3 dB 0 0 36 Locked QAM256 375000000 Hz 5.8 dBmV 40.5 dB 0 0 37 Locked QAM256 381000000 Hz 5.8 dBmV 40.5 dB 0 0 38 Locked QAM256 387000000 Hz 5.9 dBmV 40.5 dB 0 0 41 Locked QAM256 405000000 Hz 6.6 dBmV 40.7 dB 0 0 42 Locked QAM256 411000000 Hz 6.3 dBmV 40.3 dB 0 0 43 Locked QAM256 417000000 Hz 6.5 dBmV 40.3 dB 0 0 44 Locked QAM256 423000000 Hz 6.3 dBmV 40.5 dB 0 0 45 Locked QAM256 429000000 Hz 7.4 dBmV 41.2 dB 0 0 46 Locked QAM256 435000000 Hz 8.0 dBmV 41.5 dB 0 0 159 Locked Other 300000000 Hz 9.1 dBmV 41.0 dB 1188425277 0 Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 1 Locked SC-QAM 38700000 Hz 6400000 Hz 37.0 dBmV 2 2 Locked SC-QAM 32300000 Hz 6400000 Hz 37.0 dBmV 3 3 Locked SC-QAM 25900000 Hz 6400000 Hz 36.0 dBmV 4 4 Locked SC-QAM 19400000 Hz 6400000 Hz 35.0 dBmV2.5KViews0likes4CommentsCox packet loss to amazon web services
Hello, For the past 9 months I have struggled with the most frustrating issue playing games using Cox as my ISP. The issue is between the connection of Cox communications and amazon web services. The games that use amazon web services ( that I play at least) are : Fortnite, Rocket League, Mordhau, and PUBG. A Cox employee will likely comment on this post that they have pinged my router and seen no traces of packet loss (because thats not what im saying), so before that happens please understand that the issue is between Cox and AWS. I need this fixed or I am done with Cox. For anyone who reads this and has the same frustrating issues, just know that Cox sweeps this under the rug by locking every post about it. Anyone who reads this who has not yet swapped to Cox and plays and AAA title games that use AWS for their servers, please do yourself a favor and stay away. FIX IT. Thanks,2.1KViews0likes7Comments