Perhaps the vague "Stability and performance improvements" release last night resolves this. I wish they included more info in the release notes.

Latency issues?  I had it something terrible!  Disabling IPv6 fixed it all.  Eero needs to address this ASAP.  Do not blame ISP, their router, etc.  

Add me to the list of people having random drops on the home Eero network on Mac devices. I'm fine because I'm hard wired to the router, but same issue as reported by others: All lights on all Eeros never report any disruption or change color, but Macbook will randomly disassociate with the network, sometimes multiple times a day.

Same here.  Joined up because of this very issue--dropping packets, I have to sometimes turn wifi off on my device and back on, etc.  It's a mess. 

 

I have the 3x Pro 6 setup and am never more than a few feet from a wired/backhauled Eero Pro 6 and can drop packets when pinging my Fios router.

 

Also, my Sonos speakers hate this and disconnect quite frequently.

 

This exact setup was stable for over a year up until sometime for me in the past 2 weeks.

Created an account just to find some kind of help here, because multiple months of going back and forth with eero support has given me the impression that they are designed solely to deflect and run people around in circles until they give up out of sheer frustration. 

The issue is pictured in images I attached: I have been getting huge packet loss/latency spikes that happen at literally the exact same time every single minute in perpetuity. It causes issues with our baby monitor, it disconnects streaming video, it breaks up video calls, it makes online games unplayable, etc. I have literally sat at my desk with a stopwatch and been able to perfectly time the two spikes I know are coming; 50 seconds of acceptable (though wildly jittery) ping, massive spike, 10 seconds, massive spike, repeat. 

I have sent the below images (and many more of different tests that show the same thing happening under various different conditions) to eero support at various points in what is now a months-long back-and-forth with them. Four different people have given me increasingly pointless checklists to try and get me to give up and go away "troubleshoot the issue" and attempt to isolate what the problem is. Given the nature of the 'troubleshooting' so far - "are you sure the ethernet cord is plugged in to the right port?" "are you sure you're using the right type of cord?" "did you reset your network (at any point in the past two months)?" "can you run another ping test?" - I do not get the impression that they have any idea what is going on or that they care at all. 

I'm now at the point where they've apparently run of out busywork to give me, so someone has been "trying to schedule a phone call with me"...for 8 days. Hilarious. Really hope I can find some kind of guidance/solution in here, because at this point I'm concerned that there is no fix at all, eero knows this and doesn't care, and my best bet is to throw these things in the trash and buy something else. 

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!