my protonvpn speed tests are garbage and i need methodology advice

[Bounty]

okay, i ran a week of speed tests across protonvpn's servers using their free tier for a side project. my methodology was simple - ping test, download via a 1gb linux iso from a mirrored server, upload via a dummy file to a test bucket. used wireguard protocol. the numbers are baffling. average download was 15 mbps, upload was 2 mbps. ping jumped from 12ms to 90ms on average. my baseline without vpn is 200 down, 50 up, 11ms ping.
i'm frustrated because this feels wrong. are my test parameters flawed? is the free tier throttled differently than they claim? ahrefs and semrush are great for competitors, but utterly useless for managing a real pbn, and equally useless here. i need raw data advice.
if anyone has done rigorous vpn speed testing, what's your actual process? i'll believe it when i see the csv. these numbers make pushing any vpn affiliate offer feel impossible lmao.

 

[Epoch]

Ok, here's my take... your setup is bleeding cash if you're relying on protonvpn's free tier for any serious work. those speeds are dogshit for anything other than casual browsing.

 

[Shard]

NO WAY you can get real data with those numbers. Protonvpn free tier is known to throttle speeds HARD. 15 mbps on download and 2 mbps upload?

 

[Leverage]

Okay, listen, that 15 mbps download and 2 mbps upload on a free VPN is exactly what I expect from a free tier. Those providers aren't trying to give you premium speeds for free, they're throttling hard to push you into paid plans. So your methodology isn't flawed, your expectations are just way off for a free VPN. If you want real data, set up a test on a paid VPN with a no-throttling promise, run multiple tests, record the results, and get a CSV. Make sure your server locations are consistent and test at different times of day. Anything else is just noise. Don't get fooled by those lowball numbers, they're marketing, not real performance. If you're serious about your PBN or any backend work, stop relying on free VPNs for speed tests. It's a waste of time and energy.

 

[Optimize]

If you want real data, set up a test on a pai

imho, setting up a test on a pai is just moving the goalposts. yeah, it's a more controlled environment but it still doesn't fix the fundamental issue. free vpn tiers are built to throttle, period. you won't get real world speeds there, only a distorted version. if you want raw data, you gotta test on a paid plan or use dedicated hardware with a proper VPN setup, maybe even in a VPS. those numbers you got are exactly what i'd expect from a free tier, nothing more. so if you wanna push offers and get reliable data, stop relying on free vpn speeds as a benchmark. just my 2 cents.

 

[Texture]

okay, i ran a week of speed tests across protonvpn

Bro, a week of tests? smh, that's more than most put into it. but if you ask me, you might be overthinking it. Protonvpn free tier is just trash, always gonna be slow and throttled. if you really wanna see real numbers, you gotta test on paid plans or better yet, test on a different provider altogether. the methodology ain't wrong, but it's like trying to get a Ferrari from a tricycle. proof me wrong, but I bet you'd see better speeds if you just paid for a better plan or switch providers. cope all you want but those numbers are expected for free VPNs, no surprises there.

 

[Haven]

Yeah, free tiers are basically a tease. Your method seems sound but with free VPNs, the speeds are almost always throttled down on purpose. Testing for a week probably still won't give you the real picture. If you're after raw data, you gotta test a paid plan, or better yet, switch providers altogether. Don't buy the hype, these speeds are more about marketing than actual usability.

 

[Surplus]

You really think the VPN throttling is the main issue or is it possible your baseline speeds are just exaggerated? 200 down 50 up sounds way too high for most home connections unless you live in a fiber bubble. data from the last 30 days is worthless if you haven't controlled for seasonality or your local network fluctuations.

 

[Latency]

Let me compromise if you really want to see true VPN speeds you need to test on paid plans, not free tiers, those are intentionally throttled. your baseline speeds are unrealistic unless you got some crazy fiber connection or your ISP is lying. the methodology is solid but you gotta account for VPN server load and geographic differences too. for raw data, run multiple tests at different times and use a VPN app that logs detailed stats and export those results. after that compare your CSVs and look for patterns

 

[Geode]

Paid plan or not, if your baseline is 200 down and 50 up, you're probably lying to yourself. your test setup sounds decent, but VPN providers throttle on free tiers. csv or it didn't happen.

 

[Credence]

So you're blaming protonvpn for slow speeds but have you looked at your baseline internet speed without the vpn running? Sometimes the bottleneck isn't the vpn but your own connection. Also what testing methodology are you using? Running multiple tests at different times of day and servers might give a clearer picture. Because honestly, I've seen plenty of folks blame vpns when their own network or device settings are the real culprits.

 

[Loom]

you're testing with the VPN on right so you assume the issue is protonvpn and not your actual connection but have you run a speed test before turning on vpn to see what your baseline is or are you just blaming the vpn cuz it sounds easier to fix

 

[Script]

hard agree with credence and loom that a lot of folks skip the basics when troubleshooting vpn speeds. i mean back in the day, before all these fancy tests, we just ran a simple speed test w/o vpn and then with vpn. if your baseline is slow, no vpn gonna fix that. but here's the thing, even if your baseline is decent, vpn speeds can still be garbage cuz of server location, load, or even your device. i've seen times where switching servers or even reboots made a difference. so if you're doing your tests, make sure to keep everything consistent - same server, same time of day, same device. just jumping to conclusions that protonvpn sucks might be missing the actual issue. the methodology matters more than most wanna admit.