Unable to play Fortnite on AWS West Coast Servers - Southern California

Question

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.&nbsp;Note:&nbsp;My internet is fine, I can stream HD videos, surf the web, download and upload files at lightning speed.&nbsp;

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.&nbsp;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,&nbsp;20/20&nbsp;games 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, only&nbsp;4/20&nbsp;games on west coast servers yielded no problems. The other&nbsp;16, 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.
&nbsp;
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):
&nbsp;

Tracing route to&nbsp;ec2-52-71-66-128.compute-1.amazonaws.com&nbsp;[52.71.66.128]
over a maximum of 30 hops:

&nbsp; 1&nbsp; &nbsp; &lt;1 ms&nbsp; &nbsp; &lt;1 ms&nbsp; &nbsp; &lt;1 ms&nbsp; 192.168.1.1
&nbsp; 2&nbsp; &nbsp; &nbsp;2 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp;&nbsp;ip68-107-57-129.sd.sd.cox.net&nbsp;[68.107.57.129]
&nbsp; 3&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;2 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp;&nbsp;ip68-101-129-110.sd.sd.cox.net&nbsp;[68.101.129.110]
&nbsp; 4&nbsp; &nbsp; &nbsp;3 ms&nbsp; &nbsp; &nbsp;2 ms&nbsp; &nbsp; &nbsp;2 ms&nbsp;&nbsp;visthbrc01-get0702.sd.sd.cox.net&nbsp;[68.6.8.119]
&nbsp; 5&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp;&nbsp;dalsbprj02-ae2.0.rd.dl.cox.net&nbsp;[68.1.2.121]
&nbsp; 6&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 31 ms&nbsp; &nbsp; 31 ms&nbsp; 52.46.167.212
&nbsp; 7&nbsp; &nbsp; 39 ms&nbsp; &nbsp; 43 ms&nbsp; &nbsp; 32 ms&nbsp; 54.239.105.121
&nbsp; 8&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp; 176.32.125.191
&nbsp; 9&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;10&nbsp; &nbsp; 70 ms&nbsp; &nbsp; 81 ms&nbsp; &nbsp; 69 ms&nbsp; 54.239.46.0
&nbsp;11&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 66 ms&nbsp; 54.240.229.189
&nbsp;12&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;13&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;14&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;15&nbsp; &nbsp; 85 ms&nbsp; &nbsp;106 ms&nbsp; &nbsp; 89 ms&nbsp; 54.239.110.247
&nbsp;16&nbsp; &nbsp; 68 ms&nbsp; &nbsp; 67 ms&nbsp; &nbsp; 67 ms&nbsp; 52.93.26.62
&nbsp;17&nbsp; &nbsp; 83 ms&nbsp; &nbsp; 98 ms&nbsp; &nbsp; 79 ms&nbsp; 52.93.27.205
&nbsp;18&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 65 ms&nbsp; &nbsp; 66 ms&nbsp; 52.93.25.11
&nbsp;19&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;20&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;21&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;22&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;23&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;24&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;25&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;26&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;27&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;28&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;29&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;30&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.

Trace complete.

Tracing route to&nbsp;ec2-34-235-172-107.compute-1.amazonaws.com&nbsp;[34.235.172.107]
over a maximum of 30 hops:

