Comcast and Netflix now have a direct adjacency

gistfile1.md

Comcast and Netflix now have a direct adjacency

Looked at the host serving my Netflix streams today and noticed something new.

No clue if money is changing hands or not, and the return path is what actually matters, but it appears that Comcast and Netflix have reached some sort of agreement regarding direct interconnection.

$ traceroute -a 198.45.63.164
traceroute to 198.45.63.164 (198.45.63.164), 64 hops max, 52 byte packets
    (hops 1-2 redacted)
 3  [AS33651] 76.21.8.1 (76.21.8.1)  11.174 ms  14.215 ms  20.283 ms
 4  [AS33287] te-7-2-ur01.sffolsom.ca.sfba.comcast.net (68.85.103.21)  10.612 ms  12.468 ms  9.935 ms
 5  [AS33651] te-1-14-0-6-ar01.sfsutro.ca.sfba.comcast.net (68.86.143.50)  10.932 ms  14.374 ms  16.179 ms
 6  [AS7922] he-3-8-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.94.85)  24.146 ms  14.741 ms  15.096 ms
 7  [AS7922] he-0-11-0-0-pe03.11greatoaks.ca.ibone.comcast.net (68.86.85.238)  16.531 ms  16.816 ms  15.605 ms
 8  [AS7922] 173.167.57.102 (173.167.57.102)  12.722 ms  12.348 ms  13.481 ms
 9  [AS2906] ipv4_1.lagg0.c070.sjc002.ix.nflxvideo.net (198.45.63.164)  15.250 ms  17.128 ms  13.105 ms

Now how about Amazon? :)

No.

They save bandwidth costs that would be used anyways (unless the fully killed the ability to stream).

@damm Pretty sure AWS already does (and I think that's recent, too). Ignore the AS800 reference; it's a red herring.

 7  ec2-50-112-0-186.us-west-2.compute.amazonaws.com (50.112.0.186) [AS16509]  0.609 ms  0.603 ms  0.739 ms
 8  205.251.230.124 (205.251.230.124) [AS16509]  21.571 ms  21.588 ms  21.598 ms
 9  205.251.232.150 (205.251.232.150) [AS16509]  1.349 ms  1.354 ms  0.876 ms
10  205.251.232.91 (205.251.232.91) [AS16509]  15.967 ms  16.223 ms  22.263 ms
11  205.251.226.188 (205.251.226.188) [AS800]  13.640 ms  13.655 ms  13.642 ms
12  50.242.148.89 (50.242.148.89) [AS7922]  16.370 ms  16.389 ms  16.530 ms
13  68.86.85.198 (68.86.85.198) [AS7922]  36.321 ms  36.305 ms  37.042 ms
14  he-0-6-0-0-ar01.sfsutro.ca.sfba.comcast.net (68.86.90.158) [AS7922]  38.487 ms  36.345 ms  36.334 ms
15  te-8-4-ur01.sffolsom.ca.sfba.comcast.net (68.85.154.61) [AS33668]  35.190 ms  35.364 ms  35.377 ms
16  te-6-0-acr01.sffolsom.ca.sfba.comcast.net (68.85.103.18) [AS33287]  37.242 ms  37.254 ms  37.556 ms
17  c-76-21-10-87.hsd1.ca.comcast.net (76.21.10.87) [AS33651]  50.592 ms  50.600 ms  48.405 ms

As far as I know, the same is true for CloudFront, and Amazon Instant Video is still all hosted off of third-party CDNs. As long as you're using Comcast's DNS servers, not third-party ones, you should get served off of CDN nodes inside of Comcast's network.

Isn't it possible that the traffic could just be going over an MPLS backbone? If that's the case, then there could potentially be more hops that aren't seen.

It looks like this is part of Netflix's open connect project. The open connect project is a self rolled CDN by netflix. As part of this project Netflix has deployed server servers in the hundreds of terabytes size in strategic location around the would. These servers contain between 60-90% of the data that would be used for a particular country. These devices either live in the ISP like a rack at Comcast or live in a internet exchange where multiple ISPs can connect to the same switch as the Open Connect deceives.

This is beneficial in 3 ways:

1. There are less hops to the client allowing for a better stream
2. Peering is usually free and Netflix does not have to pay aws for bandwidth
3. Because the devices are inside the ISP network Netflix is less likely to be rate limited.

http://blog.netflix.com/2012/06/announcing-netflix-open-connect-network.html

There is no evidence that it's using OpenConnect Caching. It could simply be a better peering connection.

AWS offers direct connections as part of their product line and Netflix just moved there
see: https://aws.amazon.com/solutions/case-studies/netflix/