4 ms·

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

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! :/

dymk 7y ago
And did we forget about the insane AWS east outages of two years ago?
- fjp 7y ago
  During that AWS outage I was training people on [enterprise software] as part of the certification portion of [enterprise software company annual conference]. 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.
- deleted 7y ago
  [deleted]
outworlder 7y ago
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.
- deleted 7y ago
  [deleted]
- deanCommie 7y ago
  Show me a GCP post-mortem that's as detailed and proactive about future improvement as https://status.aws.amazon.com/s3-20080720.html https://status.aws.amazon.com/s3-20080720.html Their last one was laughable in it's lack of self-awareness.
  - joshuamorton 7y ago
    https://status.cloud.google.com/incident/cloud-networking/19009 https://status.cloud.google.com/incident/cloud-networking/19... Can you explain what's better about the AWS one? They both do, approximately, the same thing: provide a few paragraphs of background, approximately one paragraph describing the actual issue, and a few paragraphs describing concrete followups. The AWS one has more timestamps. You aren't confusing this[0] with the postmortem, are you? [0]: https://cloud.google.com/blog/topics/inside-google-cloud/an-update-on-sundays-service-disruption https://cloud.google.com/blog/topics/inside-google-cloud/an-...
mirceal 7y ago
i don't quite follow your logic. something about glass houses and bad luck? the whole point when something like this happens is for you to ensure that a region going down will not impact you - not to laugh at people that use another cloud or to assume that X is better than Y. That being said, there have been several Google related failures lately that don't help building confidence in the GCP offering - if you're just starting in the cloud space this may actually impact the choices you make when you pick your cloud provider.
- mrmattyboy 7y ago
  My point was that, there was a comment from someone saying 'laughing from aws' and I was trying to point out that each service is most likely (or should be considered to be) as fragile (in the relative sense) as each other. So just because google have gone down several times, doesn't mean that AWS won't have a line of outages next. Really, their services are much of a black hole to us.. we can't see _how_ they deploy their changes, what kind of reviewing they do etc. etc. Even down to how cleverly they have _actually_ architected their DCs. So my point was to _not_ to laugh at those at google (or those using their services), because AWS might be next. The whole 'I share the same glass house', was a sort of karma thing.. if someone who uses AWS is laughing at Google. If karma came round and took out AWS, not only would it affect the guy laughing at google, but I'd be the one affected as well as a multitude of other people... and the tables could be easily turned

dymk 7y ago

And did we forget about the insane AWS east outages of two years ago?

fjp 7y ago
During that AWS outage I was training people on [enterprise software] as part of the certification portion of [enterprise software company annual conference]. 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.
deleted 7y ago
[deleted]

outworlder 7y ago

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.

deleted 7y ago
[deleted]
deanCommie 7y ago
Show me a GCP post-mortem that's as detailed and proactive about future improvement as https://status.aws.amazon.com/s3-20080720.html https://status.aws.amazon.com/s3-20080720.html Their last one was laughable in it's lack of self-awareness.
- joshuamorton 7y ago
  https://status.cloud.google.com/incident/cloud-networking/19009 https://status.cloud.google.com/incident/cloud-networking/19... Can you explain what's better about the AWS one? They both do, approximately, the same thing: provide a few paragraphs of background, approximately one paragraph describing the actual issue, and a few paragraphs describing concrete followups. The AWS one has more timestamps. You aren't confusing this[0] with the postmortem, are you? [0]: https://cloud.google.com/blog/topics/inside-google-cloud/an-update-on-sundays-service-disruption https://cloud.google.com/blog/topics/inside-google-cloud/an-...

mirceal 7y ago

i don't quite follow your logic. something about glass houses and bad luck? the whole point when something like this happens is for you to ensure that a region going down will not impact you - not to laugh at people that use another cloud or to assume that X is better than Y. That being said, there have been several Google related failures lately that don't help building confidence in the GCP offering - if you're just starting in the cloud space this may actually impact the choices you make when you pick your cloud provider.

mrmattyboy 7y ago
My point was that, there was a comment from someone saying 'laughing from aws' and I was trying to point out that each service is most likely (or should be considered to be) as fragile (in the relative sense) as each other. So just because google have gone down several times, doesn't mean that AWS won't have a line of outages next. Really, their services are much of a black hole to us.. we can't see _how_ they deploy their changes, what kind of reviewing they do etc. etc. Even down to how cleverly they have _actually_ architected their DCs. So my point was to _not_ to laugh at those at google (or those using their services), because AWS might be next. The whole 'I share the same glass house', was a sort of karma thing.. if someone who uses AWS is laughing at Google. If karma came round and took out AWS, not only would it affect the guy laughing at google, but I'd be the one affected as well as a multitude of other people... and the tables could be easily turned