dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
8739

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

2 edits

SeattleMatt

Premium Member

[Networking] 1st Proof of Verizon / Netflix Direct Peering????

Click for full size
VZ Netflix Direct Peering
I fired up a Netflix feed on my MacBook this morning and decided to see where I was getting routed to with all of the fuss the past weeks.

I noticed that it ramped up VERY quickly - quicker than ever before - and ran a Netstat to see what IP it was going to.

Ran a trace - and lo and behold - this may be the 1st real sign that VZ is now peering directly with Netflix. From the attached image - you can see I connected in UNDER 10ms! There are no longer any 3rd party transits (Ntt, Telia, etc...)

I went from VZ in Philly - to Alter.net in NYC (Which is VZ) - directly to a Netflix peer in NYC.
PJL
join:2008-07-24
Long Beach, CA

PJL

Member

Re: [Networking] 1st Proof of Verizon / Netflix Direct Peering

I think still seeing 3rd-party peering in LA (using NTT.net now versus Telia.net) but the streams are now "SuperHD" quality.

Here's my current trace. (You can see the prior trace over Telia on the other recent thread.)

1 1 ms 1 ms 1 ms 192.168.1.1
2 5 ms 4 ms 3 ms L100.LSANCA-VFTTP-128.verizon-gni.net [96.229.59.1]
3 10 ms 11 ms 11 ms G1-6-0-1.LSANCA-LCR-21.verizon-gni.net [100.41.196.46]
4 47 ms 7 ms 9 ms so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
5 8 ms 9 ms 9 ms 0.xe-10-1-0.BR1.LAX15.ALTER.NET [152.63.112.245]
6 11 ms 11 ms 10 ms ae-7.r05.lsanca03.us.bb.gin.ntt.net [129.250.8.85]
7 17 ms 17 ms 17 ms ae-5.r04.lsanca03.us.bb.gin.ntt.net [129.250.2.220]
8 11 ms 11 ms 12 ms 129.250.199.50
9 8 ms 8 ms 9 ms ipv4_1.lagg0.c047.lax001.ix.nflxvideo.net [108.175.46.92]

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

PJ-
I was with Comcast when they were implementing their peering - and you saw more and more direct links pop up over a few weeks period. I'm wondering if the NYC link may be 1 of the first...

BioGeek
Quantum-VHO7
Premium Member
join:2007-08-25
West Orange, NJ

BioGeek to SeattleMatt

Premium Member

to SeattleMatt
I was getting some great resolution last night on Netflix. I will try a fresh trace route tonight to see if I am getting better routing than before. I noticed a better hold at the 720 and 1080 res last night than before. Less 480 streams.
PJL
join:2008-07-24
Long Beach, CA

PJL to SeattleMatt

Member

to SeattleMatt
I just did another check (five minutes apart) and the routing was different as it went to a different Netflix server, this time via level3. This time the performance took forever to ramp up and did not go above 720p. So different routing (which appears to be direct to Netflix) with worse performance. Go figure :-(
1 1 ms 1 ms 1 ms 192.168.1.1
2 115 ms 129 ms 7 ms L100.LSANCA-VFTTP-128.verizon-gni.net [96.229.59.1]
3 7 ms 11 ms 7 ms G0-14-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.191.122]
4 6 ms 6 ms 8 ms ae2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.209.254]
5 8 ms 7 ms 7 ms 0.xe-10-1-0.BR1.LAX15.ALTER.NET [152.63.112.245]
6 10 ms 11 ms 9 ms ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
7 16 ms 16 ms 15 ms 4.53.228.170
8 7 ms 8 ms 7 ms ipv4_1.lagg0.c039.lax004.ix.nflxvideo.net [198.38.97.148]

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

PJ-
Looks like you're still getting there via Level 3 (Hops 6/7)

BioGeek
Quantum-VHO7
Premium Member
join:2007-08-25
West Orange, NJ

BioGeek to PJL

Premium Member

