a month ago
Hi Railway team,
My service "academy-server" (project: wonbiseo.co.kr, region: US West / Metal) has been failing to deploy for over an hour. Every deployment passes Initialization and Build fine, but fails at "Deploy > Create container" with "Failed to create deployment." Some attempts hang for ~30 minutes before timing out.
Key points:
Redeploying an older commit that previously deployed successfully fails the same way, so this is not a code issue.
Railway's own auto-diagnosis flagged it as "Diagnosis > Infrastructure Error," stating the build and image publish succeeded but the container could not be created due to a platform infrastructure issue.
The public status page shows "Fully Operational," so this appears isolated to my project/region.
This service has a volume attached (academy-server-volume), so I suspect it may be related to the host machine the volume is pinned to.
Current state: the last good deployment is stuck "Sleeping," and all new deployment attempts fail at container creation.
Could you check the machine/region my service is on and help get the container created? If the host node holding the volume has an issue, please migrate it to a healthy node. Thank you.
Failed deployment IDs: 54a689df, 981c2869, b14ee14a
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
I am having the same issue
a month ago
Thanks for the failed deployment IDs and for noting the attached volume — your suspicion is right: this is the host the volume is pinned to. It's a known platform-side issue from today's US West networking disruption, where the build and image publish succeed but container creation fails because the volume is pinned to an affected host. (The status page showing "operational" is why it looked isolated to your project — the degradation is at the host/scheduling level.)
Your data volume is intact. This needs platform-side recovery to migrate the service onto a healthy node — it can't be worked around from your end. We're escalating it now. I don't have a firm ETA yet but will follow up here. (Same root cause for anyone else seeing this on a volume-attached service in the region.)
Status changed to Awaiting User Response Railway • about 1 month ago
25 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 25 days ago