Apologies for the trouble. We're aware of the "Deployments slow to start" incident affecting deployments across all regions (US East, US West, EU West, Southeast Asia) and are actively working on it. There is no workaround to force a queued deploy through while the backlog clears, and since all four regions are affected, a region change would not help for this particular event. You can follow live updates at the incident page.

The incident info is clear, thanks — what I still need help with is the recurring pattern, not this event. This is my second deploy-blocking incident in ~two weeks while running client-facing production services. Two questions for the team: (1) Are there any account- or config-level options for deploy reliability — priority build queues, paid tiers with SLA, anything that reduces exposure to build-infrastructure incidents? (2) Is deploy-queue reliability something with a public roadmap or postmortems I can follow? Trying to make an informed decision about consolidating more production workloads here, and repeat build outages are the one thing giving me pause.

This isn't just a deployment issue. My site is down, will not load.

Have the same issue, 21 hours since the last build, hitting the deployment slow start, 6 attempts over the last 6 hours (while status shows issue is fixed). I am still not able to successfully run a deployment. Not even redeploy the one that was running successfully from yesterday.

This is fixed for me. https://station.railway.com/questions/every-deploy-fails-healthcheck-confirm-4adb21e6 Refer this thread if it helps.