[qmarchi]

Heyo Googler here.

The problem was a mix between another cloud provider and GCP.

Dare I say, there should be little customer impact as of 13:37 PST.....

The status dashboard is going to be your best idea on information.

[svacko]

Is the another cloud provider AWS? I could see tons of connection timeoutes between GCP & S3/Elasticsearch service.

Hope everything is resolved now for good.

[judge2020]

Seems AWS, connection to gmail's smtp relay also started timing out.

[gigatexal]

Oh man I had no idea the big cloud providers have dependencies on other clouds like this.

[lima]

They do not, according to the dashboard, this issue merely affected connectivity between GCP and other cloud providers.

There was a different outage yesterday, which has nothing to do with the one discussed in this thread.

[dodobirdlord]

Given how much trans-continental/trans-oceanic network cable the major cloud providers own, they almost certainly have special trans-cloud network traffic infrastructure. Especially since so much of "The Cloud" is within a few 10s of square miles in a field in Virginia. I can easily see how one provider could majorly disrupt another provider by accidentally breaking inbound traffic on one of those links.

[qmarchi]

The bigger issue is that there's a lot of customers where they have split cloud deployments, which means the customers hurt even if they are stable within the clouds themselves.

[thedance]

If you are deployed in such a way that both GCP and AWS need to be up you're doing it backwards. Multi-cloud strategy is supposed to result in the intersection of cloud failures, not the union of them.

[uluyol]

I have heard that many companies are multi cloud as a result of acquisitions, resulting in a dependency on both clouds.

[qmarchi]

"But all of our problems are fixed by going to the cloud!"

[gigatexal]

Yeah, I see that now. Makes total sense.

[the-dude]

This can't be real.

[unbeli]

[removed]