dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
918
share rss forum feed

existenz

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

Google Fiber improves routing and performance

I've had GFiber a few months and have noticed they continue to improve the routing and performance. When first getting it, most traffic to coasts was routed through Chicago or Dallas. Now from KC they are routing through Denver or SLC to get to W Coast.

KC to SF Bay Area now goes through Denver instead of Dallas...
traceroute to 173.167.58.141

1 networkbox.home (192.168.1.1) 0.450 ms 0.385 ms 0.346 ms
2 xx.xx.xx.xx (xx.xx.xx.xx) 1.950 ms 2.027 ms 1.996 ms
3 ae11.bng01.mci124.googlefiber.net (192.119.17.146) 1.963 ms 1.931 ms 2.266 ms
4 ae7.ar01.mci102.googlefiber.net (192.119.17.68) 2.233 ms 2.199 ms 2.538 ms
5 xe-0-0-2.ar01.den101.googlefiber.net (192.119.17.14) 13.332 ms 13.299 ms 13.796 ms
6 ae0.ar01.den101.googlefiber.net (192.119.17.12) 51.060 ms 46.849 ms 46.805 ms
7 ae3.ar01.sjc101.googlefiber.net (192.119.17.149) 38.566 ms 38.468 ms 38.407 ms
8 te-0-4-0-7-pe02.11greatoaks.ca.ibone.comcast.net (173.167.58.141) 39.202 ms 39.163 ms 39.124 ms

KC to LA now goes through SLC instead of Dallas...
traceroute to www.aerioconnect.net (216.240.32.150), 30 hops max, 60 byte packets
1 networkbox.home (192.168.1.1) 0.560 ms 0.514 ms 0.484 ms
2 10.26.0.41 (10.26.0.41) 3.851 ms 4.451 ms 4.714 ms
3 ae11.bng01.mci124.googlefiber.net (192.119.17.146) 2.077 ms 2.054 ms 2.271 ms
4 ae7.ar01.mci102.googlefiber.net (192.119.17.68) 2.247 ms 2.385 ms 2.362 ms
5 xe-0-0-2.ar01.den101.googlefiber.net (192.119.17.14) 13.496 ms 13.464 ms 13.439 ms
6 ae2.ar01.slc101.googlefiber.net (192.119.17.155) 24.569 ms 23.407 ms 23.634 ms
7 ae1.pr01.slc101.googlefiber.net (192.119.17.159) 23.597 ms 23.648 ms 23.495 ms
8 he.net.slix.net (204.228.158.21) 23.873 ms 23.837 ms 23.840 ms
9 10ge1-1.core1.las1.he.net (184.105.222.157) 32.852 ms 32.678 ms 32.758 ms
10 10ge15-4.core1.lax2.he.net (184.105.222.161) 47.031 ms 46.961 ms 47.007 ms
11 aerioconnect.10gigabitethernet15-3.core1.lax2.he.net (184.105.224.250) 43.772 ms 43.845 ms 43.807 ms
12 fw-7-w1.oc530.aerioconnect.net (216.240.63.11) 43.768 ms 43.728 ms 43.146 ms
13 216.240.32.150 (216.240.32.150) 43.404 ms * *

To NYC area from KC continues to go through Chicago...
traceroute to 154.54.80.86 (154.54.80.86), 30 hops max, 60 byte packets
1 networkbox.home (192.168.1.1) 0.475 ms 0.406 ms 0.367 ms
2 10.26.0.41 (10.26.0.41) 2.237 ms 2.204 ms 2.402 ms
3 ae9.ar02.mci101.googlefiber.net (192.119.17.136) 2.367 ms 2.336 ms 2.352 ms
4 ae10.ar02.mci101.googlefiber.net (192.119.17.70) 2.317 ms 2.285 ms 2.450 ms
5 ae0.ar01.ord101.googlefiber.net (192.119.17.55) 12.912 ms 12.728 ms 12.973 ms
6 ae3.ar01.ord101.googlefiber.net (192.119.17.65) 12.938 ms 11.541 ms 11.385 ms
7 xe-11-0-2.edge4.Chicago3.Level3.net (4.53.98.81) 11.569 ms 30.312 ms 30.253 ms
8 be3032.ccr21.ord03.atlas.cogentco.com (154.54.12.81) 12.619 ms 12.530 ms 12.498 ms
9 be2005.ccr41.ord01.atlas.cogentco.com (66.28.4.73) 12.465 ms 12.859 ms 12.826 ms
10 be2116.mpd21.jfk02.atlas.cogentco.com (154.54.7.25) 33.422 ms 33.185 ms 34.335 ms
11 be2355.rcr21.jfk01.atlas.cogentco.com (154.54.43.94) 33.486 ms 33.468 ms be2357.rcr21.jfk01.atlas.cogentco.com (154.54.43.102) 33.854 ms
12 te8-2.mag01.jfk01.atlas.cogentco.com (154.54.80.86) 33.121 ms * *