to PJL
I find some of the resolution issues to be random. I can pause and start or close netflix and restart and somehow end up with better or worse resolution each time. I can do that multiple times in a 5 minute window and get all sorts of different streaming resolution. I almost feel like I am playing the Netflix lottery.
PJL
join:2008-07-24
Long Beach, CA

1 recommendation

PJL to SeattleMatt

Member

to SeattleMatt
said by SeattleMatt:

PJ-
Looks like you're still getting there via Level 3 (Hops 6/7)

Yes, I see that. It's interesting that Netflix has me hitting different servers with successive streams playing the Netflix text video. They're likely controlling which server replies with the stream, not Verizon, so they are controlling which route back the stream takes.

I hope you're correct that direct peering is moving along and will eventually get here to Southern California. (Since you're usually correct on these things, I'm betting on you.)
PJL

PJL to BioGeek

Member

to BioGeek
said by BioGeek:

I find some of the resolution issues to be random. I can pause and start or close netflix and restart and somehow end up with better or worse resolution each time. I can do that multiple times in a 5 minute window and get all sorts of different streaming resolution. I almost feel like I am playing the Netflix lottery.

I see the same random performance. And (per my earlier post) Netflix controls the server being used for the stream so they likely control the path back.
serge87
join:2009-11-29
New York

serge87 to SeattleMatt

Member

to SeattleMatt

Re: [Networking] 1st Proof of Verizon / Netflix Direct Peering????

Still Telia, XO or Level3 for me.
billhere
join:2011-10-21
Santa Monica, CA

billhere to SeattleMatt

Member

to SeattleMatt
I just signed up for my free month of Netflix using Apple TV yesterday. I switched to Google's servers on my Apple TV and played an HD TV show flawlessly last night in prime time.

When I initially tried to sign up for Netflix I got a moving circle and "Accessing Netflix" on screen for about five minutes before I gave up. I had no idea whether I had an Apple TV, Netflix, or Verizon problem. I called Verizon first but after being told I would be on hold for 15 minutes I gave up and called Netflix. The Netflix CSR answered within 30 seconds. His first suggestion was to pull the plug on the Apple TV and then plug it back in. That worked! I could then sign up and watch programming. Netflix may have me as a paying customer next month.
tnsprin
join:2003-07-23
Bradenton, FL

tnsprin to SeattleMatt

Member

to SeattleMatt

Re: [Networking] 1st Proof of Verizon / Netflix Direct Peering

Texas was suppose to be first according to a statement quoted in one article.
said by SeattleMatt:

PJ-
I was with Comcast when they were implementing their peering - and you saw more and more direct links pop up over a few weeks period. I'm wondering if the NYC link may be 1 of the first...

serge87
join:2009-11-29
New York

1 recommendation

serge87 to SeattleMatt

Member

to SeattleMatt

Re: [Networking] 1st Proof of Verizon / Netflix Direct Peering????

Total completion of the Netflix-Verizon direct peering process will take around 8 months, or towards the end of 2014(Oct-Dec). Some states will come online sooner than others depending on the order Verizon does things.

bigdaddy
join:2009-11-18

bigdaddy to SeattleMatt

Member

to SeattleMatt
WinMTR Statistics
WinMTR statistics


