News for hackers. Stuff that matters.
Re:Building fast.com by twinkletwinkle on Tuesday August 09, 2016 @02:27PM (#12256723)
I think the point was they conduct the speed test from the same servers that deliver video content. So ISPs can't throttle video streaming without it showing up in this speed test.
Re:Building fast.com by greenspot on Tuesday August 09, 2016 @02:33PM (#12256781)
Makes sense but wouldn't they then use the netflix domain? Something like netflix.com/fast? I could image that if providers throttle it would be a mix of IPs and domain.
Re:Building fast.com by dpark on Tuesday August 09, 2016 @02:51PM (#12256909)
If you look at the actual traffic, it's hitting netflix's content servers. e.g. ipv6_1-lagg0-c001.2.bne001.waia.isp.nflxvideo.net

The interesting traffic is not to fast.com.

Re:Building fast.com by voxic11 on Tuesday August 09, 2016 @03:51PM (#12257283)
If you look they aren't using fast.com as the domain they are downloading files from. That's just the domain that hosts the page. It doesn't matter if it gets throttled because it only serves up a few kb of html.
Re:Building fast.com by chrishacken on Tuesday August 09, 2016 @02:49PM (#12256893)
Some ISP's (we don't throttle anything) throttle based on several factors, mainly packet signatures. Traffic coming from big/known sources, such as Netflix, contain unique signatures (probably the headers, etc, that are unique to Netflix Traffic). You can then check all incoming packets that match those signatures and throttle them. So unless Netflix went out of their way to mask every request to look like video content, there's not a whole lot you could do.
Re:Building fast.com by IceyEC on Tuesday August 09, 2016 @03:29PM (#12257147)
The files that fast.com has you download ARE chunks of video files :)
Re:Building fast.com by zeristor on Wednesday August 10, 2016 @02:28AM (#12259862)
Does anyone know which video the test file is?

Perhaps it's encrypted, or a Netflix promo piece.

Wouldn't there be copyright issues to use their actual streaming licences content?

Re:Building fast.com by corobo on Wednesday August 10, 2016 @06:18AM (#12260608)
If you have a Netflix subscription it's probably this or something like this [1]. For non-flixers it's a calibration video similar to [2]

[1] https://www.netflix.com/watch/80103278

[2] https://www.youtube.com/watch?v=cGgf_dbDMsw

Re:Building fast.com by niftich on Wednesday August 10, 2016 @02:36AM (#12259888)
Earlier I got curious and I was wondering this too. Seems to be a 'random' blob of bytes every time that doesn't decode, but then I remembered they serve DRM'ed video that is then decrypted on the client.
Re:Building fast.com by WatchDog on Wednesday August 10, 2016 @01:52AM (#12259748)
The connection is encrypted, the ISP can't see request headers. For the main data download, all they can determine is its an TLS connection to a netflix content server. Potentially you could do some stateful monitoring looking for recent requests to fast.com but it's generally much harder to implement than simple IP or SNI based profiling.
Re:Building fast.com by stouset on Friday August 19, 2016 @01:50PM (#12321913)
All of the traffic is HTTPS. The ISP doesn't get to see headers.
Re:Building fast.com by jsnell on Tuesday August 09, 2016 @02:39PM (#12256817)
If it's intentional throttling, fast.com would actually not be much of a problem. It'd still be easy to selectively apply traffic shaping to streaming but not to the speedtest traffic.

It would be harder (though not impossible) if there is an actual capacity problem, and the bottleneck is outside of the ISP's network. For example insufficient peering capacity, which seems to be where most of the Netflix / ISP friction is.

Re:Building fast.com by kbenson on Tuesday August 09, 2016 @03:06PM (#12257007)
> It'd still be easy to selectively apply traffic shaping to streaming but not to the speedtest traffic.

That presumes they aren't fully emulating streaming traffic to test speed. Not only is this the correct thing to do from a video streaming company that wants to test connection speed for their services (the quantity and size of packets can affect the delivery through different mediums and devices), but it also makes it obvious when your ISP is quietly throttling your video streaming traffic.

Since it's a win-win in this respect, I would be surprised if this isn't exactly what they are doing.

Re:Building fast.com by jsnell on Tuesday August 09, 2016 @03:20PM (#12257096)
> That presumes they aren't fully emulating streaming traffic to test speed.

It's not really a presumption, it's the actual facts on the ground. The actual benchmark file is served over HTTPS from, but there are still multiple simple ways to distinguish the current speedtest testcase from normal streaming.

Re:Building fast.com by kbenson on Tuesday August 09, 2016 @03:51PM (#12257284)
> The actual benchmark file is served over HTTPS from, but there are still multiple simple ways to distinguish the current speedtest testcase from normal streaming.

Do you mind explaining the details you are aware of that lead you to think they are not emulating streaming traffic in at least some portion of their test (since they are testing multiple sessions and types of traffic)? I may have missed a portion of this article or some other source that outlined this.

It would fairly trivial to send sample content of actual video content for the test, and emulate a streaming client on the tester side, so I'm not sure how an ISP would distinguish traffic in that situation.

Re:Building fast.com by jsnell on Tuesday August 09, 2016 @04:26PM (#12257452)
Sure. One example is that someone doing a speedtest will have accessed fast.com before starting a download of video streams. This can be detected despite the the encryption, e.g. via looking at the SNI of the requests. It doesn't matter what the video stream looks like, since those separate TCP flows can be cross-correlated.
Re:Building fast.com by kbenson on Tuesday August 09, 2016 @04:50PM (#12257619)
So in that case Netflix just decides to have their streaming clients occasionally access fast.com before regular streaming to get any traffic shaping eased?

I agree, that in this case, where a separate domain was used, ISPs can use that to detect a speed test is likely. That said, I would like to note that every solution an ISP has to implement is much more expensive to any mitigation put forth by Netflix, as long as they want to hide what they are doing. If they aren't hiding it, well that's one of the reasons netflix is doing this, to inform customers what they are actually getting from their ISP, and let them make choice whether they like the current product they are using from their ISP (if they have a credible choice).

Re:Building fast.com by brazzledazzle on Tuesday August 09, 2016 @06:02PM (#12258035)
Netflix could load something from fast.com on each Netflix navigation right?

Ultimately if they're playing cat to Netflix's mouse how much does each mitigation strategy cost them relative to Netflix? I wonder if it's more cost effective to process that much traffic through shapers than it is to increase bandwidth between peers or allow Netflix to drop their boxes within their networks.

Re:Building fast.com by jonknee on Tuesday August 09, 2016 @04:42PM (#12257569)
The same functionality can surely be built into Netflix apps.
Re:Building fast.com by davb on Tuesday August 09, 2016 @04:40PM (#12257558)
> but there are still multiple simple ways to distinguish the current speedtest testcase

Like looking out for DNS queries for fast.com then handling traffic from that client differently for a period (such as the A record's TTL).