[thayne]

When I used a major cable ISP, often my connection seemed slow, so I'd go to speedtest.com. The speedtest would be fine... and then I would magically have faster network performance again.

It happened enough times that I'm suspicious the ISP had some way to detect if you run a speedtest, and then prioritized traffic to that customer.

[simmonmt]

This was one of the reasons given, at the time, for why Netflix created fast.com. It's served by the same infra that does their streaming, and is thus difficult for isps to game. That is, it'd be hard for them to do some hack to make fast.com numbers without also benefiting Netflix streaming performance in the bargain.

[dmurray]

Actually I thought Netflix had already acquired Ookla / speedtest.com, so I was surprised to see this headline. But it looks like this was just the Mandela effect.

That said, why didn't Netflix acquire the market leader in this space? Creating their own seems way less useful, since network effects are the whole point.

[fragmede]

Because Netflix doesn't care what your connection to speedtest.net is, they care what your connection to your closest Netflix server box is. A while back, Comcast/your last-mile ISP was throttling traffic to Netflix to get Netflix to pay them. So while Netflix's box had plenty of bandwidth to their ISP, your ISP wasn't using it, intentionally. Fast.com was their response to that, so you could blame your ISP and not Netflix for being slow.

[eddythompson80]

That’s a really over simplification of the issue. Plenty of Netflix edge CDNs are (and always were) ISP hosted. It’s a win-win for both and a complete no-brainer. The ISP v. Netflix argument was always about contract and margin negotiations. Flat rate, usage percentages, minimums, maximums, special plans, cuts, etc. who has the upper hand in the negotiation so to speak. Funnily enough the repeal of net neutrality gave those smaller ISPs much better position in the negotiation with big tech, not necessarily Comcast. The internet discord focused on Comcast and Verizon because fuck those guys. Who is gonna argue in favor of Comcast or Verizon? But the real winners were thousands of smaller regional ISPs.

[acdha]

The internet discourse focused on the big ISPs which refused to deploy CDN nodes and then said they needed to double-charge for peering capacity. Most smaller ISPs deployed those Open Connect nodes either becsuse they weren’t as greedy or felt that their customers had alternatives.

[dmurray]

I meant, acquire the speedtest.net domain and point it to servers inside Netflix' farm.

[mcintyre1994]

Based on Accenture acquiring them, I’d guess the actual business wasn’t really interesting to Netflix. And that leaves the infrastructure, where the value they get is it being Netflix infrastructure. I can see why they spent the money on a really good brandable domain instead.

[eddythompson80]

> It happened enough times that I'm suspicious the ISP had some way to detect if you run a speedtest, and then prioritized traffic to that customer.

ISPs definitely know when you run a speedtest.net test. 90% of the time, the data for that comes from boxes/services they host themselves. It’s not exactly hidden either. It’s a typical program any ISP can sign up for and you can easily see the destination the test is running against. I won’t be surprised if some have some logic to prioritize particular subscribers plan once they have detected a test from them. They probably view it as a “customer support calls reduction” feature.

[Suppafly]

>When I used a major cable ISP, often my connection seemed slow, so I'd go to speedtest.com. The speedtest would be fine... and then I would magically have faster network performance again.

Yeah, I suspect you could script it to do it daily. They definitely seem to deprioritize traffic from people that don't complain.