News for hackers. Stuff that matters.

A comment on Netflix is on Fire. Parent comment

Re:Netflix is on Fire by scurvy on Sunday January 03, 2016 @05:53PM (#10832971)
It could also be congestion at the peering points your ISP uses to connect (directly or through transit) to Amazon or HBO.

I think Netflix also still uses caching boxes in a few locations, but they are being phased out.

In other words, there are a lot more variables in the equation than just your home network and the Roku app.

[ Parent | on HN ]
Re:Netflix is on Fire by toomuchtodo on Monday January 04, 2016 @02:16AM (#10834400)
> I think Netflix also still uses caching boxes in a few locations, but they are being phased out.

Proof? I don't see any indication at https://openconnect.netflix.com/ that their appliance is being phased out.

[ Parent | on HN ]
Re:Netflix is on Fire by scurvy on Monday January 04, 2016 @01:18PM (#10837306)
I think Dave Temkin mentioned this at a NANOG or two. Or maybe it was at the bar. I'm not sure. I could be completely wrong. That's why I typed "think"
[ Parent | on HN ]