[147645] in North American Network Operators' Group
Re: Overall Netflix bandwidth usage numbers on a network?
daemon@ATHENA.MIT.EDU (Paul Stewart)
Fri Dec 16 09:56:50 2011
In-Reply-To: <13175F96BDC3B34AB1425BAE905B3CE50D4D8C87@ltiserver.lti.local>
From: Paul Stewart <paul@paulstewart.org>
Date: Fri, 16 Dec 2011 09:55:35 -0500
To: Dennis Burgess <dmburgess@linktechs.net>
Cc: "<nanog@nanog.org>" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I'll take a guess they are back logged - they have been working on our traff=
ic stats since a week before that posting made it to nanog list
--- Sent via IPhone
On 2011-12-16, at 9:16 AM, "Dennis Burgess" <dmburgess@linktechs.net> wrote:=
> Same here.
>=20
> -----------------------------------------------------------
> Dennis Burgess, Mikrotik Certified Trainer=20
> Link Technologies, Inc -- Mikrotik & WISP Support Services
> Office: 314-735-0270 Website: http://www.linktechs.net
> LIVE On-Line Mikrotik Training - Author of "Learn RouterOS"
>=20
>=20
>> -----Original Message-----
>> From: Blake Hudson [mailto:blake@ispn.net]
>> Sent: Friday, December 16, 2011 8:11 AM
>> To: Dave Temkin
>> Cc: nanog@nanog.org
>> Subject: Re: Overall Netflix bandwidth usage numbers on a network?
>>=20
>> Requests to this address appear to go unanswered?
>>=20
>> Dave Temkin wrote the following on 12/11/2011 6:29 PM:
>>> Feel free to contact peering@netflix<dot>com - we're happy to provide
>>> you with delivery statistics for traffic terminating on your network.
>>>=20
>>> Regards,
>>> -Dave Temkin
>>> Netflix
>>>=20
>>> On 12/7/11 8:57 AM, Blake Hudson wrote:
>>>> 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).
>>>>=20
>>>>=20
>>>> Martin Hepworth wrote the following on 12/3/2011 2:36 AM:
>>>>> Also checkout Adrian Cockcroft presentations on their architecture
>>>>> which describes how they use aws and CDns etc
>>>>>=20
>>>>> Martin
>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>=20
