WHAT HAVE YOU DONE!? Insane packet loss.

Hey folks,

I'm experiencing high latency to my Eero Pro 6. I think it started after the 6.12 update. I'm still having it with the 6.13 update too.

% ping eero-basement

PING eero-basement (192.168.69.69): 56 data bytes

64 bytes from 192.168.69.69: icmp_seq=0 ttl=64 time=2.677 ms

64 bytes from 192.168.69.69: icmp_seq=1 ttl=64 time=8.979 ms

64 bytes from 192.168.69.69: icmp_seq=2 ttl=64 time=17.680 ms

64 bytes from 192.168.69.69: icmp_seq=3 ttl=64 time=25.743 ms

64 bytes from 192.168.69.69: icmp_seq=4 ttl=64 time=67.556 ms

64 bytes from 192.168.69.69: icmp_seq=5 ttl=64 time=114.621 ms

64 bytes from 192.168.69.69: icmp_seq=6 ttl=64 time=2.899 ms

64 bytes from 192.168.69.69: icmp_seq=7 ttl=64 time=2.903 ms

64 bytes from 192.168.69.69: icmp_seq=8 ttl=64 time=3.322 ms

64 bytes from 192.168.69.69: icmp_seq=9 ttl=64 time=3.203 ms

64 bytes from 192.168.69.69: icmp_seq=15 ttl=64 time=31.071 ms

64 bytes from 192.168.69.69: icmp_seq=16 ttl=64 time=79.491 ms

64 bytes from 192.168.69.69: icmp_seq=17 ttl=64 time=124.073 ms

64 bytes from 192.168.69.69: icmp_seq=18 ttl=64 time=166.852 ms

64 bytes from 192.168.69.69: icmp_seq=19 ttl=64 time=244.340 ms

64 bytes from 192.168.69.69: icmp_seq=20 ttl=64 time=19.859 ms

64 bytes from 192.168.69.69: icmp_seq=21 ttl=64 time=3.065 ms

64 bytes from 192.168.69.69: icmp_seq=22 ttl=64 time=14.491 ms

64 bytes from 192.168.69.69: icmp_seq=23 ttl=64 time=62.967 ms

64 bytes from 192.168.69.69: icmp_seq=24 ttl=64 time=105.650 ms

64 bytes from 192.168.69.69: icmp_seq=25 ttl=64 time=148.112 ms

64 bytes from 192.168.69.69: icmp_seq=26 ttl=64 time=191.646 ms

64 bytes from 192.168.69.69: icmp_seq=27 ttl=64 time=234.922 ms

64 bytes from 192.168.69.69: icmp_seq=28 ttl=64 time=277.915 ms

64 bytes from 192.168.69.69: icmp_seq=29 ttl=64 time=321.076 ms

64 bytes from 192.168.69.69: icmp_seq=30 ttl=64 time=2.964 ms

^C

--- eero-basement ping statistics ---

37 packets transmitted, 37 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 2.677/68.928/321.076/87.179 ms

Joe

I also have this issue.  It's insanely annoying.

I have 3 6+ eero's the gateway connected to my modem, another in the hall which has a cat 7 cable running to the 3rd in my garden office.

It sometimes works fine for a few hours and then I get loads of packet loss.  A network restart fixes it briefly sometimes.

The issue I believe is the mesh connection between the gateway and the eero in the hall.  From the garden office I can ping the hall eero with no problems, but pinging the gateway eero results in massive packet loss.

Devices connected to the gateway eero are fine.  Just anything wifi or hardwired to the hall eero is not working properly.

The gateway and hall eero are no more that 10m apart with at worst an internal wall between them.

I have until 31 Jan to return these hopeless devices, but may just sent them back now!

EERO support is useless. EERO needs to recall these units. There is definitely a problem.

In the last 48 hours I have tried:

1. Swapping two different EEROs and trying to use them as gateways (no improvement)
    
2. Adding/removing all the EEROs and re-adding them to the network (no improvement)
    
3. Unplug all the EEROs and rebuild the network using Google WiFi (<12 Hours in, but so far, no reported issues)

I ran a ping test (1000 total pings) of 1.1.1.1 and 8.8.8.8 on the Google WiFi from 4 iPads on WIFI - and ZERO packet loss. The EERO is absolutely the problem.

Previously, even if hard lined into the EERO gateway, I'd get packet loss between ~ 7 -10%. If I was EERO, I'd be embarrassed right about now.

EERO - RECALL THESES! GIVE US OUR MONEY BACK.

ADMIT YOU HAVE A PROBLEM.

STOP HIDING!

I have given up with the eero's and returned them. 

Support were unable to resolve the issue after blaming everything from my cat7 cable, a dumb unmanaged netgear switch, etc etc.  They said the issue was I had a loop in my network.  Which I proved wasn't the case or if there was it was caused by the eero's. 

I've just installed 3 Linksys Velop's which were given to me.  They are working perfectly with exactly the same setup, placement and devices connected as the eero's.

Having the same issue as well but on eero 6+. Upgraded from eero released 3 years ago and never experienced this. Wi-Fi calling stopped working after upgrading to 6+ and I'm getting 1000ms ping download doing speedtest.net. eero app shows 460+Mbps running in-app speed test but on connected devices running speedtest.net shows 0.02-3Mbps. So frustrating

The workaround has remained solid since my last post.   No further issues with Teams / Zoom when leaving it on the Guest network.   
 

However, I have not taken the time to further troubleshoot what it does not like on the main network.   
 

I believe this issue is not isolated to Eero though since my in laws have an old Netgear router (non-mesh) router that was having same issue with my laptop.   

Hi Folks,

I run a small network for a church with four eero 5 Pros running in bridge mode and connected in series to each other via cable (with AP1 being directly connected to my core switch).  

I've also started noticing very high packet loss recently (I'd say about 2 weeks ago).  System has been running fine for well over 2yrs solid.  I've also noticed that I don't have that issue with the Guest Network, just the main one.  I started noticing that when clients attempt to connect, the DHCP broadcast traffic doesn't make it to my DHCP server, so even though the client connects, it reports that there is no Internet traffic.  As a quick workaround, I can change the client settings to use a static IP address and it connects fine to the eero network.  So something is wrong with the Main Network.

I decided to run an extended ping test using WinMTR over a roughly 4-hour period, and here's what I saw:

From the ping tests above, it is clear that something is up with AP2, AP3, and AP4.  I ran the same test to the core switch (SW1) and you can see virtually no packet loss (1% an issue, but not a major concern).

I was considering upgrading to eero 6 Pro, but gonna hold off for now.  If someone at eero support is watching this thread, please hit me up so we can troubleshoot.  I'm not one to quickly abandon a tech simply because issues like this arise, so let's troubleshoot please.  

I had the same issue with my eero pro 6 routers but the issue was only localized to one laptop (Windows) compared to the other (Mac). I ended up setting up the preferred band to 2.4Ghz on the Windows laptop under Wi-Fi network adaptor settings and immediately saw an improvement with no more drops other than the usual one offs. It seems in my case forcing the frequency band seemed to help. I wonder if this is the reason the issue seems to be non existent on guest network setup on eero. Maybe there is no auto switching with guest network ? Who knows.. Hope this helps anyone facing this issue.