3 ms·
https://status.heroku.com/incidents/1892 https://status.heroku.com/incidents/1892 - it appears Heroku is being particularly affected. We've had multiple sites o
by btown 7y ago
https://status.heroku.com/incidents/1892 https://status.heroku.com/incidents/1892 - it appears Heroku is being particularly affected. We've had multiple sites on multiple accounts go down in the past few minutes.
EDIT T16:31Z: It appears Heroku has failed over their dashboard, but dynos are still failing to come online. We had assumed that they had multi-region failovers for their customers. Incredibly disappointing.
- deleted 7y ago[deleted]
- bkovacev 7y agoWe cannot even restart/turn off the dynos or get into the dashboard to turn off and kill our background tasks for some of our clients.
- brianwawok 7y agoIs it best practice to run the dashboard and the cloud service in the same region of the same cloud provider?
- bkovacev 7y agoI believe it's not. As a PaaS I would think that they would run a high availability cluster on at least 2 multiple regions so that they would have a mechanism in place for events like these. I know it's expensive, but if you charge 250 for 2.5GB of RAM I believe you would have enough money to cover it. I also think as you hinted that they should separate services across different regions..
- me_pie_three 7y agoHeroku: don't restart your app; restarting is broken Also Heroku: we auto restart your dyno every day! So now my app is down because Heroku forced it to restart, and none of our hourly employees can work :|
- jrochkind1 7y agoHN discussion of heroku outage: https://news.ycombinator.com/item?id=20846270 https://news.ycombinator.com/item?id=20846270