Issue
Heroku app is not responding to requests. Client requests are timing out. Some requests may be successful, based on which dyno they are routed to.
Resolution
Dynos exhibiting connectivity issues during this incident can be replaced by stopping each dyno in the app's formation. This action may potentially restore functionality of their app prior to a full announcement from Heroku stating that the incident has been resolved.
Using Heroku CLI, first retrieve the list of dynos in an app's formation:
heroku ps -a your-app-name
Then, replace each of the app's dynos by stopping them:
heroku ps:stop --dyno-name web.1 --app your-app-name
For each dyno, substitute web.1 in this example with the actual dyno from the output of the initial heroku ps command. This process avoids replacing all dynos at the same time, which would result in a brief app outage.
Disclaimers
- This only applies to Private Space apps.
- This does not guarantee that the full functionality of an app will be restored until Heroku declares that the incident is fixed. Upstream services that are also impacted may not yet be fixed. For example, Heroku Connect is an impacted service, so if the app you are restarting uses Heroku Connect then that functionality of your app may not be available yet.
- This incident does not affect Heroku Data.