From KC to Orlando goes through Chicago instead of Dallas...
traceroute to 4.69.137.149 (4.69.137.149), 30 hops max, 60 byte packets
1 networkbox.home (192.168.1.1) 0.520 ms 0.431 ms 0.386 ms
2 xx.xx.xx.xx 2.918 ms 2.885 ms 2.852 ms
3 ae9.ar02.mci101.googlefiber.net (192.119.17.136) 2.763 ms 2.741 ms 2.723 ms
4 ae10.ar02.mci101.googlefiber.net (192.119.17.70) 2.704 ms 2.766 ms 2.747 ms
5 ae0.ar01.ord101.googlefiber.net (192.119.17.55) 12.958 ms 13.179 ms 13.454 ms
6 ae3.ar01.ord101.googlefiber.net (192.119.17.65) 13.680 ms 11.548 ms 11.502 ms
7 xe-11-0-2.edge4.Chicago3.Level3.net (4.53.98.81) 11.472 ms 11.436 ms 11.374 ms
8 vlan52.ebr2.Chicago2.Level3.net (4.69.138.190) 11.496 ms 11.652 ms 11.780 ms
9 ae-5-5.ebr2.Chicago1.Level3.net (4.69.140.193) 11.958 ms 13.012 ms 12.972 ms
10 * * *
11 vl-101.ebr1.Atlanta2.Level3.net (4.69.202.65) 32.547 ms 32.512 ms 30.424 ms
12 ae-1-8.bar1.Orlando1.Level3.net (4.69.137.149) 38.674 ms 38.640 ms 38.764 ms

existenz

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

1 edit
When first getting Gfiber a few months ago I was able to get around 800Mbps from a single computer in KC and around 600-700Mbps to the coasts. Now it's more consistently 900+ in KC from single computer and 800+ to the coasts. If doing two computers concurrently, have always been able to pull over 900 net consistently.

These tests are after 8PM CST 7/20, during prime time traffic....

KC to KC (outside GFiber network)
»www.speedtest.net/my-result/3637410068

KC to Chicago
»www.speedtest.net/my-result/3637416681

KC to NYC
»www.speedtest.net/my-result/3637424337

KC to LA
»www.speedtest.net/my-result/3637428132

Edit: Here's what I was getting a few months ago...
»Speed tests....


karpodiem
Hail to The Victors
Premium
join:2008-05-20
Detroit, MI
reply to existenz
excellent post, thank you for sharing!

existenz

join:2014-02-12
kudos:2
Reviews:
·Google Fiber
Here is a morning test from one computer to Google's speedtest within Google's KC intranet...




karpodiem
Hail to The Victors
Premium
join:2008-05-20
Detroit, MI
yeezus...

davidhoffman
Premium
join:2009-11-19
Warner Robins, GA
kudos:3
reply to existenz
Absolutely terrible performance. Google Fiber ran lots of advertising talking about a minimum of 1000 Mbps download and a minimum of 1000 Mbps upload. Anything less than 999.95 Mbps download and 999.95 upload should be considered delivery of a substandard product that is not what was advertised. Please consider having the law firm of Dewey, Cheatem, and Howe file a frivolous lawsuit on your behalf for getting such slow internet service compared to that which was advertised.

existenz

join:2014-02-12
kudos:2
Reviews:
·Google Fiber
Heavy sarcasm noted but of course one could go back to TWC for 100/5 for over $70/month.

BTW, Google does market it as 'up to' 1Gbit. The most I've seen testing 2 computers concurrently is about 960Mbps net, which is about as high as it could probably go when factoring TCP/IP and app layer overhead. At the physical layer, it probably really is doing near a Gbit. Google can't really oversubscribe service past a Gbit - they apparently do oversubscribe to 1.3Gbit at the PON level (backend) but the ethernet port on the ONT/Fiber jack is still limited to a Gbit, as well as router ports.

Is good to see them improve longhaul routing, building up their own backend network. Performance to the coasts has improved lately. And apparently they are working on 10Gbit - not sure if for beefing up fiberhoods or if eventually planning for end users.

davidhoffman
Premium
join:2009-11-19
Warner Robins, GA
kudos:3
The futurists who years ago stated the need for ubiquitous 1 Gbps symmetrical residential service in the early part of the 21st century also stated that 10 Gbps symmetrical residential service would be desirable after the middle of the 21st century. Something about hologram rooms that allow interactive role playing to remotely treat stressed out people in the late 21st century from any place on Earth.

existenz

join:2014-02-12
kudos:2
{Pulling up Google Now in 2050} "OK Google, run holodeck program 'Amazon jungle before wiped out by humanity'".

But I'd be surprised if spacial holograms would be need by then, would expect direct input to brain a la 'Brainstorm'.

JasonBourne

join:2000-05-22
Kansas City, MO
Reviews:
·Google Fiber
reply to existenz
Here's a speedtest I just ran.