So basically I've been getting high upload packet loss (what fortnite stats show it as) lately and I'm not sure why
Weird thing about is it really flairs up when I try to play with my brother, who is also wired to the same router. (we are both wired), I'll play solo for hours and not have a problem, then I try to duo with him and boom, 200% packet loss that sometimes lasts for hours.
Internet provider is Cox

I've narrowed down a few solutions we've tried
*Can't be modem or router, we bought brand new ones a day ago over $200
*Shouldn't be my ethernet cable, because when I lag, my brother lags, who is also wired up to the same router
*Shouldn't be my computer port because again, my brother lags at the same time I do
*I've talked to cox support, they've ran troubleshooting tests on it or whatever, said they fixed it but obviously not. The next step they offered is to have someone come out and look at the wiring
*I've tried doing ping tests on CMD, all came back low ms and no packet loss whatsoever

Really at a loss as to what to try next, other than paying for someone to come look at it, who will probably suggest some dumb shit I've already tried.
Let me know if you have any idea whats going on

is you isp providing enough bandwith for two of you to play a demanding mmo?
1 person playing a game while another browses the web is totally different than 2 ppl playing a game.

Already bought brand new modem and router, problem is still very there
Google speed test - 65 down 7.78 up (I pay for 150/10)
Cox speed test - 165 down 10.2 up
Those differ a ton. Idk why?



Well I've never had this problem before, maybe a month ago it randomly started. We used to play together all the time before this happened without problems.
That being said we should have more than enough bandwith considering I've never changed anything with our plans or setups.

Sorry for late replies, I've been busy and forgot to post.
Some updates on what I've done.
- paid for cox employee to come fix it. He replaced cables inside and outside, says they were old and were probably the problem
Funny thing is the problem still persists, big suprise.
It seemed to have fixed some of the problem, considering I can play throughout the day no problem until about 7pm. Around then the internet goes back to shit for hours, usually doesn't return until the next morning.
I have no clue why it does this, and I'm tired of it.

EDIT - May be important to add the detail that I'm literally the only fucking one connected to the internet around 7pm.
Edit 2 - Think a CMD ping may be important?

Pinging www.google.com [172.217.9.4] with 32 bytes of data:
Reply from 172.217.9.4: bytes=32 time=20ms TTL=55
Request timed out.
Request timed out.
Reply from 172.217.9.4: bytes=32 time=57ms TTL=55

Ping statistics for 172.217.9.4:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 57ms, Average = 38ms

C:\Users\tyson>ping www.google.com -t

Pinging www.google.com [216.58.218.100] with 32 bytes of data:
Request timed out.
Reply from 216.58.218.100: bytes=32 time=42ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.218.100: bytes=32 time=51ms TTL=55
Reply from 216.58.218.100: bytes=32 time=50ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.218.100: bytes=32 time=37ms TTL=55
Reply from 216.58.218.100: bytes=32 time=29ms TTL=55
Reply from 216.58.218.100: bytes=32 time=42ms TTL=55
Reply from 216.58.218.100: bytes=32 time=27ms TTL=55
Request timed out.
Reply from 216.58.218.100: bytes=32 time=29ms TTL=55
Reply from 216.58.218.100: bytes=32 time=27ms TTL=55
Request timed out.
Reply from 216.58.218.100: bytes=32 time=48ms TTL=55
Reply from 216.58.218.100: bytes=32 time=30ms TTL=55
Reply from 216.58.218.100: bytes=32 time=29ms TTL=55
Reply from 216.58.218.100: bytes=32 time=41ms TTL=55
Reply from 216.58.218.100: bytes=32 time=26ms TTL=55
Request timed out.
Reply from 216.58.218.100: bytes=32 time=37ms TTL=55
Request timed out.
Reply from 216.58.218.100: bytes=32 time=60ms TTL=55
Reply from 216.58.218.100: bytes=32 time=44ms TTL=55
Request timed out.
Request timed out.
Reply from 216.58.218.100: bytes=32 time=35ms TTL=55
Reply from 216.58.218.100: bytes=32 time=96ms TTL=55
Request timed out.
Reply from 216.58.218.100: bytes=32 time=50ms TTL=55

Ping statistics for 216.58.218.100:
Packets: Sent = 37, Received = 20, Lost = 17 (45% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 96ms, Average = 41ms

This post was edited by Swany on Jun 1 2018 10:10pm

If problem re-appears at 7pm everyday, I'd say it's Cox or possibly the Fortnite servers.

Unless your computer starts doing something else at 7 pm every night.

I'd rule out Fortnite servers then since everyone else can play fine. Guess I'll just talk to cox again and try to get them to fix it.