4 ms·
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
by qmarchi 7y ago
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.
- the-dude 7y agoThis can't be real.
- svacko 7y agoIs 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 7y agoSeems AWS, connection to gmail's smtp relay also started timing out.
- deleted 7y ago[deleted]
- gigatexal 7y agoOh man I had no idea the big cloud providers have dependencies on other clouds like this.
- dodobirdlord 7y agoGiven 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 7y agoThe 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 7y agoIf 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.
- gigatexal 7y agoYeah, I see that now. Makes total sense.
- lima 7y agoThey 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.
- unbeli 7y ago[removed]
- packetslave 7y agoNext time YOU are about to spout off about something, perhaps think about reading the f'ing page being linked to? "The issue with connectivity between the GCP us-east1, us-east4, and us-central1 regions to other Cloud Providers has been resolved for all affected projects as of Friday, 2020-03-27 13:37 US/Pacific."
- deleted 7y ago[deleted]