My app is down, got alerted by my monitoring. (It's a hobby/side project app, so not a big deal, I'd be freaking out if this were a money-making production app. In this case, first thing I did before even checking heroku status was seeing if I had let my domain name expire... nope! phew).<p>While the heroku outage message that suggests the main problem is "dynos can not be restarted" -- in fact what happened to me was at 3pm UTC Heroku tried to do an automatic "daily restart" of my app, triggering an outage of my app. I did not do anything else to ask for a restart.<p>The heroku stats/events page for my app shows ~300 critical errors, starting at 3pm UTC, immediately following "Dyno restart: Daily restart" event. (~1 hour 40 minutes before now). All appear to be "H20 App boot timeout". So perhaps the app has been down since then, although i would have thought my monitoring would alert me before now.<p>If when a reboot fails, it tries again, and fails again (~150 times an hour), and this is happening to a whole bunch of apps, especially as a consequence of heroku's automated dyno cycling... I can see how it would make a bad problem even worse/hard to recover from in heroku's infrastructure.<p>To heroku's credit... I'm not sure if I can remember this kind of widespread outage <i>ever</i> happening before. Against heroku's side... I'm not sure what a heroku-deploying customer would be expected, by heroku, to do, to avoid downtime here. "Have your whole thing runnable on some non-heroku stack" kind of detracts from heroku's value proposition, which is you won't have to figure out stuff like that, heroku will do it for you. If I was going to do the work to ensure my app could be switched at any time to be deployed on some other stack... I'd probably just use that some other stack instead of heroku, as it's probably cheaper than heroku. The answer is probably "No matter how much you are doing yourself, outages are possible. By using heroku you put it in their hands, but outages are still possible."<p><i>update</i> possibly related? <a href="https://status.aws.amazon.com/?date=2019-08-31" rel="nofollow">https://status.aws.amazon.com/?date=2019-08-31</a> <a href="https://status.aws.amazon.com/?date=2019-08-31" rel="nofollow">https://status.aws.amazon.com/?date=2019-08-31</a> (in which case you might have been saved by having multi-region deployment on heroku. But if it's only effecting us-east-1, you'd think heroku would have noticed and said so? Could be unrelated in an odd coincidence. Or perhaps there's effected heroku infrastructure on us-east-1 regardless of what region you choose to deploy on heroku).