5

WHAT HAVE YOU DONE!? Insane packet loss.

Tried on the same computer, and 2 different (but identical) computers (All Macbook Pro Intel)... same window of time...  

 

Its not my Fiber connection, and its not my ISP., or my any of my other routers...but look'ie what EERO does:

 

(NO, Eero tech people, I'm not your test engineer, I'm your customer, figure your own shit out)

 

After the latest (6.6.0) update--

 

EERO-6 vs. My ISP's (AT&T)'s WIFI provided modem:

 

MacBookH ➜   ping 8.8.4.4   <--- EERO 6 Pro

64 bytes from 1.1.1.1: icmp_seq=158 ttl=54 time=14.992 ms
Request timeout for icmp_seq 159
64 bytes from 1.1.1.1: icmp_seq=160 ttl=54 time=16.959 ms
64 bytes from 1.1.1.1: icmp_seq=161 ttl=54 time=33.592 ms
64 bytes from 1.1.1.1: icmp_seq=162 ttl=54 time=180.074 ms
64 bytes from 1.1.1.1: icmp_seq=163 ttl=54 time=196.682 ms
64 bytes from 1.1.1.1: icmp_seq=164 ttl=54 time=199.880 ms
64 bytes from 1.1.1.1: icmp_seq=165 ttl=54 time=226.821 ms
Request timeout for icmp_seq 166
Request timeout for icmp_seq 167
Request timeout for icmp_seq 168
Request timeout for icmp_seq 169
Request timeout for icmp_seq 170
Request timeout for icmp_seq 171
Request timeout for icmp_seq 172
Request timeout for icmp_seq 173
Request timeout for icmp_seq 174
Request timeout for icmp_seq 175
Request timeout for icmp_seq 176
Request timeout for icmp_seq 177
Request timeout for icmp_seq 178
64 bytes from 1.1.1.1: icmp_seq=179 ttl=54 time=15.916 ms
64 bytes from 1.1.1.1: icmp_seq=180 ttl=54 time=44.537 ms
Request timeout for icmp_seq 181
64 bytes from 1.1.1.1: icmp_seq=182 ttl=54 time=14.510 ms
64 bytes from 1.1.1.1: icmp_seq=183 ttl=54 time=20.719 ms

 

AT&T's provided wifi modem:

MacBookH ➜   ping 8.8.4.4  <-- CHEAP AT&T Wifi 
PING 8.8.4.4 (8.8.4.4): 56 data bytes
64 bytes from 8.8.4.4: icmp_seq=0 ttl=58 time=14.521 ms
64 bytes from 8.8.4.4: icmp_seq=1 ttl=58 time=15.761 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=58 time=15.923 ms
64 bytes from 8.8.4.4: icmp_seq=3 ttl=58 time=28.138 ms
64 bytes from 8.8.4.4: icmp_seq=4 ttl=58 time=12.035 ms
64 bytes from 8.8.4.4: icmp_seq=5 ttl=58 time=17.005 ms
64 bytes from 8.8.4.4: icmp_seq=6 ttl=58 time=18.071 ms
64 bytes from 8.8.4.4: icmp_seq=7 ttl=58 time=13.159 ms
64 bytes from 8.8.4.4: icmp_seq=8 ttl=58 time=16.233 ms
64 bytes from 8.8.4.4: icmp_seq=9 ttl=58 time=14.217 ms
64 bytes from 8.8.4.4: icmp_seq=10 ttl=58 time=16.452 ms
64 bytes from 8.8.4.4: icmp_seq=11 ttl=58 time=16.151 ms

55replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • 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

    Like
  • 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!

    Like
  • What's crazier is that I'm connected to the router via wired Ethernet and I still get the lost packages. 

    The router itself is also connected via Ethernet to the main one. 

    This makes no sense at all. 

    Like
      • AFA23
      • AFA23
      • 1 mth ago
      • Reported - view

      Jorgeit I also experienced this. Hardwired to my modem = zero problem. Hardwired to the gateway eero = massive packet loss occurring at the same intervals every minute. It is 100% an eero problem.

      Like
  • I’m experiencing the EXACT issue as other EERO owners have reported.

     

    My setup:

    - All EEROs (6) are WIRED to one 24 Port TP-LINK TL-SG1024DE Switch

    - Utility Room EERO = Gateway EERO

    - All other EEROs are basically Wired Access Points

    - Modem Plugged into EERO Gateway

     

    Things I have tested:

    - Ping EERO Gateway using wired MacBook connected via 1GB switch (no packet loss)

    - Ping Modem using wired MacBook connected via 1GB switch (no packet loss)

    - Ping Modem using wired MacBook connected directly to EERO Gateway (no packet loss)

    - Ping other EEROs using wired MacBook connected directly to EERO Gateway (no packet loss)

     

    - Ping 1.1.1.1 using wired MacBook connected via 1GB switch (packet loss)

    - Ping 1.1.1.1 using MacBook connected wirelessly (packet loss)

    - Ping 1.1.1.1 using wired MacBook connected directly to EERO Gateway (packet loss)

    - Ping 1.1.1.1 using wired MacBook connected directly to Modem (no packet loss)

    - Ping 1.1.1.1 using iPad connected directly to an iPhone 14 Pro Max Hot Spot (no packet loss)

     

    - Ping 8.8.8.8 using wired MacBook connected via 1GB switch (packet loss)

    - Ping 8.8.8.8 using MacBook connected wirelessly (packet loss)

    - Ping 8.8.8.8 using wired MacBook connected directly to EERO Gateway (packet loss)

    - Ping 8.8.8.8 using wired MacBook connected directly to Modem (no packet loss)

    - Ping 8.8.8.8 using iPad connected directly to an iPhone 14 Pro Max Hot Spot (no packet loss)

     

    Settings things I have tried:

    - Turning UPnP on/off (no improvement)

    - Turning IPv6 on/off (no improvement)

    - Turning Backup Internet on/off (no improvement)

    - Turning Guest Network on/off (no improvement)

     

    Hardware things I have tried:

    - Tried Swapping Modem. CM700 for another CM700. (no improvement)

    - Upgraded Mode from CM700 to CM2000 (no improvement)

    - Removing Access Points Temporarily - Power (some improvement)

    - Removing/Readding Access Points - Network Config/App Wise (some improvement)

    - Forcing the Access Points to be Repeaters - Unplugging Wired Back Bone Connection (no improvement)

     

    So far the only that seems to help is if I remove all the access point EEROs from my network, leaving only a single gateway EERO.

     

    Packet loss STILL occurs when using the one gateway EERO, but the latency is better (closer to 20 MS vs. ~70 MS with all EEROs connected). Problem is I’m trying to cover 6000 square feet…

     

    Personally, it sounds like EERO has a MAJOR hardware or firmware problem on theirhands and these things should be recalled.

     

    I had used Google WiFi previously for years and never had any problems. I only "upgraded" to EERO because I wasn't happy with the Google WiFi app. Little did I know I was going to spend $1,000 just to buy a bigger problem! :(

    Like
    • NMS_SALON  my ping is 9 to 10 when you buy something I don’t expect to spend hours trying to get it working eero is the worst router you could have

      Like
  • 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!

    Like 1
  • 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.

    Like
  • 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

    Like
Like5 Follow
  • 5 Likes
  • 4 wk agoLast active
  • 55Replies
  • 1502Views
  • 30 Following

Need Help? We're here for you!

We're big on support, and we want to make sure you always have the best eero experience possible. Here are several resources you can use if you ever need our help!


Quick links

Community Guidelines

Help Center

Contact eero support

@eerosupport

eero.com