To whomever commented something like 'laughs in AWS' (comment was removed before I submitted the comment)... please don't... glass house and all that... but I also share the same glass house as you.. I don't want bad luck ... and it's only a fluke that this happened to google in eu-east1 and not AWS in X region and then you (and I) would be having a time of hell! :/
Google Cloud networking issues in us-east1
61–70 of 341 posts
Re: Google Cloud networking issues in us-east1
#62To whomever commented something like 'laughs in AWS' (comment was removed before I submitted the comment)... please don't... glass house and all that... but I also share the same glass house as you.. I don't want bad luck ... and it's only a fluke that this happened to google in eu-east1 and not AWS in X region and then you (and I) would be having a time of hell! :/
And did we forget about the insane AWS east outages of two years ago?
Nobody really wanted to be [enterprise software]-certified, but it was a way to get their employers to pay for them to go to the conference with cool talks and perks and such.
We delayed the training most of the day, and couldn't say it was AWS' fault because they were sitting in the audience, waiting to get certified.
People were about to riot, that was not a fun day.
Re: Google Cloud networking issues in us-east1
#63Earlier quoted context omitted.
I don't follow comments like these, should people refrain from criticising giant companies because there are people working at them? I don't understand the purpose of this comment
My hope is that we can be kind and decent to other people even in moments of stress. Take two very different example comments: "This is a frustrating outage for us, a huge part of the attraction in Google Cloud has been the premise that we get the underlying reliability of Google's infrastructure. If we'd known what the reliability of Google in practice this year would look like, we might have stayed with AWS." and "…
if this statement you quoted is something you're not comfortable with, i have a hard time believing you have ever encountered criticism in your life.
Re: Google Cloud networking issues in us-east1
#64Re: Google Cloud networking issues in us-east1
#65What's the actual number of 9s for the major cloud services these days? My impression from their PR seems to mismatch the number of outages and issues lately.
Due to network failures etc. number visible to customers is unlikely to be going to be much higher than that in cloud services.
Re: Google Cloud networking issues in us-east1
#66Earlier quoted context omitted.
My hope is that we can be kind and decent to other people even in moments of stress. Take two very different example comments: "This is a frustrating outage for us, a huge part of the attraction in Google Cloud has been the premise that we get the underlying reliability of Google's infrastructure. If we'd known what the reliability of Google in practice this year would look like, we might have stayed with AWS." and "…
> This is a frustrating outage for us, a huge part of the attraction in Google Cloud has been the premise that we get the underlying reliability of Google's infrastructure. If we'd known what the reliability of Google in practice this year would look like, we might have stayed with AWS. if this statement you quoted is something you're not comfortable with, i have a hard time believing you have ever encountered critic…
Re: Google Cloud networking issues in us-east1
#67Holy crap. It’s an outage in all zones? What’s the point of AZs if you lose whole DCs at a time.
Re: Google Cloud networking issues in us-east1
#68To whomever commented something like 'laughs in AWS' (comment was removed before I submitted the comment)... please don't... glass house and all that... but I also share the same glass house as you.. I don't want bad luck ... and it's only a fluke that this happened to google in eu-east1 and not AWS in X region and then you (and I) would be having a time of hell! :/
Google seems to be more forthcoming with their issues. We have seen incidents in AWS where the status never got updated, but support confirmed issues.
Re: Google Cloud networking issues in us-east1
#69Earlier quoted context omitted.
I would argue that two direct Google Cloud outages within a month is pretty concerning for GCP customers, and that it's possible that the calendar outage could also be related in someway since it is likely hosted on GCP, although that is speculation
Doubt Calendar is hosted on GCP. Generally Google does not run first-party systems on GCP, instead putting them on Borg (internal cloud).
AFAIK Amazon are running a lot of actual production loads on AWS. Dogfooding can be extremely valuable, especially if a massive portion of your staff have the same profession as your target market.
I've been using Google Cloud in a new role I started recently. There's definitely some parts of GCP I like, but whenever I use the Web Console I get the distinct impression nobody at Google actually uses it. If they did, I'm fairly sure all the annoying little warts I encounter would not exist.
Re: Google Cloud networking issues in us-east1
#70To whomever commented something like 'laughs in AWS' (comment was removed before I submitted the comment)... please don't... glass house and all that... but I also share the same glass house as you.. I don't want bad luck ... and it's only a fluke that this happened to google in eu-east1 and not AWS in X region and then you (and I) would be having a time of hell! :/
And did we forget about the insane AWS east outages of two years ago?