@deleted-U06C7A8PVLJ @Ryan @Nicholas McFadden @Dustin Surwill Did anyone change any permissions or run anything in Bigquery today? Out of nowhere the majority of our scheduled queries started failing. It's happening to pipelines that don't necessarily go together.
I redoplyed the Leadspedia info
I did not do anything. I am also seeing the errors
I am seeing that central1 stuff is down
Iβm getting errors. I canβt look at some tables
I was just about to do the same
It did say to me I needed permissions to go into cloud scheduler which was weird since I could go on there in the past
*Thread Reply:* That is probably related to the identity service being down
@Joe Santana has joined the conversation
Well good to know it's not something we caused but dang- It's not even just the Americas. It's every region around the world. Cloud Redundancy be damned.
Well, the google, aws and cloudflare outages could be partially related and cause the rest of them
https://www.cloudflarestatus.com/
Looks like our Postgres DB in Google Cloud SQL is affected, integrations have started throwing connection errors
looks like they identified the issue and are recovering
Cloudflare has but not Google yet, https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW
We will have to wait for us-central1 for a good chunk of our automations
I got some input from other google centric sources that there seems to be at least, some recovery, how are we doing?
We can now see majority of our data, which we Could not before, but scheduled transformation is still hit and miss.
A lot of our main transformation pipelines run on Central1 which was the last to be fixed.
That was last I checked, I'm going to try again shortly.
Looks like scheduled queries are back up!
We can now see majority of our data, which we Could not before, but scheduled transformation is still hit and miss.
A lot of our main transformation pipelines run on Central1 which was the last to be fixed.
Identity and access management is still down for all of the Americas, but as long as we stay logged in and don't need to give/remove access so far so good on the GCP side.
Looks like Cloud Services are running again
Do we have the issue publicly released yet?