Ping test to Google (8.8.8.8) high failure rate today

[junglechuck]

Is anyone else experiencing many failed WAN tests when using a ping test to 8.8.8.8? I also tried Level3 at 4.2.2.1 but that also was failing. Is this a larger issue? It renders the NGFW mostly unreachable, and of course the connectivities at sites fails also. I'd appreciate it if anyone has also seen this today. I've changed the WAN failover tests to DNS tests which seems to have solved the issue.

[dashpuppy]

NO issues here, pinging googles and CloudFlares.

Tue Mar 15 2022 07:49:12 GMT-0700 (Pacific Daylight Time) - Test Started
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=6.12 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=5.68 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=5.82 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=5.82 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=5.82 ms


--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 11ms
rtt min/avg/max/mdev = 5.676/5.850/6.122/0.154 ms
Tue Mar 15 2022 07:49:17 GMT-0700 (Pacific Daylight Time) - Test Completed


--------------------------------------------------------


Tue Mar 15 2022 07:49:50 GMT-0700 (Pacific Daylight Time) - Test Started
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=61 time=2.48 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=61 time=2.74 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=61 time=2.77 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=61 time=2.87 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=61 time=2.34 ms


--- 1.1.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 11ms
rtt min/avg/max/mdev = 2.338/2.638/2.872/0.207 ms
Tue Mar 15 2022 07:49:55 GMT-0700 (Pacific Daylight Time) - Test Completed


--------------------------------------------------------

[junglechuck]

@dashpuppy & Albert90,

Thank you both for replying. It must have been coincidence with ISP issues in California and central Mexico. Google was timing out in the middle of the day Monday and then Monday afternoon evening there were issues in Mexico. Thanks again.

[dashpuppy]

@dashpuppy & Albert90,

Thank you both for replying. It must have been coincidence with ISP issues in California and central Mexico. Google was timing out in the middle of the day Monday and then Monday afternoon evening there were issues in Mexico. Thanks again.

Ditch google and use 1.1.1.1

[Spiral]

Try "PingPlotter" to find out where it is failing.