GCP finally acknowledges the issue: https://status.cloud.google.com/incidents/w7D5XGtVfMGcdcg4Zzud#7Nro3snGH5YXCyUfQuKS https://status.cloud.google.com/incident

GCP finally acknowledges the issue: https://status.cloud.google.com/incidents/w7D5XGtVfMGcdcg4Zzud#7Nro3snGH5YXCyUfQuKS https://status.cloud.google.com/incidents/w7D5XGtVfMGcdcg4Zz... Though their timing is incorrect. We noticed this at 9:26 AM EST and their posting says it "started" at 10:11 AM EST.