Google Fiber

Google Fiber launched in 2010 as something close to a thought experiment made real: what if a technology company built the internet infrastructure that internet companies complained was holding them back? Gigabit residential internet was essentially unheard of at the time, and Google Fiber's arrival in Kansas City prompted incumbent cable providers to scramble and upgrade their own networks in competitive markets — a competitive pressure effect that analysts argue improved broadband quality for millions of people who never subscribed to Google Fiber directly.

The service expanded through the 2010s, paused, then re-accelerated in the 2020s under the Alphabet subsidiary Access (formerly Google Fiber Inc.). Cities including Austin, Salt Lake City, Nashville, Charlotte, and others joined the network, with the product evolving to include multi-gig tiers and a no-data-cap philosophy that differentiated it from cable competitors. Google Fiber uses fiber-to-the-premises architecture with its own designed hardware, the Google Fiber Network Box, which integrates routing, Wi-Fi, and the Fiber app experience into a single managed device.

When Google Fiber goes down, users typically see the Network Box status LED shift from solid white to a blinking or amber state indicating loss of upstream connectivity. The Fiber app loses the ability to report network status or manage connected devices when the backend is unavailable. Regional fiber cuts or central equipment failures cause neighborhood-scale outages. DNS failures — where the link stays active but name resolution stops working — appear as "no internet" to most applications even though the physical connection is technically up.

Outage.gg monitors Google Fiber service status using real-time community-submitted outage reports. If your Google Fiber connection is down, slow, or the app is unresponsive, the live status page shows current reports from subscribers in your city and beyond.