Google Home Speaker Bug Is Eating Hundreds of Gigabytes. Check Your Data Usage Now

If you own Google’s $99.99 Home Speaker, open your router app before you do anything else today. Some units are quietly downloading staggering amounts of data in the background, in some cases several terabytes in a month, and owners didn’t notice until their usage graphs spiked.

Google has acknowledged the problem. “We are aware of the issue, and a fix is already rolling out that should address this for users,” product manager Mark Alexander said, according to BGR. That’s good news. It isn’t much comfort if you’re on a plan with a data cap and the meter has already been running for two weeks.

What’s going wrong

The reports started piling up on Reddit’s r/googlehome forum over the past week and were picked up by 9to5Google on October 19, then by Android Authority, Android Central and BGR. The common thread is firmware. One Redditor said their speaker “kept downloading firmware and failing to install it.” Android Authority describes a loop in which a speaker pulled down a roughly 460MB update every 20 minutes without ever applying it. Do the math and that’s around 33GB to 35GB a day, from a speaker sitting on a shelf.

A replacement unit reportedly got stuck in the same loop, which suggests the problem sits on Google’s side rather than in any one defective speaker. One owner said the issue began within the past two weeks, according to Android Central.

How bad it gets: the reported numbers

The figures vary wildly between households, and most come from user reports rather than independent testing. Here’s what’s been documented so far:

The gap between 2GB and 3.3TB tells you two things. A healthy speaker barely touches your connection. An affected one can blow through a 1TB-class monthly cap on its own. The owner with three speakers said they use them for no more than 20 minutes a day.

It also doesn’t seem to touch older hardware. 9to5Google’s writer had several Nest Hubs on the same network that behaved normally, and another owner with a Nest Audio reported nothing unusual. This looks specific to the new Home Speaker.

How to check your Home Speaker’s data usage

The most reliable place to see what the speaker is pulling down is your router.

1. Nest Wifi or Google Wifi: open the Google Home app, go to the Wifi tab, tap Devices, pick the Home Speaker and check the usage graphs for 1, 7 or 30 days.
2. Other routers or ISP gateways: many router and gateway apps list per-device usage. Look for the speaker by name or by its MAC address.
3. Check your ISP account: if you have a monthly cap, log in to your provider’s site and look for an unexplained jump starting in early to mid October.

For reference, 9to5Google saw one speaker spike to 9.99GB around 3 a.m. Pacific and hit 41GB on October 13 alone. If your speaker shows double-digit gigabytes on days you barely spoke to it, you’re probably affected.

What to do until the fix lands

Google hasn’t given a timeline or details about the fix beyond saying it’s rolling out. Until your speaker stops misbehaving, you have a few options, roughly from least to most disruptive:

• Keep watching. If usage drops back to a couple of gigabytes a day or less, the fix has probably reached you.
• Cut its time online. Some routers can pause a single device or schedule its internet access. Pausing overnight targets the window where several owners saw the biggest spikes.
• Unplug it. BGR notes some owners have disconnected their speakers entirely. It’s blunt, but it’s the only sure way to stop the meter if you’re near your cap.
• Document it. Screenshot your router’s usage graph. If you get hit with overage fees, that record is what you’ll need when you call your ISP or Google support.

The bigger problem

This is the second rough patch for the Home Speaker since launch. Earlier this year, owners complained about painfully slow Gemini responses after an update that was supposed to make smart home commands “snappier,” and Google had to push another update to fix it. Now a firmware loop is chewing through bandwidth on a device whose whole job is to sit quietly until you talk to it.

Bugs happen. But a smart speaker that can silently run up a customer’s internet bill needs better guardrails than this: a retry limit on failed updates, a warning in the Home app, something. Google should also say plainly whether it will help owners who got charged overage fees. Until it does, the router graph is your best friend.

Sources: 9to5Google, Android Authority, Android Central, BGR. Photo by Jonas Leupe on Unsplash.