Issue
Router 2.0, now generally available, is the replacement for the Common Runtime's legacy router. The legacy router end-of-life (EOL) is scheduled for Spring 2025 and all common runtime customers will be upgraded to Router 2.0 by the deprecation date.
Resolution
Can I Move to Router 2.0 Prior to the Deprecation Timeline?
Yes, we encourage you to upgrade as soon as you can to Router 2.0 by following the instructions in this Dev Center article or reading this Migration Tips and Tricks Blog Post
What is the Deprecation Timeline?
Our current target dates are below. Please note that these are subject to change as we evaluate the new router following the GA rollout.
The week of December 9, 2024, the Heroku platform will begin migrating Eco-tier Common Runtime applications from the legacy router to Router 2.0.
The week of February 3, 2025, the Heroku platform will begin migrating Basic-tier Common Runtime applications to Router 2.0.
The week of February 18, 2025, the Heroku platform will begin migrating Standard & Performance-tier Common Runtime applications to Router 2.0.
What if I run my application in a Private or Shield Space?
Private and Shield tier applications will be unaffected since they run in Private Spaces and not the Common Runtime.
What are the feature differences between the Legacy Router and Router 2.0?
Please reference this section of the HTTP Routing Dev Center article to understand the differences between the routers. Currently, there is full feature parity between the two routers.