Host % Sent Recv Best Avrg Wrst Last
192.168.0.100 0 25 25 0 0 0 0
L100.TAMPFL-VFTTP-109.verizon-gni.net 0 25 25 1 2 21 1
G0-5-3-1.TAMPFL-LCR-22.verizon-gni.net 5 21 20 0 3 5 4
ae2-0.TPA01-BB-RTR2.verizon-gni.net 5 21 20 0 10 54 2
0.xe-3-1-8.XT2.ATL4.ALTER.NET 5 21 20 0 36 120 20
0.ae4.GW9.DFW7.ALTER.NET 5 21 20 0 39 52 38
netflix-gw.customer.alter.net 5 21 20 0 59 62 57
ipv4_1.lagg0.c130.dfw001.ix.nflxvideo.net 0 25 25 128 133 135 135

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.100 - 0 | 25 | 25 | 0 | 0 | 0 | 0 |
| L100.TAMPFL-VFTTP-109.verizon-gni.net - 0 | 25 | 25 | 1 | 2 | 21 | 1 |
| G0-5-3-1.TAMPFL-LCR-22.verizon-gni.net - 5 | 21 | 20 | 0 | 3 | 5 | 4 |
| ae2-0.TPA01-BB-RTR2.verizon-gni.net - 5 | 21 | 20 | 0 | 10 | 54 | 2 |
| 0.xe-3-1-8.XT2.ATL4.ALTER.NET - 5 | 21 | 20 | 0 | 36 | 120 | 20 |
| 0.ae4.GW9.DFW7.ALTER.NET - 5 | 21 | 20 | 0 | 39 | 52 | 38 |
| netflix-gw.customer.alter.net - 5 | 21 | 20 | 0 | 59 | 62 | 57 |
|ipv4_1.lagg0.c130.dfw001.ix.nflxvideo.net - 0 | 25 | 25 | 128 | 133 | 135 | 135 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Here is the Netflix IP that has direct peering. 198.45.55.194

Oh happy day, oh happy day

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

Click for full size
DAL Direct Peering
Bigdaddy-
Nice find! Tried a trace from here in Delaware - check it out!

Most interesting is Hop 10 -

netflix-gw.customer.alter.net

Well there we have it - a Direct peering naming convention I think we'll come to expect.
jh2010
join:2009-09-03
Brooklyn, NY

jh2010 to SeattleMatt

Member

to SeattleMatt
Not working in NYC yet

C:\Users\xxxxx>tracert netflix-gw.customer.alter.net

Tracing route to netflix-gw.customer.alter.net [199.101.28.20]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home-router xxxxxx
2 2 ms 2 ms 3 ms xxxxxxxxx
3 5 ms 7 ms 4 ms G0-14-0-6.NYCMNY-LCR-21.verizon-gni.net [130.81.189.234]
4 5 ms 4 ms 6 ms 130.81.199.10
5 * * * Request timed out.
6 7 ms 6 ms 6 ms 0.ae2.BR3.NYC4.ALTER.NET [140.222.229.99]
7 4 ms 6 ms 6 ms 208.49.136.37
8 17 ms 24 ms 16 ms te1-1-10G.ar3.DCA3.gblx.net [67.17.108.134]
9 17 ms 19 ms 16 ms NOMINUM.Gi9-7.ar3.DCA3.gblx.net [64.212.109.90]
10 37 ms 42 ms 37 ms search.dnsassist.verizon.net [199.101.28.20]

Trace complete.
flashcore
join:2007-01-23
united state

flashcore

Member

netflix-gw.customer.alter.net does not resolve to any IP address. What you are seeing is Verizon's DNS poisoning resolving there search page.
jh2010
join:2009-09-03
Brooklyn, NY

jh2010

Member

that is why I said NOT working in NYC.

guppy_fish
Premium Member
join:2003-12-09
Palm Harbor, FL

guppy_fish

Premium Member

»ip-address-lookup-v4.com ··· .187.202

thatguythere
@108.13.189.x

thatguythere to jh2010

Anon

to jh2010
said by jh2010:

that is why I said NOT working in NYC.

He's saying that it's not a valid name you can lookup. It won't return the proper IP address no matter the connection used to resolve it. You'll need to tracert it via the IP address shown.
jh2010
join:2009-09-03
Brooklyn, NY

jh2010 to SeattleMatt

Member

to SeattleMatt
My trace to ipv4_1.lagg0.c039.lax004.ix.nflxvideo.net via NYC
I am sure there will be East Coast names in the future.

C:\Users\xxxxx>tracert ipv4_1.lagg0.c039.lax004.ix.nflxvideo.net

