Possibly related, I’ve been noticing some DNS resolution issues on Google Cloud beginning couple of days back. I can easily replicate launching an “apt update” from my Cloud Shell: Err:1 https://apt.releases.hashicorp.com <https://apt.releases.hashicorp.com> buster InRelease Temporary failure resolving 'apt.releases.hashicorp.com <http://apt.releases.hashicorp.com> ' [...] Err:8 http://repo.mysql.com/apt/debian <http://repo.mysql.com/apt/debian> buster InRelease Temporary failure resolving ‘repo.mysql.com <http://repo.mysql.com> ' This is inconsistent though, dig for the two domains above mostly works. >From Cloud Shell I can also resolve ‘google.us <http://google.us> ’ on 156.154.128.70 which is one of the authoritative NS failing in Lukas’ query on dns.google <http://dns.google> . There is indeed something weird going on in Google’s network/DNS but I don’t think we can fully track it down from the outside. On 29 May 2021, at 13:18, Lukas Tribus via Outages <outages@outages.org <mailto:outages@outages.org> > wrote: SERVFAIL resolving google.us <http://google.us> at 8.8.4.4 from different vantage points in Italy, Austria and Switzerland, (900 seconds intervall): https://atlas.ripe.net/measurements/30456676/#probes <https://atlas.ripe.net/measurements/30456676/#probes> _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages