edit: strange to post this and find a second post with exactly the same two points submitted while writing. I guess my thoughts aren't that special
Hell, during the height of this Comcast partnered with Speedtest, and now hav their own Speedtest servers all over the country, so you don't even leave Comcast's network.
Most ISP's do, and if you tell it to use the server of some other provider off-net they'll happily make the excuse that "we can only guarantee bandwidth to the edge of our network."
It's a crap excuse, because, duh, you have no control over the path traffic takes once it leaves your AS on hopefully the best route - but if you have poor connectivity to your peers that's still on you.
It’s problematic if they don’t, because if Comcast detects a virgin running a speed test, they can throttle virgin traffic to give lies as results. So virgin need to run their own nodes.
If you kill net neutrality, that behaviour is legal.
Also, by default Speedtest tests the connection from you to the nearest testing node. A lot of times it's the one hosted by your ISP, so the measured speed is the speed inside the ISP's local network and not the speed from you to outer Internet.
It tests using a node 200+ miles away (they tell you where) AND it actually shows slow numbers when the pipe is slow. Turns out Amazon Video was the culprit, somehow using 80% of a 100Mb connection for a single stream...
Google doesn't show me this widget, but the speed test on Google Fiber's website is just a frontend for Ookla's Speedtest I mentioned. So I suspect that the widget does the same or similar stuff. I don't know for sure though.
> It tests using a node 200+ miles away (they tell you where)
"200+ miles away" from your physical location doesn't mean "outer internet outside your ISP". It doesn't mean "far away from your ISP's network" either.
For example, some mobile carriers may operate country-wide, but route everything through Important Central Connector To Outer Internet™ in the capital city. Consequently, internet services think that user's phone is in capital city.
So while you see "City 200 miles away" as a test node, it may actually be the closest one because your ISP's network structure adds these mandatory 200 miles. ISP's internet access node and speed test node may be literally across the street or in adjacent server racks.
Not saying that it is certainly the case, just trying to explain why words on test screen may mean things different from the ones we assume.
> AND it actually shows slow numbers when the pipe is slow. Turns out Amazon Video was the culprit
From your words, it didn't show you slow pipe. It showed you regular one that was busy with streaming video.
Also, ability to watch streaming doesn't necessary indicates actual internet speed since streaming services like Netflix can provide ISPs with the hardware for caching [1] and streaming from inner ISP network. Not sure if Amazon does that though.
> Amazon Video was the culprit, somehow using 80% of a 100Mb connection for a single stream...
Amazon streams with a higher bitrate than most of the competitors. 80 Mbps isn't that surprising given that Bluray disks have 40 Mbps bitrate for 1080p video. With streaming you also preload some video ahead in a buffer, so hitting 80 Mbps is completely normal.
It does feel a bit deceptive, I grant. But to me, lying would be if they tricked speedtest into display 10mbit when only 2mbit of traffic was transferred.
Everyone games the tests. That’s why you can’t trust just about any performance test unless you run it for your workload.
