dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
9

rsaturns
join:2004-12-06
Beaverton, OR

rsaturns

Member

Re: [FiOS] Packet Loss / Latency - Beaverton, OR

Here's another traceroute from the latency tonight. I basically can barely load pages.

C:\Users\tifra>tracert youtube.com

Tracing route to youtube.com [173.194.46.6]
over a maximum of 30 hops:

1 tracert netflix.com

Tracing route to netflix.com [69.53.236.17]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms burney.tripplehelix.net.local [192.168.1.1]
2 4 ms 5 ms 4 ms static-50-53-96-1.bvtn.or.frontiernet.net [50.53
.96.1]
3 8 ms 7 ms 5 ms 50.38.7.157
4 33 ms 34 ms 32 ms ae2---0.cor01.bvtn.or.frontiernet.net [74.40.1.2
17]
5 39 ms 44 ms 42 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.2
21]
6 50 ms 49 ms 47 ms ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1
22]
7 90 ms 84 ms 74 ms 206.111.7.149.ptr.us.xo.net [206.111.7.149]
8 51 ms 47 ms 44 ms vb2002.rar3.sanjose-ca.us.xo.net [207.88.13.150]

9 28 ms 64 ms 27 ms 207.88.14.226.ptr.us.xo.net [207.88.14.226]
10 27 ms 27 ms 27 ms 216.156.84.6.ptr.us.xo.net [216.156.84.6]
11 27 ms 27 ms 27 ms xe-2-2-0-955.jnrt-edge02.prod1.netflix.com [69.5
3.225.30]
12 28 ms 27 ms 27 ms te1-8.csrt-agg02.prod1.netflix.com [69.53.225.10
]
13 27 ms 27 ms 27 ms www.trynetflix.com [69.53.236.17]

Trace complete.

Ben J
My spoon is too big
Premium Member
join:2011-09-16
Elk Grove, CA

Ben J

Premium Member

The traceroute doesn't really show it well, but this one is our problem too. It is separate, but somewhat related issue to the one reported in zebibyte's thread. That issue affects traffic only originating from Seattle, but affects everyone in Portland.... where as this one affects traffic from everywhere, but only for certain parts of Portland. We actually stumbled across this one while working on an unrelated project a few days ago and having one of those "hmmm... now that doesn't look right" moments, and finally nailed down the root cause this morning. Long story short, law of unintended consequences, we broke this ourselves while solving some other traffic issues over a year ago, it just didn't show up as a problem until the past couple weeks. We have a fix working its way through Engineering now.

rsaturns
join:2004-12-06
Beaverton, OR

rsaturns

Member

To which I can only respond with YAY! Would you mind posting back when the engineering group has implemented the change? Also if you need any other trace routes / packet captures I'm happy to provide. So far all it's done is force me to upgrade my internal infrastructure at home.

Ben J
My spoon is too big
Premium Member
join:2011-09-16
Elk Grove, CA

Ben J

Premium Member

Will do.

But I guess this is one way to convince the wife/gf to let you buy some new network gear. "No, honey... they said the only way we can fix the Netflix problem it is to order that new 802.11ac router from Newegg I've been telling you about...."

rsaturns
join:2004-12-06
Beaverton, OR

rsaturns

Member

Ha if only it was that cheap. So far it's been a lightweight AP and controller, and a new PoE ProCurve Switch. Granted part of this is to bolster up my CCNP lab.