Tracing route to ipv4_1.lagg0.c039.lax004.ix.nflxvideo.net [198.38.97.148]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home-router
2 3 ms 2 ms 2 ms xxxxxx
3 5 ms 7 ms 7 ms G0-14-0-6.NYCMNY-LCR-21.verizon-gni.net [130.81.189.234]
4 5 ms 6 ms 6 ms so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.151.222]
5 * * * Request timed out.
6 5 ms 23 ms 15 ms 0.ae1.BR3.NYC4.ALTER.NET [140.222.229.97]
7 * * * Request timed out.
8 83 ms 82 ms 83 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
9 83 ms 83 ms 86 ms ae-38-38.ebr2.Washington1.Level3.net [4.69.201.85]
10 82 ms 78 ms 85 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
11 83 ms 81 ms 80 ms ae-81-81.ebr1.Washington1.Level3.net [4.69.134.137]
12 82 ms 83 ms 79 ms ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]
13 76 ms 81 ms 84 ms ae-63-63.csw1.LosAngeles1.Level3.net [4.69.137.34]
14 79 ms 83 ms 82 ms ae-1-60.edge1.LosAngeles9.Level3.net [4.69.144.10]
15 84 ms 83 ms 81 ms 4.53.228.170
16 82 ms 83 ms 78 ms ipv4_1.lagg0.c039.lax004.ix.nflxvideo.net [198.38.97.148]

Trace complete.

bigdaddy
join:2009-11-18

bigdaddy to SeattleMatt

Member

