Deployments slow to start

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 45m it lasted.

  Anything that failed between 2026-08-28 23:30 UTC and 2026-08-29 02:15 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 6

1. investigatingAug 28, 2026, 11:59 PM UTC

   We are aware of an issue causing deployments to take longer than normal to initialize. Users may experience delays when starting new deployments. We have identified a potential cause and are actively working to restore normal behavior. We will provide updates as we learn more.

   provider

2. monitoringAug 29, 2026, 12:20 AM UTC

   We have identified the cause of the delay: a networking issue on a single host in our infrastructure caused a backlog of deployments to queue up. We have removed the affected host from rotation and are scaling additional capacity to work through the backlog. Deployments are beginning to progress again. We will continue to monitor and provide an update once things have fully returned to normal.

   provider

3. investigatingAug 29, 2026, 12:37 AM UTC

   We are continuing to investigate an issue with deployment initialization. While we identified and removed an affected host from rotation, some of our deployment workers are experiencing instability as they work through the backlog of queued deployments. We are actively working to stabilize the deployment system and clear the backlog. We will provide further updates as we make progress.

   provider

4. investigatingAug 29, 2026, 3:05 AM UTC

   We continue to work through a backlog of queued deployments. Our deployment workers have stabilized following configuration changes, and throughput is gradually returning to normal levels. Some deployments may still experience delays as the backlog clears. We are actively working to reduce the remaining queue. We will provide further updates as we make progress.

   provider

5. monitoringAug 29, 2026, 3:33 AM UTC

   Deployments are continuing to recover. We have stabilized our deployment pipeline and cleared most of the backlog of queued deployments. Throughput has returned to nominal levels and new deployments are progressing through the queue. Some delays may still be experienced as the remaining backlog fully clears. We are actively monitoring and will provide a further update shortly.

   provider

6. resolvedAug 29, 2026, 3:38 AM UTC

   Deployment delays have been resolved. Our deployment pipeline has stabilized. The backlog of queued deployments has been cleared, and throughput has fully returned to normal. 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.