Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS us-east-1 outage

status.aws.amazon.com

Post reply on HN
Print view View original

381–390 of 1001 posts

Re: AWS us-east-1 outage

#381

Post by Kavelach »

ethbr0 wrote: post #235
jolux wrote: post #151

Earlier quoted context omitted.

It should be costing them trust not to push it when they should though. A trustworthy company will err on the side of pushing it. AWS is a near-monopoly, so their unprofessional business practices have still yet to cost them.

> It should be costing them trust not to push it when they should though. This is what Amazon, the startup, understood. Step 1: Always make it right and make the customer happy, even if it hurts in $. Step 2: If you find you're losing too much money over a particular issue, fix the issue . Amazon, one of the world's largest companies, seems to have forgotten that the risk of not reporting accurately isn't money, but…

> It's late Soviet Union in a nutshell

How come an action of a private company in a capitalist country is like the Soviet Union?

Re: AWS us-east-1 outage

#383

Post by zedpm »

SEMW wrote: post #343
andrew_ wrote: post #229

Earlier quoted context omitted.

Side question: How happy are you with API Gateway's WebSocket service?

No idea, we don't use it. These were websocket connections to processes on ec2, via NLB and cloudfront. Not sure exactly what part of that chain was broken yet.

This whole time I've been seeing intermittent timeouts when checking a UDP service via NLB; I've been wondering if it's general networking trouble or something specifically with the NLB. EC2 hosts are all fine, as far as I can tell.

Re: AWS us-east-1 outage

#384

Post by kortex »

melony wrote: post #243
maximedupre wrote: post #227

Earlier quoted context omitted.

Or just take responsibility. People will respect you for doing that and you will demonstrate leadership.

And the guy who doesn't take responsibility gets promoted. Employees are not responsible for failures of management to set a good culture.

The Gervais/Peter Principle is alive and well in many orgs. That doesn't mean that when you have the prerogative to change the culture, you just give up.

I realize that isn't an easy thing to do. Often the best bet is to just jump around till you find a company that isn't a cultural superfund site.

Re: AWS us-east-1 outage

#386

Post by dotancohen »

kylemh wrote: post #141
sakopov wrote: post #38

Earlier quoted context omitted.

Those five 9s don't come easy. Sometimes you have to prop them up :)

https://aws.amazon.com/compute/sla/ looks like only four 9's

  > looks like only four 9's
That's why the Germans are such good engineers.

  Did the drives fail? Nein.
  Did the CPU overheat? Nein.
  Did the power get cut? Nein.
  Did the network go down? Nein.
That's "four neins" right there.

Re: AWS us-east-1 outage

#387

Post by john37386 »

It seems a bit long to fix!

They probably paint themselves in a corner just like facebook few weeks ago.

This make me think;

Could it be that one day the internet will have a total global outage and it will take few days to recover?

Re: AWS us-east-1 outage

#388

Post by hinkley »

Spivak wrote: post #237
JohnJamesRambo wrote: post #112

Earlier quoted context omitted.

> Goodhart's Law is expressed simply as: “When a measure becomes a target, it ceases to be a good measure.” It’s very frustrating. Why even have them?

Because "uptime" and "nines" became a marketing term. Simple as that. But the problem is that any public-facing measure of availability becomes a defacto marketing term.

Also 4-5 nines is virtually impossible for complex systems, so the sort of responsible people who could make 3 nines true begin to check out, and now you've getting most of your info from the delusional, and you're lucky if you manage 2 objective nines.

Re: AWS us-east-1 outage

#389

Post by bithavoc »

temuze wrote: post #113

Friends tell friends to pick us-east-2. Virginia is for lovers, Ohio is for availability.

Sometimes you can't avoid us-east-1; an example is AWS ECR Public. It's a shame. Meanwhile, DockerHub is up and running even when it's in EC2 itself.
Post reply on HN