EHOSTUNREACH errors last night for heartbeat requests made from a Fly app

I have a small Bree app deployed to Fly that runs a job every 5 minutes and makes a heartbeat request at the end. Last night we’ve gotten heartbeat missed errors for the first time with the following errors logged in the Fly app:

FetchError: request to<HEARTBEAT_ID> 
failed reason: connect EHOSTUNREACH 2606:4700:3108::ac42:2aea:443

There’s no indication of the heartbeat endpoint experiencing downtime, so I was wondering if there’s any chance the issue had to do with networking and routing on Fly’s infrastructure.

Coincidentally (related or not I’m not sure yet) we’ve had monitor health checks alert us last night on https endpoints deployed to Fly as well with requests timing out after 10 seconds.