a month ago
Deployments failing at "Deploy > Create container" with generic
"Failed to create deployment." — Infrastructure Error per your own diagnosis.
Service: organizasst (ID 0564fb45-183f-478e-8c99-7f318c93155c)
Project: 9652e271-d208-40df-b5b0-f8903e6d7c97, env production, region sfo
Timeline: last successful deploy ~16:40 GMT-4 today; since ~16:45, 6+
consecutive attempts fail instantly (00:00) at container creation.
Build always succeeds, image pushes fine (530 MB). No config changes
(your diagnosis confirmed "identical deployment succeeded 6 minutes
earlier"). Failed deployment IDs: 55e58860, 353b3d48, c77dfcc5, 283fa54c.
The running deployment stays Online. Please unblock container scheduling
for this service.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hi - apologies. We had an incident which caused this behavior. (https://status.railway.com/incident/V0KCMT8G) Everything should be back to normal now. Let us know if you see otherwise.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago