Vercel provides Instant Rollback as a way to quickly revert to a previous production deployment. This can be useful in situations that require a swift recovery from production incidents, like breaking changes or bugs. It's important to keep in mind that during a rollback:
- The rolled back deployment is treated as a restored version of a previous deployment
- The configuration used for the rolled back deployment will potentially become stale
- The environment variables will not be updated if you change them in the project settings and will roll back to a previous build
For teams on a Pro or Enterprise plan, all deployments previously aliased to a production domain are eligible to roll back. Hobby users can roll back to the immediately previous deployment.
To initiate an Instant Rollback from the Vercel dashboard:
On the project's overview page, you will see the Instant Rollback.. From there, click
After selecting Instant Rollback, you'll see an dialog that displays your current production deployment and the eligible deployments that you can roll back to.
If you're on the Pro or Enterprise plans, you can also click the Choose another deployment button to display a list of all eligible deployments.
Select the deployment that you'd like to roll back to and click Continue.
Once you've selected the deployment to roll back to, verify the roll back information:
- The names of the domains and sub-domains that will be rolled back
- There are no change in Environment Variables, and they will remain in their original state
- A reminder about the changing behavior of external APIs, databases, and CMSes used in the current or previous deployments
Once you have verified the details, click the Confirm Rollback button. At this point, you'll get confirmation details about the successful rollback.
The rollback happens instantaneously and Vercel will point your domain and sub-domain back to the selected deployment. The production deployment tile for your project will highlight the canceled and rolled back commits.
The rolled back deployment will be replaced whenever the next successful commit happens to the main production branch.
- You cannot run parallel roll backs on the same project
- Only one deployment can be rolled back at a time for every project. However, a rolled back deployment stays disabled in your deployment list and can be accessed and re-reverted whenever you want
You can also roll back from the main Deployments tab in your dashboard. Filtering the deployments list by
main is recommended to view a list of eligible roll back deployments as this list all your current and previous deployments promoted to production.
Click the vertical ellipses (⋮) next to the deployment row and select the Instant Rollback option from the context menu.
- Hobby plan: On the hobby plan you can roll back to the previous deployment
- Pro and Enterprise plan: Owners and Members on these plans can roll back to any eligible deployment.
Deployments previously aliased to a production domain are eligible for Instant Rollback. Deployments that have never been aliased to production a domain, e.g., most preview deployments, are not eligible.
The Promote to Production option allow you to force an explicit overwrite of the current production deployment with any successful preview and production deployments. This process involves rebuilding the entire application, which can be slow.
Instant Rollback is a relatively faster process since it involves assigning domains to an existing deployment rather than a complete rebuild. We therefore recommend using Instant Rollback to quickly recover from an active incident in production. However, if you have time to build your project and you aren’t in a rush to resolve an urgent issue, it may make more sense to promote to production since you get your environment variables re-built.