Nest WiFi Pro wired connection is about 10% of what it was on Nest WiFi

[junton]

So, my WiFi Pro arrived today and I was really excited to get it setup. I set everything up using the Google Home app and downloaded the updates. I have a fiber gigabit connection from my provider and their most recent modem. My wired connections are pegged to about 90Mbps. My Nest WiFi (non Pro) was getting 900+Mbps wired.

My troubleshooting has been the following:

• Restart the Nest WiFi Pro network
• Restart the modem
• Restart all switches
• Reboot the hard wired computers

My Nest WiFi Pro is in DHCP WAN mode and connected directly to the 10Gbps ethernet port on my modem. I am using a mix of CAT 5 and CAT 6 cabling and my switches are all gigabit or higher.

Plugging the old Nest WiFi (non Pro) back in yields 900+Mbps on wired connections.

I think something is wrong

[junton]

This was my issue exactly. I'm on Verizon FiOS using the newest router with the Nest WiFi plugged into the 10Gbps port on the modem. Nest WiFi gets ~900Mbps. Nest WiFi Pro seemed to be capped at 90Mbps. It wasn't worth the headache to keep messing around with them, so I returned them this last weekend.

[Jhonleanmel]

Hey everyone,

Thanks for posting — let's see what's going on. 

Are you using a modem/router combo from your Internet Service Provider (ISP)? How many devices are dropping from the network? Also, do you have any paused devices? 

Give these steps a try:

1. If you're using a modem/router combo, set that to bridge mode to avoid double NAT issues.
2. Make sure that there is minimal to no interference (concrete, bulletproof glass, metal, mirror, etc.) and the points are no more than two rooms apart.
3. Remove any special characters in your network name and password.
4. Turn off IPv6.
5. Change your DNS server into 8.8.8.8 on the primary and 8.8.4.4 on the secondary server. Hit the save/ floppy disk icon on the upper right.
6. Unplug the power from your Google Wifi devices for 2 minutes.
7. If the issue persists, try factory resetting your network.

Let us know how it goes.

Best,

Mel

[Peter-maude]

Many of us have done this, and been walked through support on this, it does not help.  I think it would help to escalate this, as a product failure, rather than sending people on these On and Off again fruitless tasks 

[junton]

1. If you're using a modem/router combo, set that to bridge mode to avoid double NAT issues. - This didn't help. Additionally, the Nest WiFi (non Pro) works flawlessly when swapping back with no additional changes.
2. Make sure that there is minimal to no interference (concrete, bulletproof glass, metal, mirror, etc.) and the points are no more than two rooms apart. - These are wired points. I am not even looking at the WiFi speeds. Just wired computers to the points and main hub.
3. Remove any special characters in your network name and password. - Removing special characters from your password affects wired network speeds now?
4. Turn off IPv6. - It was not on to begin with.
5. Change your DNS server into 8.8.8.8 on the primary and 8.8.4.4 on the secondary server. Hit the save/ floppy disk icon on the upper right. - When set to automatic (the out of the box setting) DNS is automatically set to Google DNS.
6. Unplug the power from your Google Wifi devices for 2 minutes. - Reset these, factory reset these. No change.
7. If the issue persists, try factory resetting your network. - Did this. Didn't work. There is something wrong with these devices.

Swapping back to the Nest WiFi routers with no additional configuration changes provides desired results. These devices either have bad firmware, a setting we cannot access, or a problem with the hardware itself. We've wasted so much time with these. Just read through this thread to see what everyone's been through. I don't even know if I would give these a second try.

[LanceM]

Something I've been doing for troubleshooting is I unplugged my previous Google Nest (non-pro) and Google Wifi points (I did NOT do a factory reset).  Then when I went through adding the new Nest Pro, I added it to a new Home in the Google Home app (so I could use the same wifi network name).  That way I can more easily switch back without having to re-setup all my port forwards and settings.

[G-Mo]

nope, did all those steps when I spoke with Google support, none of it worked.

[krroller]

1. Nest Wifi Pro Router direct connected to Frontier Fiber ONT.  The ONT is 3 months old and is the latest version.   

2. There is no physical interference and the two points use a wired backhaul.

