I only looked back at 40 tests, that was the only time where it was 1.7%, otherwise 0% or maybe 0.54%.
A packet loss of up to 1% is considered normal. Maybe the 1.7% had their microwave or something else disturbing turned on by chance.
But no matter how it doesn't explain the slowing down throughout the day.
Just tested again to clarify.
Package loss >0 isn't normal, sorry to say that.
Zero is the normal.
What is your Starlink plan?
I'm not understanding these screenshots. You are reaching 420Mbps (download) and 10Mbps (Upload). What are you expecting?
test via ethernet and you won't get packet loss
wish i had another flint 2 to test this!
Quite normal standard offer. 50 euros per month unlimited.
What I expect??? The router becomes slower and slower throughout the day until in the end it only has maybe 10 Mbit and has to be restarted.
Strangely enough, only the Flint 2 has this. I don't have this with an alternative router
I didn't read the whole conversation. But only to be clear: Did you only test via WiFi?
Are you sure its not the WiFi connection what is getting slower? What are your WiFi settings? (80MHZ or 160MhZ? Which channel? I'm asking because I had a strange phenomenon yesterday with my Flint 2 where WiFi was super slow but wired had the normal speed. Only a reboot helped.
Yes, apart from 2 devices (repeaters) in the household, everything runs via WiFi.
80MHZ
Yes, I'm sure because no matter whether it's a PC, cell phone or FireTV stick, the speed goes down everywhere
Can you run a speedtest on the Flint 2 via SSH while it's slowed down?
For example with:
wget -O /dev/null http://speedtest.wdc01.softlayer.com/downloads/test500.zip
or
wget -O /dev/null http://ams-speedtest-1.tele2.net/1GB.zip
Or even better with iperf3 (needs to be added as a package)
Best way, imho, is using a real speedtest:
wget https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-aarch64.tgz && tar xzf ookla-speedtest-1.2.0-linux-aarch64.tgz && ./speedtest
If you take the VPN out of the question, is the speed normal then?
Ive just been thinking about this issue.
Does the packet loss maybe only happen on a longer time of a constant connection?
Do you think this can be replicated with a ping?
Ping can be super usefull, if the ms keeps stable its ok, now remember it is wireless so it is fine that it can fluctate but not into a extreme.
What you can do is first use a tracert/traceroute and then first start pinging the first local ip you see for some longer time (on windows it is ping -t usedirectip) and then follow up the list.
The tracert can help to map a full route to the internet so you will hit all gateways on your local network (you can here also diagnose if there was a local issue even with multiple routers behind), and also infra gateways by starlink and up on the list 
If one device shows rather stable output in ms, but once of the sudden goes 1000, there is your point of interest.
It can be a hardware issue with the starlink modem, because i very well remember my first days diagnosing a coax modem with those intel puma chipsets you can google about this, i went to a other isp once they didn't want to give a different one😁
the ip was after my modem, but when i asked the internet person about it he told me it were 2 gateways in one device, so not some type of service cabine by them, and that chip can overheat and caused packet loss when there is too much packets ...
And now connect to your StarLink router directly and test again.
It is currently in bypass mode so everything needs to be reset
Well, it will be required for troubleshooting.
You (and we) need to understand where the issue occurs.
So the main question is: Is the StarLink network slow or only the router.
Please do all tests without VPN. VPN adds a layer of complexity which is not useful.
We still see some loss, which isn't normal.
Yup bypass mode or bridge still can cause issues if the device doesn't work properly you can see what ive written about the puma chipsets im not sure if it is a similar case but its good to diagnose it.
but like @admon has said vpn only cause more complexity because it uses a constant connection.
The funny thing is that there are no problems with the Asus ax86U and there are with the Flint 2. I'll see if I can do it later
