Netduma Fraser

I have let the team know and they should push an update tomorrow

Did you follow all the steps again, if you're already on the game then it likely wouldn't detect. We recommend it because the specific services can get out of date which is what I thought could possibly have happened here.

Did you do step 3 & 5 from my steps? As it should be added with the Games Console service instead of Fortnite which should then work

Resync the cloud, then re-ping the game does it appear then?

We haven't changed anything on our end, try this: Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager (if on PC) Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter with the manual option Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client Then see if it works. Also, if you're not aware, the way that Fortnite matchmaking works is that it will only try to connect to a server when it's loading into the pre-game run around lobby so the fastest way to filter would actually be to disable Filtering Mode but use it to see where the game puts you - if it is too far away or the ping is too high then quit and re-search - this will be faster than waiting for it to kick you.

Thanks for the information, we'll update the ticket with this and hopefully we can get to the bottom of it.

Thanks for the report, we'll take a look!

Thanks for the feedback, we'll add it to the list to be potentially added in future!

Ah yes looks like you rebooted after. If you're able to get it connected again and can get a log when it disconnects that would be really helpful

Thanks for that, around what time did it occur? Then we can try to match it up with the log

That should be fine thanks, also do you see anything in the logs on the VPN page?

No that is controlled by the service, e.g. Netflix, you would just need to find a VPN that hasn't been blocked by the affected services.

They can support it but they can't prevent services blocking their known VPN IP addresses, some providers offer a free trial in which case you could try it to see if that is the problem with no monetary obligation.

Have you tried another provider just in case the services you want block the VPN you're currently using?

Given the PingPlotter results you've provided and that the Ping Test Under Load doesn't show packet loss either then I don't think you are actually getting packet loss and more likely something we would have to look into as to why it is showing that happening. It's always showing right at the end so it could be the test is dropping off to finish and interpreting that as packet loss for example.

That could be why then as 8.8.8.8 is used by Benchmark by default unless it is unavailable and then it would switch to 8.8.4.4, as a test if you switch the DNS to 8.8.8.8 then redo Benchmark does the packet loss go away?

Thank you very much, I see it's forcing you onto 8.8.4.4 rather than 8.8.8.8, could you try that please and provide a screenshot?

Could you provide a full page screenshot of PingPlotter please?

Great, let us know how you get on!

How did you do the factory reset initially? Hold the reset button for 30 seconds, then wait 2 minutes before accessing the interface

I think you may need to do a reboot, then retry or if that doesn't work, a factory reset and then try again. I believe it's got itself into a weird state and can't tell when you've entered VPN details.

Is it still saying no VPN configured when you try to connect?

Could you try with a different server/config (adjust the config to match the template) and try again please?

A latest internal firmware passed at 90% with two important issues being flagged that we're currently working on resolving so it depends how long that takes really, shouldn't be too long and then it should pass at 100% and we can proceed with a release. 450 should follow very closely after the 500.

Are you seeing it every time you run the test? I'd suggest using PingPlotter and see if you see the same packet loss when pinging a more local site