Google Cloud Is Down

Post by tango24 » Sun, Jun 02, 2019, 8:13 PM UTC

votepaunchy wrote: post #49

tubaguy50035 wrote: post #37

Earlier quoted context omitted.

Obviously we don't know what the extent of the issue is yet, but afaik there has never been an AWS incident that has affected multiple regions where an application had been designed to use them (like using region specific S3 endpoints). GCP and Azure have had issues in multiple regions that would have affected applications designed for multi-region.

> like using region specific S3 endpoints AWS had the S3 incident affecting all of us-east-1: “Other AWS services in the US-EAST-1 Region that rely on S3 for storage, including the S3 console, Amazon Elastic Compute Cloud (EC2) new instance launches, Amazon Elastic Block Store (EBS) volumes (when data was needed from a S3 snapshot), and AWS Lambda were also impacted while the S3 APIs were unavailable.” https://aws.am…

Post by murat124 » Sun, Jun 02, 2019, 8:13 PM UTC

40acres wrote: post #78

Can't wait for the postmortem!

Post by sdan » Sun, Jun 02, 2019, 8:14 PM UTC

Post by f_martinez » Sun, Jun 02, 2019, 8:15 PM UTC

Post by boulos » Sun, Jun 02, 2019, 8:17 PM UTC

marksomnian wrote: post #87

boulos wrote: post #80

Earlier quoted context omitted.

Edit: and I agree! I’m not in SRE so I don’t bother with all the backup modes (direct IRC channel, phone lines, “pagers” with backup numbers). I don’t think the networking SRE folks are as impacted in their direct communication, but they are (obviously) not able to get the word out as easily. Still, it seems reasonable to me to use tooling for most outages that relies on “the network is fine overall”, to optimize for…

> the status dashboard now correctly highlights that multiple things are impacted because Networking. this column of green checkmarks begs to differ: https://i.imgur.com/2TPD9e9.png