BeerHunter

For any other Fortnite R2 Gamers The best way (IMHO) to use the Geo-Filter for Fortnite is to 1. Set your required GF radius (Be realistic anything under 50ms is perfectly fine) 2. Have DumaOS open on a device next to you as you search for a game in Fortnite. 3. When Fortnite says its preparing to move to Server / Lobby, look at the DumaOS it will now show you (white icon) what server your going to 4. You then have a about 3-7 seconds to cancel the search before Fortnite moves you to that lobby 5. Restart search (Xbox Press B then Y), it's not ideal but it's so much smoother than the DING Beacon service error, DING Beason Service error loop

Just for info, if you are playing on XBOX and get this issue in the future, it's not a router issue, the XBOX quick resume for Fortnite doesn't work in a lot of scenarios, so will just hang on that screen. The fix is easy, 1. Press the X (middle) button on the controller. 2. The Game/ App side menu appears with Fortnite at the top, goto the fortnite (game icon) 3. Press the menu button (3 lines) and select Quit 4. Start Fortnite again 5 Game should load perfectly fine now

Hey Morph, I feel your pain, I almost had the exact same issue as you on my XBOX X playing Fortnite I'm using the R2 over Wifi, only the XBOX is connected to the R2 Good Internet bandwidth 1000mb d/l etc Using the R2 via a TP-Link Router (Deco M4) - Zero LAG spikes on the TP-Link, constant spikes via the R2 Play Fortnite on the R2, intermittent Lag spikes make the game absolutely unplayable I play from the UK but more often than not land on German servers (25ms -35ms) I get lag spikes on the London server with 9ms latency, i get spike lags on any server, no matter the latency, switch to the TP-Link lag spikes disappear, switch back to the R2 and like a bad smell the Lag spikes come back! Frustrating as hell. Tried everything you did, but nothing worked until this... My steps from TP-Link (deco M4) to R2 1. Factory reset the R2 and start with a clean install 2. Upgrade to the latest R2 firmware. 3. On my TP-Link router, I reserved the address of the connected R2 router (this assigns internal static IP address) 4. In the TP-Link I have assigned the R2 as High priority (locate client in the TP-Link UI, should be a toggle for High Priority) 4. GOTO to the Advanced -> NAT Forwarding -> Port Forwarding section on your TP-Link and forward the following ports for the R2 Ports required for XBOX Port 88 (UDP) Port 3074 (UDP and TCP) Port 53 (UDP and TCP) Port 80 (TCP) Port 500 (UDP) Port 3544 (UDP) Port 4500 (UDP) If you have the same UI on your TP-Link then its should be something like Service Type = Custom Service Name = Port 88 (UDP) - this is example for port 88 Internal IP - Select the IP of the R2 that you reserved early Internal Port = 88 External Port = 88 Protocol = UDP Repeat for all Ports listed above - Double check at the end that all ports have been correctly forwarded to the correct reserved IP using the stated protocols TCP, UDP or TCP & UDP Restart your devices Xbox / PS5 & R2 (i didn't bother restarting the TP-Link) Hopefully like me, you should now see zero lag spikes on the R2 Best of luck buddy