to SeattleMatt
Here are some more Verizon-Netflix direct links.

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.100 - 0 | 88 | 88 | 0 | 0 | 0 | 0 |
| L100.TAMPFL-VFTTP-109.verizon-gni.net - 0 | 88 | 88 | 1 | 2 | 24 | 1 |
| G0-5-3-1.TAMPFL-LCR-22.verizon-gni.net - 2 | 84 | 83 | 0 | 3 | 12 | 4 |
| ae8-0.TPA01-BB-RTR2.verizon-gni.net - 2 | 84 | 83 | 0 | 7 | 89 | 2 |
| 0.xe-3-1-8.XT2.ATL4.ALTER.NET - 0 | 88 | 88 | 17 | 28 | 98 | 20 |
| 0.ae4.GW9.DFW7.ALTER.NET - 0 | 88 | 88 | 38 | 38 | 63 | 38 |
| netflix-gw.customer.alter.net - 0 | 88 | 88 | 34 | 34 | 37 | 34 |
|ipv4_1.lagg0.c136.dfw001.ix.nflxvideo.net - 0 | 88 | 88 | 35 | 35 | 37 | 36 |
|________________________________________________|______|______|______|______|______|______|
IP 198.45.54.200

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.100 - 0 | 14 | 14 | 0 | 0 | 1 | 0 |
| L100.TAMPFL-VFTTP-109.verizon-gni.net - 0 | 14 | 14 | 1 | 1 | 2 | 1 |
| G0-14-1-5.TAMPFL-LCR-21.verizon-gni.net - 10 | 11 | 10 | 0 | 4 | 8 | 5 |
| ae5-0.TPA01-BB-RTR1.verizon-gni.net - 10 | 11 | 10 | 0 | 19 | 99 | 3 |
| 0.xe-3-1-2.XT1.ATL4.ALTER.NET - 10 | 11 | 10 | 0 | 30 | 79 | 17 |
| 0.ae3.GW9.DFW7.ALTER.NET - 10 | 11 | 10 | 0 | 38 | 42 | 38 |
| netflix-gw.customer.alter.net - 10 | 11 | 10 | 0 | 39 | 48 | 35 |
|ipv4_1.lagg0.c150.dfw001.ix.nflxvideo.net - 0 | 14 | 14 | 34 | 35 | 37 | 35 |
|________________________________________________|______|______|______|______|______|______|
IP 198.45.55.199

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.100 - 0 | 17 | 17 | 0 | 0 | 1 | 0 |
| L100.TAMPFL-VFTTP-109.verizon-gni.net - 0 | 17 | 17 | 1 | 7 | 77 | 1 |
| G0-14-1-5.TAMPFL-LCR-21.verizon-gni.net - 8 | 13 | 12 | 0 | 5 | 6 | 6 |
| ae1-0.TPA01-BB-RTR1.verizon-gni.net - 8 | 13 | 12 | 0 | 10 | 77 | 2 |
| 0.xe-3-1-2.XT1.ATL4.ALTER.NET - 8 | 13 | 12 | 0 | 18 | 25 | 17 |
| 0.ae3.GW9.DFW7.ALTER.NET - 8 | 13 | 12 | 0 | 38 | 39 | 38 |
| netflix-gw.customer.alter.net - 8 | 13 | 12 | 0 | 40 | 48 | 34 |
|ipv4_1.lagg0.c088.dfw001.ix.nflxvideo.net - 8 | 13 | 12 | 0 | 40 | 48 | 35 |
|________________________________________________|______|______|______|______|______|______|
IP 198.45.55.167

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.100 - 0 | 11 | 11 | 0 | 0 | 0 | 0 |
| L100.TAMPFL-VFTTP-109.verizon-gni.net - 0 | 11 | 11 | 1 | 1 | 1 | 1 |
| G0-5-3-1.TAMPFL-LCR-22.verizon-gni.net - 13 | 8 | 7 | 0 | 4 | 10 | 10 |
|so-2-0-0-0.TPA01-BB-RTR2.verizon-gni.net - 13 | 8 | 7 | 0 | 9 | 27 | 2 |
| 0.xe-1-0-0.XT2.ATL4.ALTER.NET - 13 | 8 | 7 | 0 | 27 | 62 | 16 |
| 0.ae2.GW9.DFW7.ALTER.NET - 0 | 11 | 11 | 38 | 38 | 39 | 38 |
| netflix-gw.customer.alter.net - 0 | 11 | 11 | 34 | 34 | 34 | 34 |
|ipv4_1.lagg0.c019.dfw001.ix.nflxvideo.net - 0 | 11 | 11 | 34 | 34 | 35 | 34 |
|________________________________________________|______|______|______|______|______|______|
IP 198.45.54.148

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.100 - 0 | 10 | 10 | 0 | 0 | 1 | 0 |
| L100.TAMPFL-VFTTP-109.verizon-gni.net - 0 | 10 | 10 | 1 | 10 | 89 | 1 |
| G0-14-1-5.TAMPFL-LCR-21.verizon-gni.net - 17 | 6 | 5 | 0 | 4 | 6 | 5 |
| 130.81.199.26 - 17 | 6 | 5 | 0 | 9 | 33 | 5 |
| 0.xe-3-1-2.XT1.ATL4.ALTER.NET - 17 | 6 | 5 | 0 | 29 | 70 | 17 |
| 0.ae3.GW9.DFW7.ALTER.NET - 17 | 6 | 5 | 0 | 38 | 39 | 38 |
| netflix-gw.customer.alter.net - 0 | 10 | 10 | 34 | 41 | 47 | 40 |
|ipv4_1.lagg0.c192.dfw001.ix.nflxvideo.net - 17 | 6 | 5 | 0 | 35 | 37 | 35 |
|________________________________________________|______|______|______|______|______|______|
IP 198.45.55.221
PJL
join:2008-07-24
Long Beach, CA

PJL to SeattleMatt

Member

to SeattleMatt
Anyone know how to force Netflix to assign you to a different streaming server? Apparently when I sign into Netflix I get a streaming server assigned at that time (or it uses a "nearby" server). I would like to figure out if there is a way to use one of the peered servers. Netflix is still using their (low-powered) ISP (Telia, etc.) for my connections. It's nice to see that Netflix is moving to having Verizon as their ISP for Verizon customers (that's how I consider these new "peering points") instead of these companies for at least some areas with more to come.

I'm using the Windows 8, Sony Blu-ray, Android app and Android app casting to Chromecast. Maybe if I configure the firewall to not accept connections from the server Netflix assigns to me?

bigdaddy
join:2009-11-18

bigdaddy

Member

Are there any TX FiOS user's here that can test and confirm that they are also getting these new Netflix direct peering routes ?

Thanks.
bigdaddy

