Earlier quoted context omitted.
Most boxes like "Open Connect" pay to be colocated and connected that way. Netflix insists on free installation.
Not true. Big CDNs have been cutting deals like this for a long time. It's often in a network owner's financial interest to host a node for free, because it saves them so much upstream bandwidth which they would otherwise pay for.
Comcast and Netflix now have a direct adjacency
31–40 of 69 posts
Re: Comcast and Netflix now have a direct adjacency
#32Earlier quoted context omitted.
I don't think so. It's multiple direct 10GE ports. Given the traffic volume the two networks exchange, there's no way it would be economical to move these bits over a public peering exchange (which Comcast doesn't participate in in the first place). Even so, if it were in fact going via the IX, you'd see Netflix's IP from the exchange (206.223.116.133) as hop 8 in the traceroute.
Am I understanding this right? If I am an ISP, I can request a Netflix appliance and serve customer requests for netflix content from this appliance directly?
Re: Comcast and Netflix now have a direct adjacency
#33It's anti-climactic that all it was going to take was a compelling business case. Netflix made it easy with their peering initiative [1]. Now Comcast gets to count these bytes against their customers' quotas, and it costs them nearly nothing to deliver the traffic. This reminds me of NNTP, but Netflix is still running their own hardware. [1] Netflix's "Open Connect" https://signup.netflix.com/openconnect/guidelines
Strategically, Netflix was holding a far weaker hand because the ISPs had no reason to give in since their brand perception was already so bad. I mean really, is it possible to hate Comcast more than most people already do?
Re: Comcast and Netflix now have a direct adjacency
#34Earlier quoted context omitted.
I've done this before for large scraping projects. I find the datacenter the target website is hosted in, then get a dedicated server right next to it. I've never gotten better performance.
Putting aside legal issues, you don't have any moral problems doing volumes of scraping content that is not yours?
Re: Comcast and Netflix now have a direct adjacency
#35Re: Comcast and Netflix now have a direct adjacency
#36It's anti-climactic that all it was going to take was a compelling business case. Netflix made it easy with their peering initiative [1]. Now Comcast gets to count these bytes against their customers' quotas, and it costs them nearly nothing to deliver the traffic. This reminds me of NNTP, but Netflix is still running their own hardware. [1] Netflix's "Open Connect" https://signup.netflix.com/openconnect/guidelines
Re: Comcast and Netflix now have a direct adjacency
#37Earlier quoted context omitted.
Most boxes like "Open Connect" pay to be colocated and connected that way. Netflix insists on free installation.
Yeah, it's a value proposition. The argument ISPs keep using is that Netflix traffic is costing them too much. I don't think Netflix should have to engineer a solution to that problem AND pay the ISP for the privilege of saving them tons of money. If the costs (4U of rack space, networking equipment, and network engineering around privacy/security) are more than the ISP would save, it's an easy decision. Note that in…
Also it's largely semantics where a device like OpenConnect is hosted. Netflix could host it at a datacenter across town with a direct fiber interconnect to the ISP and it would be effectively the same thing. This is how all the big CDNs do it; that way they host equipment once and connect to multiple local ISPs.
Re: Comcast and Netflix now have a direct adjacency
#38Earlier quoted context omitted.
I've done this before for large scraping projects. I find the datacenter the target website is hosted in, then get a dedicated server right next to it. I've never gotten better performance.
Putting aside legal issues, you don't have any moral problems doing volumes of scraping content that is not yours?
(Don't downvote him, it's a valid question)
Re: Comcast and Netflix now have a direct adjacency
#39Earlier quoted context omitted.
Can you tell me why Netflix is so terrible on Uverse 20Meg in San Jose? Blurry mess. Speedtest is always 13Meg+
Its the same reason Comcast was so bad, except you have ATT. Different companies, same problem. Switch to Sonic or something and that problem will go away.
Re: Comcast and Netflix now have a direct adjacency
#40Earlier quoted context omitted.
I've done this before for large scraping projects. I find the datacenter the target website is hosted in, then get a dedicated server right next to it. I've never gotten better performance.
How large of a scraping project are we talking about in terms of throughput?
I offered to help them set up an API instead of scraping, but they decided scraping was easier in the short term.