Every time AWS, Heroku, GitHub, Twitter is down it gets posted here and this is exactly the discussion the takes place:

Commenter1: Well they should've never relied on X platform. Single point of failure, etc.

Replyers: It's not Platform X's fault, the engineers should've set up servers like XYZ. It's not like it's hard to do.

Then someone says their app is down, someone else says this sucks, some statistics on uptime get thrown about, and the exact same conversation ensues as the last time any other service went down.

So my honest and sincere question is this: why? Why do "Service X is down" posts get posted and upvoted to the front page? Why do we all have the same discussion each time it happens? It just seems like there's just nothing else to say about it and these sites have status pages where we can all find out for ourselves if they're down or not, so why are we repeating ourselves?

Heroku, AWS, GAE are popular and well-known... but by tightly integrating an application or service to a proprietary platform, you're pretty much at the mercy of the PAAS provider.

To avoid vendor lock-in, check out OpenShift[1] from Red Hat. It's open source[2] so you can set it up on your own servers if you felt Red Hat weren't providing the service you required, or as redundant servers for fail-over.

[1] https://openshift.redhat.com/community/paas

[2] https://openshift.redhat.com/community/open-source/download-...

I thought Heroku was committed to building out more robust handling after the last AWS issue? Rather disappointed with Heroku's uptime solely based on articles I've seen on HN.

I'm not a customer of Heroku, I've stuck with Rackspace the last 5 years because they are located in San Antonio and I'm in Austin. However, many project I've worked on the last 12 months use Heroku for production.

Amazon is showing "Performance issues" on their status page.

I think we've all misunderstood. They actually aren't reporting service disruptions, but rather their revenue having having "performance issues" with all the SLA crediting they'll have to do.

It is so common with heroku to go down !

Not just because of AWS, but on there own they have many issues with platform.. a short list - https://twitter.com/rtdp

we need to seriously shift away of heroku asap !

Yes, we are also experiencing difficulty in accessing https://api.heroku.com/login and git push to heroku. However, our web app is up and running.

Our production site has been down for an hour (a separate staging site on heroku is still up and running), and it does appear to be Elastic Load Balancer-related from what I can tell.

Heroku uptime is almost a replica of AWS uptime. If AWS is down, heroku is the first service to go down.

But status emailing system is really good :)

I guess its due to EC2 North America issues - http://status.aws.amazon.com/.

Hugely pissed. My SSL site has been down since 10pm EST last night. It's a huge traffic day for us as well. Damn those AWS and Heroku jackasses. No excuse for this nonsense occurring almost regularly. I'm done with Heroku for good. You'd think AWS and Heroku would figure out some kind of way to handle it when AWS-East goes down. But I guess Heroku is too busy overcharging people to care. /rant

Quora is down Edit: back up, for the moment

Our game is on Heroku and it's up http://warsocial.com