Live data from Hacker News

Ask HN: Is S3 down?

news.ycombinator.com

771–780 of 1001 posts

Re: Ask HN: Is S3 down?

#773
post #440

Earlier quoted context omitted.

Same here, and it's 100% consistent, not 'increased error rates' but actually just fully down. I'd just stop working but I have a demo this afternoon... the downsides of serverless/cloud architectures, I guess.

Well what if you'd hosted it on your hard drive and it crashed? It seems like the probability of either is similar nowadays.

Grab different machine, git clone your repo, good to go.

What's the odds of the server with your repo and your own hard drive crashing at the same time?

Re: Ask HN: Is S3 down?

#775

I like how you know this comment is in poor taste, and posted it anyways.

I'm happy the top comment was posted, and simultaneously happy that you pointed out that it is in questionable taste/timing.

Life is full of tradeoffs and balances, it's not wrong to point out the social or human ramifications of a post, just as it's not wrong to reply, "Yes, but nevertheless..."

Re: Ask HN: Is S3 down?

#776

Earlier quoted context omitted.

Could be worse, your entire infrastructure could be hosted on Heroku. You don't use S3 but because they do, your entire infrastructure crumbles.

I don't see why this is being downvoted. It's a pretty legitimate concern.

esp since my side project on heroku which uses nothing is down because of this.

Re: Ask HN: Is S3 down?

#778

Yup, same here. It has been a few minutes already. Wanna bet the green checkmark[1] will stay green until the incident is resolved? [1] https://status.aws.amazon.com/

It's crazy how much better the communication (including updates and status pages) is of the companies that rely on AWS than AWS' communication itself. https://status.heroku.com/incidents/1059

Font Awesome went out for me for a bit, but they did a great job getting back up and keeping their users in the loop.

https://status.fortawesome.com/

Re: Ask HN: Is S3 down?

#779

It's interesting to note the cascading effects. For example, I was immediately hit by three problems: * Slack file sharing no longer works, hangs forever (no way to hide the permanently rolling progress bar except quitting) * Github.com file uploads (e.g. dropping files into a Github issue) don't work. * Imgur.com is completely down . * Docker Hub seems to be unavailable. Can't pull/push images.

A doctor's office that's unable to process patients due to the outage: https://mobile.twitter.com/drjincali/status/8366578638879989...

I mean, that's not really AWS's problem, is it? Outages happen. If you have a mission-critical service like health care, you really shouldn't write systems with single points of failure like this, especially not systems that depend on something consumer-grade like S3.

This appears to be a normal doctor's office where there are routine appointments. Emergencies would be referred to the ER anyway. And while I obviously don't know the details of how his office is run, you'd think that you could get by on a pen-and-paper fallback to manage the office. Maybe that's an advantage to keeping experienced office staff on board.

Post reply on HN