Deployments are slow to progress

What to do

• Check whether you use Railway Southeast Asia (Singapore), US West (California, USA), EU West (Amsterdam, Netherlands), US East (Virginia, USA) 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 17m it lasted.

  Anything that failed between 2026-07-22 21:10 UTC and 2026-07-22 21:28 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.

Updates from Railway 3

1. investigatingJul 22, 2026, 9:10 PM UTC

   We are aware of an issue causing deployments to take longer than expected to progress. Users may experience deployments remaining in a pending state. We are actively investigating and will provide updates as we learn more.

   provider

2. identifiedJul 22, 2026, 9:17 PM UTC

   We have identified the root cause and deployed a fix. Deployments are recovering and the queue is clearing. We will provide further updates as the situation improves.

   provider

3. resolvedJul 22, 2026, 9:28 PM UTC

   The issue affecting deployment progression has been resolved. Deployments are completing normally and the queue has fully cleared. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com/.

   provider

Corrections

None so far.

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