Deployments stuck in initializing

What to do

• Check whether you use Railway US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands), Southeast Asia (Singapore) in apac, eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 12m it lasted.

  Anything that failed between 2026-10-28 17:05 UTC and 2026-10-28 19:17 UTC may need a replay.

• Subscribe to Railway's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=railway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

We have identified the cause of an issue that causes deployments to become stuck in an initializing state.

Updates from Railway 2

1. identifiedOct 28, 2026, 5:49 PM UTC

   We have identified the cause of an issue that causes deployments to become stuck in an initializing state. Users attempting to deploy may experience delays with builds and deployments not progressing. We are actively fixing and will provide updates.

   provider

2. resolvedOct 28, 2026, 7:17 PM UTC

   Builds and deployments are back to normal. An issue in the system that processes builds caused delays, so we briefly paused new deployments to clear the backlog. Everything queued has now been processed. If a deployment failed during this time, please trigger a redeploy. Still seeing issues? Reach us at https://station.railway.com. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.