dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
9
share rss forum feed

existenz

join:2014-02-12
kudos:2
Reviews:
·Google Fiber

4 edits
reply to iansltx

Re: Google Fiber Kansas City

said by iansltx:

Also, mind tracing to 108.61.204.176? It's in Dallas. My bet is you'll get there in 10ms.

This time it routed through Chicago before going to Dallas...

traceroute 108.61.204.176
traceroute to 108.61.204.176 (108.61.204.176), 30 hops max, 60 byte packets
1 networkbox.home (192.168.1.1) 1.468 ms 1.448 ms 1.434 ms
2 xx.xx.xx.xx (xx.xx.xx.xx) 3.397 ms 3.401 ms 3.405 ms
3 * * *
4 xx.ar01.mci101.googlefiber.net (xx) 3.345 ms 3.328 ms 3.314 ms
5 ae0.ar01.ord101.googlefiber.net (192.119.17.55) 13.475 ms 13.721 ms 13.718 ms
6 ae3.pr01.ord101.googlefiber.net (192.119.17.65) 14.000 ms 11.548 ms 11.825 ms
7 xe-1-3-0.chi11.ip4.tinet.net (199.229.231.109) 11.668 ms 11.600 ms 11.687 ms
8 xe-3-2-0.dal33.ip4.tinet.net (141.136.109.150) 25.157 ms xe-2-0-0.dal33.ip4.tinet.net (89.149.185.85) 33.221 ms xe-3-1-0.dal33.ip4.tinet.net (89.149.180.246) 25.516 ms
9 gtt-gw.ip4.tinet.net (173.241.130.138) 25.622 ms 24.791 ms 24.588 ms
10 as20473.xe-5-1-2.cr1.dfw1.us.nlayer.net (69.31.63.238) 25.625 ms 25.182 ms 25.382 ms
11 108.61.204.176.vultr.com (108.61.204.176) 25.890 ms 26.127 ms 25.764 ms

Here's one to dallas.com, this one goes straight from KC (mci is KC airport code) to Dallas...

(66.111.96.159), 30 hops max, 60 byte packets
1 networkbox.home (192.168.1.1) 1.000 ms 0.987 ms 0.974 ms
2 xx (xx) 2.847 ms 2.833 ms 2.816 ms
3 * * *
4 xx.ar01.mci101.googlefiber.net (xx) 2.756 ms 2.747 ms 2.864 ms
5 ae0.ar01.dfw101.googlefiber.net (192.119.17.53) 12.002 ms 12.206 ms 12.176 ms
6 ae4.pr01.dfw101.googlefiber.net (192.119.17.67) 12.256 ms 10.327 ms 10.293 ms
7 xe-7-1-0.edge5.Dallas3.Level3.net (4.59.36.57) 10.253 ms 54.555 ms 54.484 ms
8 ae-42-90.car2.Dallas1.Level3.net (4.69.145.196) 10.957 ms ae-22-70.car2.Dallas1.Level3.net (4.69.145.68) 11.164 ms 11.362 ms
9 HOSTING.COM.car2.Dallas1.Level3.net (4.71.171.82) 11.587 ms 10.692 ms 10.700 ms
10 ae1-core1.dal01.hosting.com (199.168.255.5) 10.921 ms ae1-core2.dal01.hosting.com (199.168.255.7) 11.508 ms ae1-core1.dal01.hosting.com (199.168.255.5) 11.512 ms
11 199.168.255.21 (199.168.255.21) 12.078 ms po4-dist3.dal01.hosting.com (199.168.255.15) 12.253 ms 199.168.255.21 (199.168.255.21) 12.221 ms
12 66-111-96-159.neospire.net (66.111.96.159) 12.232 ms 12.468 ms 12.601 ms

Edit: I did various tests to coasts and looks like anything E goes through Chicago, anything W or S goes through Dallas, which is strange because KC has over 12 longhaul providers that have trunks from KC to both coasts. I would think Denver or Phoenix would be a hop if not straight to W coast.

Edit: Anyone happen to have IP or name of a Netflix streaming server, not the website but actual streaming server? I guess I'll do a tcpdump on a Netflix session and find one.

Edit: Here's a speedtest to a Dallas server...



CoolMan

join:2008-01-07
Tennessee
kudos:2
Reviews:
·Charter
·Suddenlink
said by existenz:

Edit: Anyone happen to have IP or name of a Netflix streaming server, not the website but actual streaming server? I guess I'll do a tcpdump on a Netflix session and find one.

Here is a few:

108.175.35.136

108.175.41.138

108.175.40.69

108.175.43.135

existenz

join:2014-02-12
kudos:2
Reviews:
·Google Fiber
said by CoolMan:

said by existenz:

Edit: Anyone happen to have IP or name of a Netflix streaming server, not the website but actual streaming server? I guess I'll do a tcpdump on a Netflix session and find one.

Here are a few:

108.175.35.136

108.175.41.138

108.175.40.69

108.175.43.135

Thanks, I found what I connect to but it doesn't seem Google is using Netflix CDN yet. Maybe they don't need it.