3. I do have one special character in the SSID password which is "." (a period or dot) but not the SSID itself.  I'm not going to change this because it would involve changing over 80 home automation devices including Google cameras, doorbells, nest protects, nest hubs, nest speakers, chromecasts, Wemo light switches, etc.  None of these can be bulk changed and it's far less effort to simply return the Nest Wifi and replace it with another system that does not have the bugs Nest Wifi Pro is showing.  Further take note that the system was working fine with Nest Wifi.   In addition, removing a special character would weaken the password strength.

4. IPv6 has been disabled since original configuration, but I did try enabling it to see if that would help, which it did not.

5. DNS has been updated to use the Google servers.   I've turned this on and off and the DNS settings seem to have no impact on the issues.

6.  Router/points/ONT/switches have been power cycled countless times since installation for a time period of between 2-5 minutes. 

7.   Rather than do another factory reset, it's faster to get a working system by returning the Nest Wifi Pro and replacing with an alternate system.

Certainly it seems there is a bug in the firmware to be impacting so many users with the same set of issues where continuous factory resets and power cycling simply cannot be the resolution.

[LanceM]

It is odd that I recall these kind of ONT issues (and also the "port forwarding doesn't work when connected to LAN network") with the Google Wifis came out...

[Peter-maude]

Remove any special characters in your network name and password.

This is the most frustrating suggestion, asking people to wreck their home setups, and arguably lower the security bar, by making passwords simpler.  When it has been explained authentication is fine, but speed is slow, is not a good idea.

[WarpedTrekker]

Those steps will not make a difference. Changing dns  and removing special characters from password.lol and ipv6 is frowned upon for disabling. It's 2022 and all windows OS rely on ipv6 internally for routing. It should never be unbound in windows nor on the router.

I'm in usa with ATT fiber 1Gb with Bgw320. No ppoe. In the bgw320 got it set properly like always to Pass thru and gave the Nest Pro main point a static ip. Devices are not routed properly to wifi 6ghz channel. On my laptop I have Killer Intel wifi app installed and it is showing the 6Ghz channel as poor quality unless I'm right next to it. Most of my devices don't even connect to 5ghz and go directly to 2.4ghz. So something is definitely wrong with Nest wifi Pro. My Nest Wifi old ones, everything worked fine with faster speeds. Google if you are listening, roll out a firmware update asap. 

[NerdJolt]

Factory reset, no router in between the ONC and the Google Wifi Pro. Factory reset, updates the DNS with no improvement. This is a firmware/device issue. Not a line issue, cable issue or ONC issue my previous custom Asus router works flawlessly at the correct speeds from the ISP. Please escalate if you can.

[mustafa_rabbi]

done all that and the issue still exists. this needs to be fixed asap 

[Jeff]

Hi everyone, 

Thanks for flagging reduced internet speeds on Nest Wifi Pro routers. The issue appears to be affecting a small number of users. We've let the right folks know, and they're working to roll out a fix. 

If you're also experiencing this behavior, feel free to add your report in the comments below and stay tuned to this community thread for updates.

[krroller]

This is not a UK only issue.  I'm in Dallas, Texas and having similar issues that have been reported within this forum.  I have reported the issues here, but also through google support with an open case, and via Twitter #madebygoogle

I just swapped the cables from the Nest Wifi Pro back to my Nest Wifi and all is working normal using the same cables, switches and app settings.  Certainly seems like a hardware or firmware issue and it's not exclusive to the UK.

[perrypetrie]

Having this issue in Canada as well. Definitely not just a UK issue..

[dgene84]

Jeff, this is NOT singled out to just the UK. There are many people who have very cleary indicated where they are from and there is a LARGE group of people in the US> I am in Houston, TX with this issue. 

[Tonycdh]

Definitely not "concentrated" in the UK.  Illinois here.  The responses are not mainly from the UK, they are all over.  Lets not let google concentrate on one area, they need to concentrate on the product as a whole. 

[mustafa_rabbi]

The issue is persistent in other countries as well, not only UK. Facing this issue from Bangladesh. Got the system preordered from US.

[Peter-maude]

Can you explain how you know the number of affected users are small , vs unreported , or because many are connecting via an ISP hub as opposed to direct to the ONT.

I expect this to be broken for anyone with FTTP connecting the device to the ONT

[junton]

I'm in Massachusetts, USA.

[Oli3]

I'm in Canada and have the exact same issue. 

