Every couple hours i would have a few minutes where my router would just lag out. It could happen at any time, mornings,4 am, nights etc where I am the only one using it.
This is what my ping looks like
and this is what the logs say
Cut&paste of the textual data is far more useful that "screenshots". We can't "quote" parts of a screenshot easily.
Your numbers do indeed look very high on the ping times. They should be "fractions of a second" on your local network. The kernel log, (again textual data would be more useful) does look "strange". Have you attempted to "reboot" your Almond, to see if this provides either temporary or permanent resolution to this issue?
If it helps any, you can compare your results to mine:
ping almond-ap
PING almond-ap.XXXXXXX.dyndns.org (10.77.13.79) 56(84) bytes of data.
64 bytes from almond-ap.XXXXXXX.dyndns.org (10.77.13.79): icmp_req=1 ttl=64 time=0.461 ms
64 bytes from almond-ap.XXXXXXX.dyndns.org (10.77.13.79): icmp_req=2 ttl=64 time=0.472 ms
64 bytes from almond-ap.XXXXXXX.dyndns.org (10.77.13.79): icmp_req=3 ttl=64 time=0.521 ms
64 bytes from almond-ap.XXXXXXX.dyndns.org (10.77.13.79): icmp_req=4 ttl=64 time=0.466 ms
64 bytes from almond-ap.XXXXXXX.dyndns.org (10.77.13.79): icmp_req=5 ttl=64 time=0.505 ms
64 bytes from almond-ap.XXXXXXX.dyndns.org (10.77.13.79): icmp_req=6 ttl=64 time=0.480 ms
--- almond-ap.XXXXXXX.dyndns.org ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 0.461/0.484/0.521/0.025 ms
What version of the Firmware are you using? (Check the Status screen on the touch screen)
My output looks a little different from yours, as I am using a Linux machine for my "ping test". My Almond is configured as an "Access Point" so it lives at 19.77.13.79, (its DHCP IIP address as issued by my main router).
We should have a new Firmware soon, so this might get solved upon installing the next Firmware if a simple "reboot of the Almond" doesn't solve this issue, temporarily or otherwise. Please try this, and report the results back to this message thread.
Have you tried swapping out the cables, to ensure this isn't caused by a bad network cable?