25 days ago
Region: us-west2 · Failed deployment ID: a2925951 (one of many)
Since ~09:40 CEST today every deployment of our service hangs or fails at
"Deploy › Create container" (7+ attempts, timeouts after 19–23+ minutes).
Images build and push successfully every time. Railway's own diagnosis says:
"Infrastructure Error — unable to schedule the container in the us-west2
region… the code and configuration are correct."
To rule out a volume-attach conflict we removed the running deployment —
scheduling still hangs even with the volume free. As a result the service
is now COMPLETELY DOWN (edge returns "Application not found").
This matches the known CREATE_CONTAINER-stuck pattern (cf. the May 19 thread
"Production app down 8h+, Postgres stuck…") that required manual intervention
by the Railway team.
IMPORTANT: the volume mounted at /data holds our production database.
It must stay attached to this service — do NOT migrate, detach, wipe or
re-initialize it.
Please unstick container scheduling for our service — you can identify the
project via my account / the deployment ID above.
1 Replies
Status changed to Awaiting Railway Response Railway • 25 days ago
24 days ago
Hey, you're back up. Verified your service's current deployment is running as of a few minutes ago.
You called it correctly, this was the same class of issue as the May 19 incident: container creation stuck on a subset of us-west2 hosts, June 11-12. The 7+ attempts hanging at 19-23 minutes were all landing on affected hosts. No manual intervention ended up being needed, the fleet recovered and your deploy went through.
Sorry this ate your day. If anything regresses reply here.
Status changed to Awaiting User Response Railway • 24 days ago
17 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 • 17 days ago