I am two weeks in with an alternative and counting. Not once have I seen the issue.

Eero support went dark on this a week or so ago, which is discouraging. I want to like the product and the company, but it is hard not to share my experience widely. I feel like I should warn people, as these are very expensive devices and too heavy to function as a boat anchor.

Curious about a couple of things for those having this problem:

1. Are you using Gen1 or Gen2? I am all Gen1. Wondering if there's a correlation.

2. Wired or wireless backhaul? I have had trouble with both.

3. Bridge mode or router mode? I am all bridge mode - one of my troubled sites uses PPPoE and the other has quite a few port forwards.

An update, but no news.

Eero followed up with me. The person on the case (I assume it has been escalated because the other guy, Adam, was great and cared a lot) had read through all the notes and had a handle on the issue. But he is starting over in thinking about it.

So I turned the eeros back on and took the competitor (which was working perfectly) out of service. I experienced the issue within a few hours. I shared the info with eero. I think what they want to do is correlate my experience with anything they find in their logs.

But I also put together a little script I run in the background. It logs mac network info (via the airport executable) every minute or so. If it is unable to retrieve an http request (I have it pointed to a site on my LAN that loads very fast), it logs the same Mac wifi info constantly while it is not working.

I am no Python programmer (this is actually my first script), but it seems to work. And I am also not a wifi expert, so I do not know if the information is informative..

Here is the git repo if anyone cares to gather the same info and knows what to do with it.

Of course I would most like to hear if anyone knows what this is and how to solve it, besides buy a replacement. I am trying to preserve my six eero investment.

Thanks in advance.

Jeff C. I have a brand new MBP 13 inch with Touchbar.  Every time I turn it off or close the lid (sleep mode) and restart, I can't connect to internet.  I have to run wireless diagnostics and it does something and then I'm magically connected again.  On diagnostic tool, everytime wi-fi, wi-fi settings, and network are green.  ISP, Internet, and Server are Red.  After I run wireless diagnostics everything turns green and then I'm connected again.  Tried with older MBP and it works fine everytime.  So...new MBP something is going on.  Maybe the network card, maybe the network configuration, I don't know, but hopefully eero support can figure it out.  

Honestly, there have been so many posts on reddit and other sites complaining of this MBP issue, while nobody seems to ever report anything similar with non-MBPs anymore, that it seems crazy to not consider this a known issue.

I've been having this issue since I first got eero. Turning the wifi on/off works 100% of the time. The eero support people basically told me there was nothing they could do and that it had to be a Mac problem, even though that makes no sense at this point. They worked with me for a while before giving up. I've spent so many hours trying to fix it that I finally just gave up too. I spent so much on eero, and it works reasonably well with my other devices, that I decided it wasn't worth replacing eero with a competitor's product.

I have a MBP 15" w/ TB. It is a little better than when I first got it (it was debilitating at first, occurring hourly or more, but now happens maybe 1-2x/week). I've never had anything like this happen on any other network.

Interestingly, it used to happen even when eero was hardwired to my MBP (using a USB ethernet dongle), but that issue disappeared with one of the eero updates. The wifi issue remains.

I occasionally get a dead connection on my iPhone that requires that I turn the wifi on/off and then it works again. That only happens once every few weeks though, so may be an unrelated issue.

I've basically just decided that I'll use my MBP hard-wired when I am at home to avoid this issue that is almost certainly an eero issue. When I'm ready to upgrade in the future I might go non-eero to avoid this issue unless they finally discover what is causing this problem, even if it is one that doesn't affect enough of their customers for them to work on it anymore.