- cross-posted to:
- linux@lemmy.ml
- floss_replacement@lemmy.ml
- cross-posted to:
- linux@lemmy.ml
- floss_replacement@lemmy.ml
Free and Open Source Speed Test. No Flash, No Java, No Websocket, No Bullshit.
how does that compare to https://openspeedtest.com/ ?
Works well. I host this myself to check up on my data center and how it’s doing routing traffic to consumer isps in the real world.
I host this for my own troubleshooting purposes. It works well enough. The other posters are talking about the Netflix speed test, don’t forget cloudflare has one that also tests latency loaded and unloaded.
This is the only one that gave me accurate speeds when I was experiencing very slow internet
fast.com just gave me a 5gbps speed on a router that maxes out at 1gbps lmao
Edit: most of this comment regarding fast.com is wrong
Fast.com only shows download speeds and likely has no app (which is especially helpful if you want to bypass the VPN).
Librespeed shows ping and jitter as well as up- and download speeds. Also you get a shareable picture/link of your speed test.
Fast.com shows ping, loaded ping and upload speed. It has a mobile app, but I didn’t understand your point about VPNs. You also get a sharable picture if you know how to take a screenshot 😂
You are absolutely right. I didn’t see the “additional infos” button. I edited my original text.
I actually did experience this once.
Fast.com is a separate domain, I don’t think the ISP would have any trouble throttling only Netflix.com without fast.com.
The actual load test is from Netflix’s servers and Netflix’s domains. Open up the network tab in your browser debugging tool when running a speed test on fast.com and you’ll see.
Netflix created fast.com to prove that some ISPs were throttling Netflix and hold them accountable towards their customers.
ISPs don’t see domains. Unless they control your DNS. I assume fast.com uses the same servers as Netflix and would have the same IP address, which would only be resolved to fast.com or Netflix inside Netflix’s servers. I think this is a fair assumption, as that’s the biggest benefit to Netflix. They want to prove your ISP is the problem not Netflix.
Your ISP can see the packets they pass, and your https headers still have the SNI field unencrypted unless you’re on a VPN or the operator has ESNI (old) or ECH (new) configured, but I don’t think these are super prevalent just yet. Having the SNI available means they can still traffic shape your packets if they have the hardware in place.
Most ISPs provide their own router which will (by default) use their own DNS servers. They will use this to enforce site bans amongst other things.
Anecdotal of course but years back I noticed my service got really slow sometimes, but speedtest.net reported decent speeds. After running the test my service would be fine… for a bit… until I ran another speed test which “fixed it” immediately again for a while.
It got so bad that I’d be running a speed test every 45 mins or so, which would literally make Netflix etc work instantly.
So tried just doing an nslookup on the domain out of curiosity, and wouldn’t you know it that worked too!
Confused on why this test says 430 mbps and fast.com says 630 Mbps. Seems like a pretty big difference.
I like my crack cocain foss
But why?