Hi. We've used Google Wi-Fi (not Nest) for years. Until recently, our hardwired Gig Ethernet network has worked great. Our fiber Internet service offers 750mbps down / 200 up and we consistently see that or better at the router (Google Wi-Fi puck) via the home app (see pic) and all our hardwired devices have as well until recently.
Just recently (the past week or two), I've started noticing that devices -- whether they're hardwired or on Wi-Fi -- never get above 100mbps. My high-end gaming PC, with dual GB Ethernet, gets up and down in the 90s on Google's speed test in Chrome:
I've restarted the network and get the same bandwidth throttling at our devices, but everything is fast at the router. Any idea what might be going on?
hey. I've just noticed the same thing. I have Google Wifi (not nest) sitting behind an AT&T modem with the wifi turned off. All the Google stuff is hard wired together via a 1000mbs switch.
I'm getting 999mbs down and 898mbs up from the AT&T box, but then nothing on my network can exceed 100mbs.
My brand new MacBook M1 Pro is only getting 91mbs down and 71mbs up.
If I make it a priority device on the network, then I can increase that to 349mbs down and 340mbs up.
Sorry about the speed limitations you're seeing on your mesh networks. That's frustrating to deal with, I'm sure. When speeds are lower than expected, there can be a lot of different reasons for seeing that. We have a help article that runs through many things you can look at. That article is found here: https://bit.ly/3GESP9p.
In addition to the article, there are a couple of other things you can test to see how it impacts things. Try running a speed test and note the results. After the test, prioritize a device on your network and run it again. If you are seeing a different result that's dramatically higher or lower, let me know. In addition to the device prioritization, you can try disabling or setting preferred activities in the Home app to see how it impacts things as well.
Give the article a look and see if anything there might apply to your situation. If you're still having issues, let me know here.
Hi, Jeff. I've already done literally everything you mention -- restarted the network, disabled preferred activities, prioritized and deprioritized devices, etc. -- and nothing makes a difference. I never had this problem with my old Google (Asus) Onhub router, but since you've EOL'ed those, I had to replace it with a Google Wi-Fi puck. Could this be related to that?
My setup is like this:
WAN (Altafiber) <--> Altafiber router (in pass-thru mode) <--> Google Wi-Fi router <--> two Google Wi-Fi APs (both hardwired), all 100% Gigabit networking and unmanaged Gbit switches
This morning, I managed to see 240mbps down via Wi-Fi, but my hardwired devices are all still maxing out at <100mbps.
If you have already tried the suggestions listed here and are still seeing random results or poor results, it might be a good idea to get in touch with support directly. They can diagnose your setup while you are on a live chat or phone call with them and they'll be able to give you some insight into what is going on there. If you've already worked with support and find yourself in the same spot, let me know here.
Well, I don't know what to make of this, but I apparently fixed it.
I started at my PC's connection and, using a laptop, verified that I was getting 75-92 Mbps down all the way back (plugging the laptop in at each switch and jack along the tree) to the G Wi-Fi puck router.
I then disconnected the LAN connection on the G Wi-Fi puck router so I could connect the laptop directly to it. I then got expected (good) speeds: 400-600 Mbps down! So I then reconnected the router to the LAN and rechecked every switch and connection back down to my office where my PC is and got great speeds all the way there. I then retested on the PC and -- lo and behold -- 400-600 Mbps down. It seems that forcing the router to renegotiate a LAN connection (or something...IANANE) seems to have fixed it...I didn't even restart the router during all this. Go figure. Anyway, I'm still not entirely sure what the issue was, but it's working as it should now. Thanks.
Wow, that's quite a process, cfOH, but I'm happy to hear it worked! Before marking this as resolved, let's watch it for a few days and make sure things stay stable for you with time. I do appreciate you sharing the steps you took, that's really helpful for the community to see.
If you have any other questions, just let me know!