Heroku down for production and staging apps

Heroku down for production and staging apps(status.heroku.com)

29 points by julioademar 12 years ago | 15 comments

julioademar 12 years ago |

I still dream of the day they'll let us set up different availability zones. Not that I'm sure this wouldn't occur, mind you.

sync 12 years ago | |

Dynos already run in different availability zones: https://devcenter.heroku.com/articles/production-check

You can take that a step further by running dynos in the European (eu-west-1) region: https://devcenter.heroku.com/articles/regions

1qaz2wsx3edc 12 years ago | | |

> Multiple dynos are also more likely to run on different physical infrastructure (for example, separate AWS Availability Zones), further increasing redundancy.

It's not guaranteed. As I understand it, it's random.

And as for regions. They only help you locate content to a closer region. You cannot use them for balancing/redundancy. As any data or third party add-on you use, will manage it's data in it's own specific zone. Thus creating latency issues.

julioademar 12 years ago | | |

That's still in Beta though.

gabrtv 12 years ago | |

If you need deeper control of your application platform infrastructure, you should check out something like http://deis.io/. You can run a private Heroku in any EC2 region, zones, etc.

Running your own PaaS is not for the faint of heart -- and Heroku certainly saves you time and headache -- but it's nice to have a private PaaS option that is Heroku compatible.

crashoverdrive 12 years ago |

I'd be curious to see the numbers of how often Heroku pushes code to production, and also how often those pushes break the build.

julioademar 12 years ago | |

Well, it may not be their fault: http://status.aws.amazon.com/

crashoverdrive 12 years ago | | |

Sorry, what I meant was that I wasn't suggesting it was their fault, I was merely reminded of my own curiosity of wanting to build a better product but not wanting to break what a ton of customers are using and paying a lot of money for

oliverdavenport 12 years ago | |

Is this issue not to do with the AWS problems?

justinsb 12 years ago | | |

For some reason, that story seems to have fallen off the front page, so people may not know that the root cause is not Heroku:

https://news.ycombinator.com/item?id=6380772

webbruce 12 years ago |

Yeah, seems to be Amazon, not Heroku this time.

chubot 12 years ago | |

Note from last time: https://status.heroku.com/incidents/151

"This post will reference the AWS services that we use behind the scenes so that we can be very specific. Note that although we will be discussing various AWS service failures, we don't blame them for what our customers experienced in any way. Heroku takes 100% of the responsibility for the downtime affecting our customers last week."

In other words, they shouldn't be exposing AWS outages to users (although as as long as they use a single cloud provider that's impossible to avoid in general.)