Overall Netflix bandwidth usage numbers on a network?

I guess most (i.e. those
which aren't Akamai) are more concerned with making money than with delivering
a good service to the end user.

Really? I always thought that higher profits and buying transit were mutually exclusive relative to higher profits and openly peering.

So what you are saying is that one stands to make more by paying upstreams for bit swapping? How's that work?

You are assuming that peering with $ISP will lower someone's transit bill. That is demonstrably false in the case of Level 3 who (to a first approximation - please do not argue corner cases) pays no one for transit.

It is also likely false over some set of $ISP_n for some peers. As a trivial example, if $NETWORK peers with your transit, not only would it not save them money to peer with you, it may cost them money if peering with you endangers the peering with your upstream. This can happen if $NETWORK does not have enough traffic to qualify for peering with your upstream when your traffic is removed from the link.

So peering does not always equal profit. Would that life were so simple! =)

If the argument is that the opex required for maintaining peering relationships is too expensive relative to the direct and indirect cost of buying bandwidth, I love to be edumacated on how that math actually works because it makes absolutely no sense to me.

Peering is not free. I can easily see the cost of bringing up a port to someone with 10 Mbps costing more than it saves for some perfectly valid network topologies. And that's just the most obvious example. The one above is another obvious example.

There are reasons not to peer. Assuming there are not is a bad way to enter a negotiation. Put yourself in the place of the other network, figure out what their pain points are - performance, complexity, stability, cost, slot density, spare cycles (human and machine), etc., etc. To be successful in a negotiation, I submit it is useful to help them eliminate one or more of those pain points, i.e. make it worth their while.

Remember, my company's peering policy (at public exchanges) is "YES". Since I wrote the policy, you can probably guess my view on peering. But if simply I assumed no one ever had a reason to say "no", I wouldn't get very far.

There are two sides to every story. Sometimes the other side is confused, or even flat out wrong, but not always. And even when the other side is wrong, it may not be useful to bash them over the head with the truth.

I'm somewhat assuming you're trolling here. :confused:

but just in case...

the lost revenue from peering with someone when you could be
charging them transit prices is the tradeoff being referred to
here; Level3 isn't in the business of paying upstreams for
bandwidth. (well, other than comcast, but that's a different
thread entirely. And yes, I suppose that would be me trolling.
Bad Matt!)


Requests to this address appear to go unanswered?

Dave Temkin wrote the following on 12/11/2011 6:29 PM:

Same here.

I'll take a guess they are back logged - they have been working on our traffic stats since a week before that posting made it to nanog list

--- Sent via IPhone

Yeah, that's an interesting one. We currently utilize netflow for this,

but you also need to consider that netflix streaming is just port 80

www traffic. Because netflix uses CDNs, its difficult to pin down the

traffic to specific hosts in the CDN and say that this traffic was

netflix, while this traffic was the latest windows update (remember

this is often a shared hosting platform). We've done our own testing

and have come to a good solution which uses a combination of nbar,

packet marking, and netflow to come to a conclusion. On a ~160Mbps

link, netflix peaks out between 30-50Mbps around 8-10PM each evening.

The rest of the traffic is predominantly other forms of HTTP traffic

(including other video streaming services).

We (Sandvine) also have a product that does this measurement in the

IP network, per CDN, per device type (e.g. how much Netflix on xbox

is on Akamai vs Limelight). In addition it measures the delivered

quality per CDN.

Anyone can feel free to contact me off list for more information.


Yes, sorry. We will respond to all takers shortly; there was a flaw in our logic used to generate these numbers and wanted to ensure that we were painting an accurate picture. We will have statistics out within a week, hopefully.