25 days ago
All deployments have been failing at the CREATE_CONTAINER stage since June 11.
Builds complete successfully every time, but the container scheduler in us-west2
cannot start new containers. The service is stuck on the May 31 deployment.
Service ID: 4cc1f188-342f-49f9-a1af-79ac236f1209
Project ID: dc3e8bf5-30ee-4c2d-9419-5b83e4477088
Region: us-west2
Last successful deployment: May 31 (commit 3a69d873)
Failing since: June 11
Pattern:
-
Build succeeds (~18s)
-
Deploy > Create container times out after 9–10 minutes
-
Error: "Failed to create deployment"
-
No deploy logs produced (container never starts)
-
Happens on every attempt: code pushes, manual redeployments, railway up via CLI
-
Resource usage is normal (memory ~400MB, disk ~1GB)
-
Your own AI diagnostic confirmed this as a platform-side infrastructure issue
in us-west2's container scheduler
The running container has been live for 12+ days with no issues — this is not
a code problem. Please investigate the scheduler for this service.
1 Replies
Status changed to Awaiting Railway Response Railway • 25 days ago
24 days ago
Hey, your service is running now, I verified the current deployment directly.
You had it diagnosed right: this was on us, not your build. Container creation in us-west2 was failing on a subset of hosts June 11-12, worst of it was June 12 13:00-15:00 UTC. Your 9-10 minute timeouts with no deploy logs are the exact signature, the container never got created so there was nothing to log.
Resolved now. Your latest deploy went through clean.
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