Hey there!

You can improve your Build and Deployment times a few main ways:

1. Reduce your container size. The resulting container from your build needs to be packaged up, uploaded to Railway's registry, and then downloaded on your deploying workload. Any space you can save can decrease the times for each of these processes. You may want to look at your package manager and see what dependencies you can remove, or look at your Dockerfile and see if you can use a smaller, more production-ready base image.

2. Reduce your Resource Limits. If you're using replicas, Railway's orchestrator has to find space for the number of replicas * the Resource Limits you have set on the Settings tab. Lowering these limits to a more realistic size for your workload can decrease the time it takes for the orchestrator to schedule your workload.

It seems like an issue, it never takes that long, the usual time is 2 o 3 minutes for the entire pipeline

I'm having the same issue - build that would deploy in under 2-3 minutes are now taking 15min + and in some cases failing

I'm having the same issue as well

I am also facing the same issue

Also facing >20min and still not done

Currently investigating thank you all!

same issue

railway down again?

same issue here

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

We're currently investigating this and working on a fix thank you for raising! Will update here as soon as I have an update.

✅ The ticket Deployment issues with container creation. has been marked as completed.

✅ The ticket Deployment issues with containers has been marked as completed.