All of these symptoms are indicative of a Hubitat Hub that is no longer connected to the Hubitat cloud. Have you tried simply rebooting the Hubitat hub from its Settings menu? Have there been any recent changes to your home network configuration that might be blocking the HE hub from reaching the Hubitat Cloud Servers?
Networking is never straightforward and without a terminal access with a full suite of tools it is that much harder to debug. It's entirely possible that the hub had cached the resolved IP of some failed over aws host which cleared out after some timeout. FWIW, the public IP I had tried pinging was 8.8.8.8 . But the system is so opaque that it's nearly impossible to debug and the absence of any logging for this makes it that much harder to understand what's going on
In any case, thanks for the pointer to the (well hidden) ping tool. I was about to roll out a custom app to run pings.
FWIW, there are some serious issues with the whole remote admin setup. my.hubitat.com was showing some random hub as a registered hub with me and I could access the remote admin page of it; most likely a hub I had returned at some point