Common Runtime Legacy Router End-of-Life FAQ
[Router 2.0](https://devcenter.heroku.com/articles/heroku-runtime-router-2-0) is generally available and the default router for any new Common Runtime application. Additionally, 94% of Common Runtime apps are already using the new router. Router 2.0 introduces several performance and security improvements, including HTTP/2 support and keepalives to dynos. The legacy router end-of-life (EOL) is scheduled for **Summer 2025** and all common runtime customers will be upgraded to Router 2.0 over the next few weeks.
In general, **the migration to Router 2.0 is an automatic switch that will happen transparently for customer applications**. No action is required on behalf of the customer. However, if a customer would like to validate the new router themselves before the automatic migration, they may do so by following [How do I access Router 2.0?](https://help.heroku.com/JMLSBDF0/how-do-i-access-router-2-0-the-new-common-runtime-router). If a customer is encountering issues using the new router, they may disable it and fall back to the legacy router.