Netflix streams our content payload via one of three methods:

A) An embedded cache inside of your network, provided you meet certain traffic criteria (generally greater than 5Gbps of traffic).  We call this the "Open Connect Appliance"

B) PNI (SFI) at common private peering locations 

C) Public Peering (SFI) via IXs at common public peering locations

Any of the above options make you automatically enabled for Netflix Open Connect - our next generation content delivery infrastructure that delivers Super HD and 3D content.

Please contact us at peering@netflix.com to help determine the best method to efficiently serve Netflix traffic to your users.  To help us expedite your inquiry, please be sure to provide your AS as well as any downstream ASes (or a IRR record that can be expanded) and the locations that you wish to ingest Netflix content at.  We will contact you as soon as possible.

Note that Netflix does not operate a backbone; you will receive prefixes relevant to the region that you interconnect in only.

***NOTE ON MED SCHEME***

We accept your MEDs within a relevant geographical area (example:  we will not serve UK content from Atlanta), but we automatically add a med of 50 to PNI and 100 to IX in addition to the MED you send us.  We use MEDs BEFORE geolocation - they will always override our geolocation service.

***NOTE ON WEBSITE***

Our website, http://www.netflix.com , is operated from the AWS Cloud in relevant geographical regions.  Simply looking at routes for www.netflix.com is not indicative of whether or not you have connectivity to Open Connect.  The best way to check is to expand AS-NFLX and refer the individual networks contained within there or contact us at peering@netflix.com for assistance.