Migrating away from the old Heroku legacy routing layer

Heroku has set an end-of-life date for their legacy routing layer and if you're using Heroku, this could affect you and your applications. Starting September 29th, they will no longer support applications use their legacy routing. Here is the criteria for determining if you are using their legacy routing layer:

Has and uses example-app.heroku.com domain

Has any DNS records with values that are subdomains of .heroku.com (typically proxy.heroku.com or example-app.heroku.com)

Has DNS A records with values that are IP addresses of infrastructure maintained by Heroku

Uses SSL termination add-ons of types ssl:ip or ssl:hostname

Heroku has published an excellent article explaining how to handle the move. We recommend reading through that first before making any changes.