|A Technical Look at Google Fiber||August 12, 2012|
While visiting Kansas City recently, I decided to investigate Google Fiber, Google's ambitious new residential gigabit Internet service they are building in Kansas City, Kansas, and central Kansas City, Missouri. While they haven't connected residential customers to the network yet, they have provisioned service at several local businesses. They also opened a showroom called "Fiber Space" to demonstrate the service to potential customers.
My first stop was the Mud Pie Vegan Bakery and Coffeehouse, a neat coffee house in a historic area of Midtown Kansas City. Mud Pie has the Google Fiber hookup, which customers can use via Wi-Fi or the ethernet-attached Chromebooks which Google has provided. I tried to convince the barista to let me borrow the ethernet connection from a Chromebook so I could test the fast path, but he declined due to Google not wanting people to interfere with their hardware in such a way. However, I found I was able to accomplish most of my investigation goals using a combination of my laptop on Wi-Fi and the wired Chromebooks. I ended up hanging out at Mud Pie for several hours, running tests and chatting with the barista and customers.
Four blocks south of Mud Pie, Google has set up a showroom for Google Fiber called "Fiber Space." It's a very consumer-oriented experience aimed at selling the service to locals. Many Google Fiber employees are on hand to show people what hardware they'll need, and demonstrate the Internet and TV services in virtual living rooms. The "car roller coaster" set from the Google Fiber promotional video and free snacks were also on hand. In addition to the wired Chromebooks on display, people can bring their laptops to try out Google Fiber via the Wi-Fi. However, an employee told me that they didn't allow hooking up to the wire, citing a concern about piracy or illegal activities or some such. (Which sounds like a pretty weak excuse to me.)
Naturally, the first thing people want to know about Google Fiber is how fast is it, really? Unfortunately, it's difficult to reliably measure the practical speed of the service due to the many other bottlenecks that exist once you remove the bottleneck of the last mile. Also, since others have performed plenty of speed tests, I decided to focus more on other characteristics of the network. However, I did run a few throughput tests for good measure.
Here is the result from speedtest.net, running on the wired Chromebook:
I tried running the test against servers in other locales, but the default Palo Alto server delivered the best result. I don't think these tests are great measures of throughput for such high speeds, since not only might the test servers be bottlenecked, but they may not run the tests long enough for the TCP window size to ramp up to the connection's true capacity.
A slightly better test was to download very large files full of random data from various cloud servers:
|data center||file size||time||rate|
|Forethought.net (Denver)||100MB||8 seconds||104.858 Mbps|
|Forethought.net (Denver)||512MB||42 seconds||102.261 Mbps|
|Forethought.net (Denver)||512MB||41 seconds||104.755 Mbps|
|Linode (Dallas)||256MB||72 seconds||29.826 Mbps|
|Linode (Dallas)||256MB||79 seconds||27.183 Mbps|
I don't know why the Linode download was so slow, although the outbound route to that server went out to California, and even across Comcast's network (!) before heading to Dallas. The download from a server at Forethought hit a much higher bottleneck somewhere, but it's difficult to say where.
I performed pings and traceroutes to a number of hosts, to get an idea of Google Fiber's positioning on the network and the available peering points for outbound packets. These tests were conducted from the Wi-Fi network at Mud Pie, so a few milliseconds can be attributed to local Wi-Fi latency (see the first item on the list).
|networkbox||1.766||2.736||5.007||0.909||The local gateway, for reference|
|www.apple.com||Dallas, TX (see notes)||33.024||35.813||39.896||2.499||Akamai CDN node in Dallas, TX|
|www.kcnap.net||Kansas City, MO||75.605||76.977||78.628||0.902|
|www.frgp.net||Denver, CO||19.390||20.931||23.498||1.576||Major peering point in Denver|
|cafbit.com||Denver, CO||48.177||52.195||58.210||3.121||You are here|
|www.facebook.com||Palo Alto, CA||70.686||75.499||80.526||3.325|
|188.8.131.52||Mountain View, CA||39.154||42.498||45.488||2.106||Last Googlebot host to visit cafbit.com|
|b.root-servers.net||Marina Del Rey, CA||50.488||53.980||55.954||1.805|
|d.root-servers.net||College Park, MD||118.310||122.118||134.235||4.868|
|l.root-servers.net||San Jose, CA||47.904||48.733||49.733||0.561||(anycast)|
The full ping/traceroute output is available.
As far as I can tell, outbound packets exit Google Fiber's network via links to either San Jose, CA, or Dallas, TX. In San Jose, Google Fiber seems to be peering with Comcast and XO communications. (Presumably at Equinix's 11 Great Oaks facility.) In Dallas, Google Fiber seems to peer with Level 3 and Google's main network (which is a separate autonomous system from Google Fiber). As you might expect, access to Google services (such as Google Drive and YouTube) is quite snappy from the Google Fiber network.
While on Mud Pie's network, my laptop was assigned an IPv6 address in the fc00::/7 block which is designated for unique local addresses. However, I'm not sure what the point of this is. I definitely could not reach the IPv6 internet via ping6.
Google Fiber is fast. If it was available in my neighborhood, I'd sign up.
UPDATE 2012-12-28: I've made another visit to Kansas City... see my post about plugging into the ethernet at the Hacker House.