Heya, we're still investigating the root cause for these failures. I'm going to escalate this to our infra team so they can finish the migration.

Hello!

We've escalated your issue to our engineering team.

We aim to provide an update within 1 business day.

Please reply to this thread if you have any questions!

Apologies for the confusion - your service is still up and running, and the failed deployment you see is an error from our end.

Railway may move workloads across hosts for maintenance and/or load-shedding reasons. This is a proactive measure we take to ensure sustained uptime of your services, and to guarantee that your workload can fully access the resources you have according to your plan's limit.

We usually do this when we notice anomalous metrics in our internal monitoring that may result in degraded performance (slower CPU etc.) for our users' deployments.
We're in the middle of scaling up our fleet so these will not happen as frequently in the next few months.

Your workloads may also be moved due to the Railway Metal migration, if you are not already on Metal.

If you encounter this issue again, please respond here or create a new thread and we'll be happy to assist you.

Best,

The Railway Team

❌ The ticket Migration issue encountered has been marked as canceled.