I agree that it's a difficult problem, but it's Heroku's obligation to solve those problems. You can't position yourself like this: > Heroku takes full respons

I agree that it's a difficult problem, but it's Heroku's obligation to solve those problems. You can't position yourself like this: > Heroku takes full responsibility for your app's health, keeping it up and running through thick and thin and not commit to solving hard problems like geographically dispersed EC2 instances. Resource constraints, to be fair, aren't an acceptable excuse at this point. They aren't a floundering startup. They're a part of a multibillion dollar company.