On Tue, Feb 8, 2022 at 4:05 PM Mike Hammett <nanog@ics-il.net> wrote:
Some people need a clue by four and I'm looking to build my collection of them.


Someone on Outages was nice enough to send this about someone else's thread:
https://peering.google.com/#/learn-more/faq

"Google services, including Google Public DNS, are not designed as ICMP network testing services"


you know what you COULD do though... probe it with DNS requests, and then you know, test the service being offered, and still know that 'the internet is not on fire'.

 
From: "Tom Beecher" <beecher@beecher.cc>
To: "Mike Hammett" <nanog@ics-il.net>
Cc: "NANOG" <nanog@nanog.org>
Sent: Tuesday, February 8, 2022 3:01:27 PM
Subject: Re: Authoritative Resources for Public DNS Pinging

Are there any authoritative resources from said organizations saying you shouldn't use their servers for your persistent ping destinations?

I'm not sure that an ' authoritative resource ' is really needed. It should be generally understood at this point in the internet's life that networks will block / restrict some or all ICMP traffic as they need to. 

On Tue, Feb 8, 2022 at 12:58 PM Mike Hammett <nanog@ics-il.net> wrote:
Yes, pinging public DNS servers is bad.

Googling didn't help me find anything.

Are there any authoritative resources from said organizations saying you shouldn't use their servers for your persistent ping destinations?