Nest wifi runs twice as fast in my gigabit connection. Nest wifi pro immediately at half the speed. 

This was a very expensive upgrade and not the results I expected. 

[GDog9]

Same here. Very poor speeds.

[deanhtid99]

Hi Jeff. I don’t believe this is a UK issue. It’s a PPPoE issue. Something is capping the speed at 50MB. It’s been a few days now. Surely Google are close to a fix? I suspect most people will be sending it back soon if not already. 

[jcbjulio]

I'm having the same problem here in Brazil. Nest Wifi Pro connected through PPPOE, with speed capped at 50MB (600MB with the non-pro)

[DmitryP]

What?! No! Can't be! This is a UK-only issue according to Google... 🤣

[SpottedQuoll]

Hey @Jeff , are you doing that thing again where you minimise the problem in a reply that you mark yourself as the "accepted answer"?  Naughty boy, and a bit of a recidivist.  I didn't know you worked for the marketing department.

[Mike30]

Not sure how this forum works or the role that you play? Do you work for Google?

The 'answer' isn't a complete answer clearly, as you can see in this thread, the issue with the Nest WiFi pro extends well beyond the shores of the UK. In fact, it looks much more likely that PPPoE connections are the culprit generally. 

[sliyk]

Jeff, why have you marked this thread as solved? It is not solved and what you have given is not the answer.

[Antonios]

Same issue here. Everything worked fine with nest wifi but less than half the speed now with nest wifi pro.

Are you sure it's affecting a small number of users? How did you measure that?

[camnickles]

“Upgraded” to Nest WiFi Pro from Nest WiFi & I’m getting half of what I was getting. I’m subscribed to 1 Gig through Spectrum. I used to test about 750mbps (which I was fine with), but now I’m getting 400mbps at best. Upload speeds are exactly the same though, so I’m hoping for a firmware update or I’ll be going back to the regular Nest WiFi.

[Anonymous]

“A small number of users”….

You’re a clown and you should be ashamed of trying to make this look like an isolated event. 

[iansray]

Same issues in Charlotte NC. I have fiber from a local company and had the google nest wifi running at 998 mbps now it tops out at 90 mbps with this new pro. I bought three of them to create a mesh network. I’ve been on the phone and troubleshooting for two weeks now. I’m sending it back before I am out of the 30 day warranty. 

[JKH5199]

This is not a UK only issue. I’m in Ohio and have the same issue. I’ve already opened a ticket for it. Was told I would hear something within 48 hours. It’s now 72 hours and not a peep. Might be time to return it. 

[Mike30]

I have my RMA pickup scheduled for Friday. This is the end for me, no Comms from Google is really poor

[TrunStrat]

Me too. BT 900 FTTP and my speeds are down to around 200 from 900+ on my old google mesh router. 

[rheironimus]

Hi,

I just swapped my old Nest Wifi router and points with the new Nest Wifi Pro units. My download speeds are 10% of what they used to be (Cox cable gigablast). Was getting 900 Mbps and now getting 90Mbps. Have restarted everything multiple times. Any ideas?

[junton]

We've got a thread over here: https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-WiFi-Pro-wired-connection-is-about-10-of-what-...

[Tonycdh]

Same issue here. Was getting 600mb on old nest, now getting 300 on pro. Very sad

[Jhonleanmel]

Hey folks,

Thanks for posting — let's see what's going on. 

Are you using a modem/router combo from your Internet Service Provider (ISP)? How many devices are dropping from the network? Also, do you have any paused devices? 

Give these steps a try:

1. If you're using a modem/router combo, set that to bridge mode to avoid double NAT issues.
2. Make sure that there is minimal to no interference (concrete, bulletproof glass, metal, mirror, etc.) and the points are no more than two rooms apart.
3. Remove any special characters in your network name and password.
4. Turn off IPv6.
5. Change your DNS server into 8.8.8.8 on the primary and 8.8.4.4 on the secondary server. Hit the save/ floppy disk icon on the upper right.
6. Unplug the power from your Google Wifi devices for 2 minutes.
7. If the issue persists, try factory resetting your network.

Let us know how it goes.

Best,

Mel

[Peter-maude]

none of this worked.  google support walked me through all the common steps listed above.  There are simply too many people ALL having the same issues, and have the old model to compare with, for this to be localised.  Something is wrong with the firmware or hardware in the new model.