3 months ago
On Vercel
Every deployment is a new immutable version.
Your current live version stays running until the new one is built & verified.
If the new build fails → Vercel just never “promotes” it to production.
Result: No downtime, old deployment continues serving traffic.
On Railway
Railway is more like “run this Docker/container forever”:
You usually have one running instance of your service.
When you deploy:
It rebuilds & restarts that same service.
If the new build / start command fails → the service crashes.
Since there is no previous instance kept alive, your API goes down.
Need vercel deployment method please help me to build in railway for zero down time.
Pinned Solution
2 months ago
Hey, please refer to the health check documentation. The quick summary is that you want to have an endpoint, such as /health that responds status ok (200) once your service is ready (for example after successful start up and after all database connections have established. For simple APIs that don't have any external dependencies, starting up correctly and not crashing may already be enough, so responding status ok right away may also be fine in your case).
11 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
Hello,
As long as you use a health check we will wait until the new deployment passes the health check before switching over for a true zero downtime deployment.
Status changed to Awaiting User Response Railway • 4 months ago
3 months ago
i have to put my api link in healthcheck
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Please help me to configure the health-check for my project.
2 months ago
Please help me
2 months ago
أرجو السماح لى بمساحة عنل
scancarz
i have to put my api link in healthcheck
2 months ago
Hey, please refer to the health check documentation. The quick summary is that you want to have an endpoint, such as /health that responds status ok (200) once your service is ready (for example after successful start up and after all database connections have established. For simple APIs that don't have any external dependencies, starting up correctly and not crashing may already be enough, so responding status ok right away may also be fine in your case).
uxuz
Hey, please refer to the health check documentation. The quick summary is that you want to have an endpoint, such as /health that responds status ok (200) once your service is ready (for example after successful start up and after all database connections have established. For simple APIs that don't have any external dependencies, starting up correctly and not crashing may already be enough, so responding status ok right away may also be fine in your case).
2 months ago
I have to make changes in my code base.
scancarz
I have to make changes in my code base.
2 months ago
Ideally, it's just an API route that responds 200.
Status changed to Solved brody • about 2 months ago
uxuz
Hey, please refer to the health check documentation. The quick summary is that you want to have an endpoint, such as /health that responds status ok (200) once your service is ready (for example after successful start up and after all database connections have established. For simple APIs that don't have any external dependencies, starting up correctly and not crashing may already be enough, so responding status ok right away may also be fine in your case).
9 days ago
Still not work
Status changed to Awaiting Railway Response Railway • 9 days ago
scancarz
Still not work
9 days ago
Define "still not work". What doesn't work? How is your health api route setup?