I purchased a nest wifi router on 23-Jun-2022 from store.google com under order GS-8762-4775-1541. This past week it started intermittently reducing throughput from the expect 1 Gbps to less that 2 Mbps which caused my network to repeatedly fail. I isolated the faulty component and have removed it from my home network. As it is only 6 months old it should be well within the 1 year warranty period.
How do I request a replacement unit?
Have you already spoken with support via chat or email? If not, you can reach them directly here: https://goo.gle/31i1U5t. Choosing phone is most likely your quickest way to reach them and get some help with your router. Let me know if you have any issues getting in touch with them.
As I mentioned above, I did speak to Nest support on Saturday night, 12/10/2o22 at 10 pm eastern time. the tech persons name was Angela. They did not solve my issue. However, I am absolutely sure this router which is under warranty is failing and would like it replaced. How do I get an RMA to get that done?
The Case ID [1-8137000033067], but as I mentioned above, they failed to resolve my issue.
After I was transferred to my ISP, and we determined it was not an ISP issue, I spent 3 more hours to fix it by isolating the failing component and replacing it. The network is working perfectly once removed. As the failed component is no longer in the network there is nothing I can have them look at and I am not about to put it back in and cause more issues,
So given that, just looking for an RMA to replace the 6 month old component that caused many days of network issues until it was removed,
Thanks for your help.
Thanks for the details. If you're looking into getting your Nest Wifi router replaced, you can reply to the email sent to you by the agent who was helping you so they can have it processed for you.
I wanted to follow up and see if you are still in need of any help. Please let me know if you are still having any concerns or questions from here, as I would be happy to take a closer look and assist you further.
Awesome — glad to hear that your issue is fixed. It looks like we can consider this one complete, so I will lock the thread shortly unless I can help out with anything else.