Re:Google Kubernetes Engine's third consecutive day of servi...
by human_error on Sunday November 11, 2018 @08:32PM
(#18429954)
> When an entire region is down what I have noticed is that all things are fucked globally on aws.
Do you have an example on this?
Re:Google Kubernetes Engine's third consecutive day of servi...
by excalq on Sunday November 11, 2018 @09:58PM
(#18430284)
On 17 October, there was a multi-AZ network failure at us-east-1. It only lasted 3m35s, but it was enough that our customers were calling about our site being down.
Re:Google Kubernetes Engine's third consecutive day of servi...
by ghusbands on Monday November 12, 2018 @05:16AM
(#18431651)
That's still just one region, unless you were also hosted outside us-east-1.
Re:Google Kubernetes Engine's third consecutive day of servi...
by ransom1538 on Sunday November 11, 2018 @08:39PM
(#18429982)
Just grabbed first article. Example: In this case capitalone went down. I don’t work at capitalone - but I imagine they had their data copied across every region 30 times.
https://www.geekwire.com/2018/widespread-outage-amazon-web-s...
Ok. So on aws we were* paying for putting systems across regions, but, honestly I don’t get the point. When an entire region is down what I have noticed is that all things are fucked globally on aws. Feel free to pay double - but it seems* if you are paying that much just pay for an additional cloud provider. Looks like it’s the same deal on GCP.