Hi Sam, As you may have noticed, Netflix no longer uses Cogent as a transit provider. You will see all of your transit traffic from us traverse Level3. We are happy to try to work with you to find the best way to deliver your traffic. Please reach out to peering@netflix.com and the team will try to help. Regards, -Dave On Sun, Dec 4, 2016 at 9:14 AM, Sam Norris <Sam@sandiegobroadband.com> wrote:
Hey all,
In early October our traffic levels from NetFlix went from about half Level3 and half Cogent - pretty well balanced - to all on Level3. Standard multihomed BGP setup with minimal TE if I can help it. I am starting to run into problems with a full gigabit port on Level3 and only 100-200mbps on Cogent at that colo. I tried padding, I even tried 65000:2906 bgp community, but it seems like if our level3 port is up NetFlix chooses it solely. How can I load balance NetFlix traffic across my two ports so that I am not paying for overages and/or forced to up to a 10G port immediately? I have 3 other providers at that colo and cannot find any mix of bgp tricks to get some of it thru our other providers.
I notice AS2906 has a localpref of 86 - odd ...
The 108.175.47.0/24 block seems to be using as 2906 so I thought a 65000:2906 wouldn't announce those prefixes to them at all. I have about 10 prefixes being announced so I could implement a no-export on some of them to load balance but that doesn't work.
Thx,
Sam
BGP routing table entry for 108.175.47.0/24
Paths: (2 available, best #1)
2906
AS-path translation: { 108.175.47.0/24 }
ear3.LosAngeles1 (metric 100000)
Origin IGP, metric 30334, localpref 86, valid, internal, best
Community: 2906:51081 North_America Lclprf_86 United_States Level3_Peer Los_Angeles Level3:10984
Originator: ear3.LosAngeles1
2906
AS-path translation: { 108.175.47.0/24 }
ear3.LosAngeles1 (metric 100000)
Origin IGP, metric 30334, localpref 86, valid, internal
Community: 2906:51081 North_America Lclprf_86 United_States Level3_Peer Los_Angeles Level3:10984
Originator: ear3.LosAngeles1