bigdaddy to guppy_fish

Member

to guppy_fish
This is interesting. This is a New Jersey IP 152.179.187.202 and yet I am routed thru to DFW 0.ae2.GW9.DFW7.ALTER.NET ?

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.100 - 0 | 30 | 30 | 0 | 0 | 0 | 0 |
| L100.TAMPFL-VFTTP-109.verizon-gni.net - 4 | 26 | 25 | 0 | 1 | 4 | 1 |
| G0-14-1-5.TAMPFL-LCR-22.verizon-gni.net - 4 | 26 | 25 | 0 | 4 | 20 | 4 |
|so-2-0-0-0.TPA01-BB-RTR2.verizon-gni.net - 0 | 30 | 30 | 2 | 9 | 53 | 2 |
| 0.xe-1-0-0.XT2.ATL4.ALTER.NET - 4 | 26 | 25 | 0 | 26 | 70 | 51 |
| 0.ae2.GW9.DFW7.ALTER.NET - 4 | 26 | 25 | 0 | 39 | 42 | 40 |
| netflix-gw.customer.alter.net - 0 | 30 | 30 | 48 | 63 | 134 | 48 |
|________________________________________________|______|______|______|______|______|______|
IP 152.179.187.202
tnsprin
join:2003-07-23
Bradenton, FL

tnsprin

Member

said by bigdaddy:

This is interesting. This is a New Jersey IP 152.179.187.202 and yet I am routed thru to DFW 0.ae2.GW9.DFW7.ALTER.NET ?

|---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.100 - 0 | 30 | 30 | 0 | 0 | 0 | 0 |
| L100.TAMPFL-VFTTP-109.verizon-gni.net - 4 | 26 | 25 | 0 | 1 | 4 | 1 |
| G0-14-1-5.TAMPFL-LCR-22.verizon-gni.net - 4 | 26 | 25 | 0 | 4 | 20 | 4 |
|so-2-0-0-0.TPA01-BB-RTR2.verizon-gni.net - 0 | 30 | 30 | 2 | 9 | 53 | 2 |
| 0.xe-1-0-0.XT2.ATL4.ALTER.NET - 4 | 26 | 25 | 0 | 26 | 70 | 51 |
| 0.ae2.GW9.DFW7.ALTER.NET - 4 | 26 | 25 | 0 | 39 | 42 | 40 |
| netflix-gw.customer.alter.net - 0 | 30 | 30 | 48 | 63 | 134 | 48 |
|________________________________________________|______|______|______|______|______|______|
IP 152.179.187.202

That corresponds to the comments of Texas connections being done first.

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

1 recommendation

SeattleMatt

Premium Member

It's definitely still random - and the non direct peering stinks.

This AM fired up a stream - took well over 90 seconds to ramp up to HD.

Researched and I was accessing a peer in Atlanta - but went out over NTT.net.
PJL
join:2008-07-24
Long Beach, CA

PJL

Member

said by SeattleMatt:

It's definitely still random - and the non direct peering stinks.

This AM fired up a stream - took well over 90 seconds to ramp up to HD.

Researched and I was accessing a peer in Atlanta - but went out over NTT.net.

If you're referring to 720p, that's what the streams are maxing out for us, also via NTT.net. It's way-off peak but the stream never goes above SuperHD (1080p) quality.

Since Netflix controls the stream rate I have to infer that they're capping non-direct connections (those through third part ISPs).

SeattleMatt
Streaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA

SeattleMatt

Premium Member

Click for full size
Netflix - Dallas Peering
Ran a Netflix test on my MacBook this morning - noticed that it ramped up to HD almost immediately. Looks like a new direct peering point has been set up in Dallas, TX.

So, we now have 2 confirmed direct peers - in NYC and TX.

guppy_fish
Premium Member
join:2003-12-09
Palm Harbor, FL

guppy_fish to SeattleMatt

Premium Member

to SeattleMatt
It will be interesting to see what percentages of bandwidth declines there are on the internet for Netflix traffic as Comcast and Verizon become direct connections.