Google Home and Google Nest users are reporting a frustrating slowdown this morning, with some smart speakers still hearing commands but taking an unusually long time to answer. In some cases, the reply arrives after roughly 30 seconds; in others, no response comes at all before the request times out.
The complaints are spreading across Reddit, suggesting the problem is not isolated to a single household or a single device. For affected users, the issue feels less like a minor delay and more like a temporary breakdown in the core promise of a smart speaker.
Reports span old and new devices
Early user posts do not point to one specific model as the only one affected. Reports mention a mix of older units and recently purchased Google Home speakers, which makes the disruption appear broader than a single-generation hardware issue.
Some users also say their Home speakers suddenly went offline without any obvious reason. That adds a second layer to the complaints, since the symptom is not only slow assistant replies but, in some cases, a loss of connectivity or service availability.
| Reported symptom | What users say | Possible impact |
|---|---|---|
| Delayed response | Replies can take about 30 seconds | Voice commands feel unusable |
| No response | The speaker times out without answering | The assistant appears stuck |
| Offline state | Some devices suddenly go offline | Control and availability are interrupted |
Signs point to a limited but real disruption
The full scale of the problem is still unclear, and there is no official confirmation yet on how many users are affected. Even so, public signals suggest activity above normal levels, with Downdetector showing reports for Google Gemini rising above baseline.
That does not prove a major outage across the entire Google Home ecosystem, but it does support the idea that something is happening behind the scenes. At this stage, the clearest evidence remains the steady stream of user complaints describing the same delayed or missing replies.
A familiar pattern for Google Home users
The timing of the disruption matters because Google Home and Nest have already faced repeated criticism over the quality of the smart speaker experience. In recent periods, the platform has drawn attention for problems that users say have made the product feel less reliable.
The r/GoogleHome community on Reddit has even developed a habit of opening dedicated complaint threads, which shows how often users turn to one another when the service acts up. Weeks ago, Gemini itself was also reported to be having issues, adding to the sense that the broader service layer has been unstable at times.
Google has previously acknowledged that the Google Home experience has worsened, which gives current complaints added weight. Against that backdrop, a morning of slow or missing replies does not look like an isolated annoyance, but part of a pattern users have been worried about for some time.
Gemini rollout keeps the focus on stability
Google has been expanding Gemini to older devices while also launching a new Google Home speaker line. That combination has placed more attention on how stable the platform remains across both legacy hardware and newer products.
There is still no confirmation that the Gemini rollout is the cause of today’s slowdown. It may be a service-side issue, a home network problem, or a mix of both, but Google has not yet explained where the fault lies.
The company has reportedly been asked for comment, and users are still waiting for a clear answer. Until then, the practical reality is simple: some Google Home owners are finding that their speakers are listening, but not responding the way they should.
