News for hackers. Stuff that matters.

A comment on Google Kubernetes Engine's third consecutive day of service disruption. Parent comment

Re:Google Kubernetes Engine's third consecutive day of servi... by doodliego on Sunday November 11, 2018 @09:08PM (#18430095)
Compare Amazon's responses during their S3 outage: https://www.theregister.co.uk/2017/03/01/aws_s3_outage/ (toward the bottom)

What's the better communication plan: detailed, hourly updates or terse, one-line blog posts scattered across several days?

[ Parent | on HN ]
Re:Google Kubernetes Engine's third consecutive day of servi... by joshuamorton on Sunday November 11, 2018 @09:21PM (#18430156)
I think this comes down to the two outages being not at all similar. An s3 outage affects practically every Amazon customer. This affects a relatively small number of go customers.

And I'm confused about what was good about that response. That article is about how the s3 outage caused so many issues that Amazon couldn't update their status dashboard to inform users at all.

[ Parent | on HN ]