Google mesh network needs rebooted on a daily basis to resolve horrible speed issues

[jeb5010]

I have a 3 pack of AC-1304 running 14150.43.80. I installed these in July 2019 and they have worked flawlessly until the last couple of weeks.

I have one connected directly to my fios modem, another one connected to the one operating as a router via an unmanaged switch, and a 3rd operating over the wireless mesh.

My Verizon fios service is 500/500 and I typically get closer to 600/600. This network has worked great for several years, but in the last couple of weeks it has gone to complete garbage. On a daily basis I find myself needing to restart the network because all my devices (both wired to the LAN and on the wireless) slow down to crawling speeds. Sometimes 5-6 Mbps, sometimes even below 1Mbps. If I do a speed test from the app (Google to my ISP) it always returns the expected fast speeds, so it is an issue internally on the LAN side. It happens to my iPhones, my AppleTV, my Windows PC, and every other device on the network.

As far as the app goes, it thinks all devices are online and running great. This is absolutely maddening and I'm ready to scrap the entire thing. The app is very limited and I do not see any obvious way to troubleshoot this or force a firmware update if there is one. I did find several threads from last year describing a very similar issue. Either a recent firmware update is causing this or my hardware is failing. I would greatly appreciate any advice on how to fix this.

[gertjvr]

Since the release 14150.43.80 seems all devices are throttled and you need to prioritise one device every 8 hours to get the same performance as before the recent upgrade 22/04 

[jeb5010]

Lol what an absurd bug... thanks for the recommendation though.

[Jeff]

Thanks for the input, gertjvr.

jeb5010, have you tried doing a network reset (power cycle) since the issues started happening? Sometimes when a new firmware lands, restarting the network allows everything to refresh across the mesh network. If you've already done so, let's look at other steps later. Let me know where you stand on this and we'll get it sorted out.

Thanks.

[jeb5010]

I've tried power cycling about 50 times since this started as that was the only action that temporarily resolved the issue. Thankfully setting a priority device every 8 hours also fixes it and is an easier solution, but still a terrible one.

I appreciate your reply but I can find tens if not hundreds of posts on the Internet about this issue with these APs. It is clearly a known firmware code level issue, and a platform breaking one at that. I would love if a fix released for this, but by the time that happens I will likely have replaced these with Aruba Instant On APs.

[Jeff]

I understand, jeb5010.

The device priority stuff is definitely more of a workaround than a fix. We're going to keep looking at the issue and work on that, but I fully understand why this is and has been frustrating for you.

Thanks.

[CM77]

Jeff,

I may have the same problem. I have Nest wifi router connected to a SB6190 modem and with 2 attached wifi points. Slow speeds resolved once I resolve either the router or modem. Doing just the router seems to restore the speeds. Call to Xfinity indicated no problem with cables and anything from their side. As speeds restored once router is restarted, I think I have same problem as others. The software version (per the google home app) is 14150.43.81. 

Can you please suggest what I can do so that I do not have to restart the router everytime speeds slow? Many thanks.

[gertjvr · Accepted solution]

Ended up factory resetting all my google wifi units and has resolve the issue for me

[jeb5010]

Over 24 hours after a factory reset and things seem to still be working properly... Hopefully I'm good now.

[Jeff]

Hey, jeb5010.

I'm just checking in to see if everything was still working well for you or to see if you needed any more help on this. If things are still stable, just let me know.

Thanks,

- Jeff

[jeb5010]

Yes it works fine now after the factory reset. This really should have been fixed via a firmware update though.

[Jeff]

I'm happy to hear it's working well. Sorry it was a bit of a hassle to get back to a solid performance. Before I mark this one as resolved, is there anything else you might need?

Thanks,

- Jeff

[Jeff]

Hi, everyone.
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Thanks,
- Jeff

[CM77]

Hi Jeff,

I posted back in early May with this issue and I see that factory reset is the solution here. I have not done this yet but will try to do so within next couple of days. If factory reset, do I have to re-set up everything? Thanks.

[Jeff]

Hi, CM77.

Yes, if you do a factory reset, you'll need to set up the devices as if they were new. Let me know if you run into any issues in that process and I'll be happy to help.

Thanks,

- Jeff

[Jeff]

Hey, CM77.

I'm just checking in once more to see if you ever went through with the factory reset and I wanted to see if that worked things out for you. If you still need some help, let me know.

Thanks,
- Jeff

[Jeff]

Hey, all.

It looks like we've slowed once again. We'll be closing this up unless anyone has any final input here.

Thanks,

- Jeff

[Jeff]

Hi again, jeb5010.

Just checking once more to see if you're still having good performance. Let me know if you have had any troubles.

Thanks,

- Jeff

[jeb5010]

I'm at the point where I'm going to try factory resetting my units, but how has there not been a software/firmware fix for this deployed? Looks like my software updated to 14150.43.81 but the problem still exists. This is absurd.