25 days ago
I have been trying to deploy my webapp since yesterday, it keeps failing at the "creating container" stage. When I click diagnose, it says:
This deployment failed at the container creation stage due to a platform-side issue. The build completed successfully every time, and the commit only adds a documentation file with no code or config changes. This same failure has occurred six consecutive times for this commit, pointing to a persistent infrastructure problem.
5 deployments have failed. There are no logs since container fails. The embedded AI chat mentioned:
You need to contact Railway support. Provide them with:
Service: cliniquiz_html
Deployment IDs:
0d1e9979-8371-4e1c-97ed-d9657eece7ec (1st failure)
6eae22dc (2nd failure)
a80e3e66-3aef-4ef1-b95e-9cd8b1c339b8 (3rd failure)
Commit: aa8a161 (only adds a docs file)
Issue: Container creation failing consistently while builds succeed
This is beyond a simple retry—the Railway team needs to investigate the container scheduling failure on their infrastructure.
Please help!
5 Replies
25 days ago
We're aware of transient container creation issues and are actively working on improvements. Please cancel any queued deployments for now, as additional retries can compound the queue, and try again shortly.
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
I haven't been able to deploy an API because of this failure for almost 24 hours!
25 days ago
Yes, i also think status page should reflect current situation. I see its green but we are not able to deploy for 7 hours. Also openai requests fails completely.
24 days ago
Hey all, Angelo from Railway.
There were two back-to-back infra issues, which is why the timelines in this thread don't all match: an image registry performance problem starting the evening of June 11 (UTC), and a networking issue on a subset of US West / US East hosts on June 12, worst between 13:00-15:00 UTC. Both broke container creation after successful builds. Both are resolved.
You're also right that the status page didn't reflect the June 12 issue while it was happening. That's a miss on our side and I've flagged it internally.
Everyone here: trigger one fresh deploy (cancel anything stuck first). If yours still fails at creating container, reply with the deployment ID and I'll trace it individually.
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