Gateway monitor down
-
It's certainly much larger than I would expect. Rttsd values are usually and order or mangnitune less than the actuall RTT time. Like:
Name Monitor Source Delay StdDev Loss Status Substatus BT_DHCP6 fe80::2621:24ff:fed9:623f%pppoe1 fe80::fad1:11ff:fec1:5b57%pppoe1 2.566ms 0.282ms 0.0% online none PROTONVPN_VPNV4 10.24.0.1 10.24.0.9 227.778ms 60.327ms 0.0% online delay WAN2 8.8.4.4 xx.xxx.xxx.xxx 3.243ms 0.337ms 0.0% online none WAN_PPPOE 8.8.8.8 yy.yyy.yyy.yy 6.194ms 0.132ms 0.0% online none
Are you actually seeing ping spikes to 8.8.4.4?
Steve
-
Right now, I do. But that's probably because there was a recent submarine cable cut in SEA that our ISP is using. The latency problem, however, started happening way before that submarine cable cut issue. I tried using the mtr package and I see the same spikes after 100 pings to each hop.
-
Might just be how your link behaves then.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.