3 ms·
It appears to only be affecting apps that have multiple dynos. While Heroku is busy fixing the issue if you scale your app to a single dyno (assuming it can ha
by craigkerstiens 5y ago
It appears to only be affecting apps that have multiple dynos.
While Heroku is busy fixing the issue if you scale your app to a single dyno (assuming it can handle the traffic) it should restore availability.
- ericpauley 5y agoWe also had single-dyno apps affected.
- craigkerstiens 5y agoIt may have been during an earlier part of the instance, but we just scaled multiple affected apps to a single dyno and all recovered. ps restart with multiple dynos and no effect.
- jeremyjh 5y agoI did too. I'm curious if you also have pre-boot enabled? I think that may set the routing configuration the same as if multiple dynos are up.
- bisRepetita 5y agoI had single dynos affected.
- reubano 5y agoMy 6 apps are all single dyno. Not sure if I have pre-boot enabled or not though....
- jrochkind1 5y agoMy single-dyno app was affected. However, while I could not connect to my app, nobody I know could connect to my app, and my monitoring service could not connect to my app for a ping... my app logs showed that some traffic continued to connect throughout the outage. So it was not entirely universal. And was clearly a routing problem of some kind.