BandwithCapping

Latest

  • Netflix lays out official response to bandwidth capping allegations

    by 
    Darren Murph
    Darren Murph
    03.23.2009

    After a small but vocal amount of Netflix users got the world thinking that it was pulling a Comcast and putting caps on computer-based Watch Instantly users, the outfit's Chief Product Officer Neil Hunt has come forward to clear the air. He makes clear that Netflix's aspiration is to "deliver to everyone the best bitrate that their broadband connection can support," also noting that congestion "could affect some users, but not others, at some times, but not always." He also notes that different titles and encodes for different playback device types "may come from different CDNs or different servers at a particular CDN, so they may have different paths and different bottlenecks." We'd encourage you to hit the read link for the full explanation, but we're already seeing enraged Roku users bark back by his dodging of the so-called out-of-sync audio issue that's evidently still present. We'll go ahead and warn you, Netflix -- you can't please 'em all.

  • Is Netflix putting caps on computer-based Watch Instantly users?

    by 
    Tim Stevens
    Tim Stevens
    03.16.2009

    Depending on your choice of computing platform, possession of dedicated streaming hardware, and love of otherwise forgettable '80s films, Netflix's Watch Instantly service is either a godsend or a gimmick. Regardless, nobody likes arbitrary bandwidth caps, and that's what Riyad Kalla at The "Break it Down" Blog claims to have spotted, finding that Watch streams on his Xbox take multiple minutes to buffer, but that those on his PC (using the same connection) can take hours -- if they work at all. Doing a little snooping he found he was being capped to about 50 KB/sec per download thread on his PC, but if he spawned ten such threads he was able to get over 700 KB/sec. Something, it seems, is issuing a per-thread cap, but is it really Netflix? Or, rather, is it his Qwest DSL line doing a ham-fisted job of managing bandwidth? We've seen similar issues intermittently, but nothing consistent, so we're not quite ready to call this an internet-wide conspiracy just yet, but would love to hear about your streaming experiences lately. Update: Based on the volume of "It's working just fine for me" comments both here and elsewhere it seems safe to say that if there is a conspiracy at work here, it's not Netflix's. [Via Slashdot]