[KETHERCORTEX]

Simplest way to do this: good speed on Speedtest, rubbish everywhere else.

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.

[verdverm]

I've been using the Google widget when you search "speedtest"

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...

[KETHERCORTEX]

> I've been using the Google widget when you search "speedtest"

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.

[1] https://openconnect.netflix.com/

[verdverm]

The other node is in another country that does not have the same ISP. Again, it seemed accurate, so not sure why your even bringing it up. We could watch it change as we turned on and off the Amazon stream. That's how we figured out that it was this one service, not the ISP or Internet at large

Amazon says how many gigs per hour it uses for different qualities, none went over 2 digits in an hour, so there should have been sufficient bandwidth.