I keep getting lag spikes like every 20 seconds while playing Fortnite

[Shakeel_]

Hello,

I get lag spikes like every, let's say 20 seconds, while playing Fortnite, and it's not good, as it ruins the fun for me. My internet is fine, I have the 73mbps plan, and get approximately 54mbps. I even tried changing to Wi-Fi 6 compatibility and Wi-Fi 5 as well, I think it did help a bit,  but I'm not sure, I kept it on Wi-Fi 6 compatibility.

I've had so many technical problems when moving into my new home, a good afternoon with friends playing Fortnite is so good, so I would LOVE a fix. 😅

[Shakeel_]

Yeah, exactly, I put it out there on the ground, and it's like very near my room, I can see it outside when moving my chair back a little, and looking back, but my father put it inside temporarily to do something.

[JimM11]

@Shakeel_ There are two very import things, one is the position of the router, and second if you game, cable back from the Router to the PC with Ethernet, forget you D Link wireless can be FRAUGHT with problems! Both may not be possible so the work around then has to happen.

[Shakeel_]

It wasn't the DLINK, I tried a ping test on my phone and got a lag spike. Do you think it could be a NAT issue? I have UPNP on.

[JimM11]

@Shakeel_ What do you get when you run a 5 min test pc to the EE Router. Cmd is ping 192.168.1.254 -n 300. Post the final result back and see how many high pings you get by looking up the output file. The test i run for the 5 minute period, with 3 catches in that time, more than likely the wife's wireless you tube stream all wireless was on, and done from my wireless connected laptop. Results below that i have highlighted.

Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=81ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64

Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=114ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64

Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=104ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.1.254:
Packets: Sent = 300, Received = 300, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 114ms, Average = 3ms

Same ping to EE but wireless connected to my Asus Router 5g band
only one instance and the grouping was all together.

Reply from 192.168.1.254: bytes=32 time=2ms TTL=63
Reply from 192.168.1.254: bytes=32 time=25ms TTL=63
Reply from 192.168.1.254: bytes=32 time=78ms TTL=63
Reply from 192.168.1.254: bytes=32 time=79ms TTL=63
Reply from 192.168.1.254: bytes=32 time=2ms TTL=63

Ping statistics for 192.168.1.254:
Packets: Sent = 300, Received = 300, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 79ms, Average = 2ms

[JimM11]

@Shakeel_ Ten minute test which is running with the laptop on wireless concurrent test, 1st is the desktop wired Ethernet, and 2nd below it is the Laptop, with the time to walk hit enter to get it started.

Desktop PC (Ethernet)

Ping statistics for 192.168.1.254:
Packets: Sent = 600, Received = 600, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 14ms, Average = 1ms

Laptop (Wireless)

Ping statistics for 192.168.1.254:
Packets: Sent = 600, Received = 600, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 57ms, Average = 3ms

[Shakeel_]

I have tried the "ping 8.8.8.8" command before, but thank you for sending this to me, I like that it's a 5 minutes test unlike the short tests I was doing on those websites and my cmd.

[JimM11]

@Shakeel_ Correct, was pinging the EE Router from 2 different sources, all my wireless connected etc, to try and see if and when the EE Router gets busy and cannot respond, i have nothing major to worry about, and have a way more complicated network setup, multiple routers, extenders, powerline etc, but i know how everything behaves.

One bad device can kill a network, on its internal side, external you have no control over.

[JimM11]

@Shakeel_ Until you connect an Ethernet cable from your PC to the Router, that will be the only good test, wireless just throws to many questions out there, and if you do believe that the router is your issue, then change it is all that can be recommended. 

[Shakeel_]

Yeah, one device could be the problem...

[Shakeel_]

I have another router which is not from EE, should I try to connect that with my open reach socket?