Deploy fails at 'Create Container' with zero logs (sfo region) - Diagnose tool reports Infrastructure Error
andersonglobalenterprises
HOBBYOP

a month ago

Service: age-interview-prep (b2687c42-868f-46e5-b382-1c7e8919e703), project afd2885c-8030-47df-8595-2cd8c1bb3e4a, environment production, region sfo. 4 consecutive railway up deploys today (2026-07-08, ~21:02-21:35 UTC) all failed. Build stage succeeds every time (image compiles and pushes fine, all expected routes present). Deploy fails at Deploy > Create Container in 0 seconds every time, with zero output from Build Logs, Deploy Logs, and HTTP Logs streams. The currently active deployment (from 2026-07-05) stayed healthy and served traffic throughout. The built-in Diagnose tool returned: Infrastructure Error - Three consecutive deployments on July 8th all failed at the container creation stage after successful builds. This appears to be a platform-side issue with container scheduling in the US West (sfo) region. I also reproduced the exact build and start commands locally and the app boots and serves correctly in under 1 second, so this is not an application code issue. Could you look into container scheduling capacity/health in sfo for this service, or let me know if I should switch regions? This is a live paying-customer app.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


sam-a
EMPLOYEE

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


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...