&nbsp; 1&nbsp; &nbsp; &lt;1 ms&nbsp; &nbsp; &lt;1 ms&nbsp; &nbsp; &lt;1 ms&nbsp; 192.168.1.1
&nbsp; 2&nbsp; &nbsp; &nbsp;2 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp;&nbsp;ip68-107-57-129.sd.sd.cox.net&nbsp;[68.107.57.129]
&nbsp; 3&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp;&nbsp;ip68-101-129-110.sd.sd.cox.net&nbsp;[68.101.129.110]
&nbsp; 4&nbsp; &nbsp; &nbsp;3 ms&nbsp; &nbsp; &nbsp;2 ms&nbsp; &nbsp; &nbsp;5 ms&nbsp;&nbsp;visthbrc01-get0702.sd.sd.cox.net&nbsp;[68.6.8.119]
&nbsp; 5&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp;&nbsp;dalsbbrj02-ae3.0.rd.dl.cox.net&nbsp;[68.1.5.134]
&nbsp; 6&nbsp; &nbsp; 31 ms&nbsp; &nbsp; 31 ms&nbsp; &nbsp; 33 ms&nbsp; 72.21.221.202
&nbsp; 7&nbsp; &nbsp; 48 ms&nbsp; &nbsp; 51 ms&nbsp; &nbsp; 36 ms&nbsp; 176.32.125.150
&nbsp; 8&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 31 ms&nbsp; 176.32.125.159
&nbsp; 9&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;10&nbsp; &nbsp; 70 ms&nbsp; &nbsp; 77 ms&nbsp; &nbsp; 72 ms&nbsp; 54.239.43.206
&nbsp;11&nbsp; &nbsp; 65 ms&nbsp; &nbsp; 64 ms&nbsp; &nbsp; 64 ms&nbsp; 54.239.43.96
&nbsp;12&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;13&nbsp; &nbsp; 82 ms&nbsp; &nbsp; 92 ms&nbsp; &nbsp; 78 ms&nbsp; 54.239.111.166
&nbsp;14&nbsp; &nbsp; 63 ms&nbsp; &nbsp; 62 ms&nbsp; &nbsp; 62 ms&nbsp; 54.239.110.182
&nbsp;15&nbsp; &nbsp; 80 ms&nbsp; &nbsp; 87 ms&nbsp; &nbsp; 87 ms&nbsp; 54.239.110.187
&nbsp;16&nbsp; &nbsp; 72 ms&nbsp; &nbsp; 68 ms&nbsp; &nbsp; 70 ms&nbsp; 52.93.25.114
&nbsp;17&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;18&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 65 ms&nbsp; &nbsp; 65 ms&nbsp; 52.93.24.127
&nbsp;19&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;20&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;21&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;22&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;23&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;24&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;25&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;26&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;27&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;28&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;29&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;30&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.

Trace complete.

Tracing route to&nbsp;ec2-34-237-197-55.compute-1.amazonaws.com&nbsp;[34.237.197.55]
over a maximum of 30 hops:

&nbsp; 1&nbsp; &nbsp; &lt;1 ms&nbsp; &nbsp; &lt;1 ms&nbsp; &nbsp; &lt;1 ms&nbsp; 192.168.1.1
&nbsp; 2&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp;&nbsp;ip68-107-57-129.sd.sd.cox.net&nbsp;[68.107.57.129]
&nbsp; 3&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp; &nbsp; &nbsp;1 ms&nbsp;&nbsp;ip68-101-129-110.sd.sd.cox.net&nbsp;[68.101.129.110]
&nbsp; 4&nbsp; &nbsp; &nbsp;3 ms&nbsp; &nbsp; &nbsp;2 ms&nbsp; &nbsp; &nbsp;2 ms&nbsp;&nbsp;visthbrc01-get0702.sd.sd.cox.net&nbsp;[68.6.8.119]
&nbsp; 5&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp;&nbsp;dalsbbrj02-ae3.0.rd.dl.cox.net&nbsp;[68.1.5.134]
&nbsp; 6&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 31 ms&nbsp; &nbsp; 37 ms&nbsp; 52.46.167.210
&nbsp; 7&nbsp; &nbsp; 48 ms&nbsp; &nbsp; 43 ms&nbsp; &nbsp; 47 ms&nbsp; 54.239.105.99
&nbsp; 8&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 32 ms&nbsp; &nbsp; 31 ms&nbsp; 176.32.125.157
&nbsp; 9&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;10&nbsp; &nbsp; 69 ms&nbsp; &nbsp; 80 ms&nbsp; &nbsp; 73 ms&nbsp; 54.239.46.4
&nbsp;11&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 67 ms&nbsp; 54.240.229.217
&nbsp;12&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;13&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;14&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;15&nbsp; &nbsp; 86 ms&nbsp; &nbsp; 78 ms&nbsp; &nbsp; 86 ms&nbsp; 54.239.110.227
&nbsp;16&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 66 ms&nbsp; 52.93.26.74
&nbsp;17&nbsp; &nbsp; 69 ms&nbsp; &nbsp; 81 ms&nbsp; &nbsp;109 ms&nbsp; 52.93.27.221
&nbsp;18&nbsp; &nbsp; 66 ms&nbsp; &nbsp; 65 ms&nbsp; &nbsp; 66 ms&nbsp; 72.21.197.243
&nbsp;19&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;20&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;21&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;22&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;23&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;24&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;25&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;26&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;27&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;28&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;29&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.
&nbsp;30&nbsp; &nbsp; &nbsp;*&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp; &nbsp; *&nbsp; &nbsp; &nbsp;Request timed out.

Trace complete.

Thanks for your time.

becky · Answer

Hi Juices, your traceroutes seem to show normal ICMP deprioritization. Please explain what you mean by "it is how COX interacts with the Fortnite West Coast AWS servers." -Becky, Cox Support Forums Moderator

402primetime · Answer

COX Moderators,&nbsp;
Unsure what you'd be looking for from us from a technical perspective; however, this is a VERY real problem experienced by hundreds if not thousands of COX users specifically playing on the West Coast. Do some basic homework and you'll understand the problem. Cox should be on a call right now with someone from EPIC games and AWS to better understand the problem, and not just blanketly respond with "it's not on COX's end" because this is clearly specific to COX connections. This problem is recent, real and needs to be addressed. Else, I'm assuming a large contingency of folks will be thinking as I am (12+ yr customer), to jump to another provider who doesn't have these issues present. It's understandable that playing a video game and its general performance is probably not high on the priority list, but this is literally one of the most popular titles ever and provides entertainment/enjoyment to some of us. I've literally resigned myself to not playing anymore, which is disappointing because it's literally the only title I play anymore.&nbsp;

ekayze · Answer

Ive been having the same issue as your and I am from San Diego also. The past week I gave Haste a try and it fixes these packet loss issues I am having.
You can give the program a trial and see if it works out for you. I know this is not a real fix but I love to game and I needed to find a solution since Cox won't fix these issues for a very long time.

juices · Answer

If you read the above, I mentioned that when I'm in-game(Fortnite), If I set the region I'm playing on to "West Coast" I start to experience severe packet loss/lagging issues, however, when I set the region I'm playing on to "east-coast", I can play perfectly fine with no packet loss/lag. However, since I live in California it is not preferable to play on east-coast servers due to high pings, which means we are playing at a huge delay/disadvantage. As I stated above, I thoroughly tested 20 games each on both west and east coast servers and only had issues on the&nbsp;Fortnite west-coast servers, especially during peak hours. So I'm assuming the problem is how COX internet interacts with the "Fortnite West-Coast servers." Seems kinda silly that I'm making a big deal out of a video game, but I stream/play Fortnite as a source of income so this is a serious issue for me. This problem occurs on a daily basis. Everyday, I've been trying to research/find different ways to fix the problem but nothing works, seems like this is an issue on COX's end and is out of my reach. I've emailed support and they said they currently are investigating it, do you know if they found out what the problem is yet? It has been over two weeks.

juices · Answer

I've heard of it, and I'm looking for a permanent solution, are you seriously paying $15 a month for it or you just doing the 14-day trial?&nbsp;

Forum Discussion

Unable to play Fortnite on AWS West Coast Servers - Southern California

Related Content

Packet Loss Southern California (Fortnite)

Packet Loss in Southern California (Fortnite)

Fortnite Packet Loss

Southern California poor PBS transmission

Cox ruining Fortnite and Live Streaming experience with PACKET LOSS

Recent Discussions

Some devices can’t connect to my panoramic wifi gateway but some can

Flickering? Fluctuating? speed

Unable to work due to internet dropping out.

Internet a joke

Internet Not Working