Deployments are slow

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

  Anything that failed between 2026-08-20 14:50 UTC and 2026-08-20 17:45 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 20, 2026, 3:27 PM UTC

   We are aware of an issue causing deployments to queue and take longer than usual to progress. Users may experience delays in deployments starting or completing. We are actively investigating the root cause and will provide updates as we learn more.

   provider

2. identifiedAug 20, 2026, 3:56 PM UTC

   We have identified that a Google Cloud infrastructure issue is contributing to deployment delays. Our backend services experienced elevated internal errors from Google Cloud beginning around 14:53 UTC, which caused our deployment processing pipeline to become congested. We are actively working to mitigate the impact and restore normal deployment throughput. We will provide further updates as the situation develops.

   provider

3. identifiedAug 20, 2026, 4:15 PM UTC

   We have identified that a Google Cloud infrastructure issue is contributing to deployment delays. Our backend services experienced elevated internal errors from Google Cloud beginning around 14:53 UTC, which caused our deployment processing pipeline to become congested. We are actively working to mitigate the impact and restore normal deployment throughput. As we do this deployments will be temporarily paused at times and slower. We will provide further updates as the situation develops.

   provider

4. identifiedAug 20, 2026, 5:29 PM UTC

   We have identified that a Google Cloud infrastructure issue is contributing to deployment delays. Our backend services experienced elevated internal errors from Google Cloud beginning around 14:53 UTC, which caused our deployment processing pipeline to become congested. We have made adjustments and it is starting to improve but still delayed. We will provide further updates as the situation develops.

   provider

5. monitoringAug 20, 2026, 5:31 PM UTC

   The deployment pause has been lifted and the backlog of queued deployments is clearing. New deployments are being accepted and processing again, though some delays may persist as the queue continues to drain. We are continuing to monitor the situation and will provide further updates.

   provider

6. resolvedAug 20, 2026, 6:20 PM UTC

   Deployments are operating normally. The backlog of queued deployments has cleared and deployment times have returned to expected levels. The root cause was a Google Cloud infrastructure issue beginning around 14:53 UTC that caused elevated errors in our backend services, leading to congestion in our deployment processing pipeline. We temporarily paused new deployments to prevent further backlog buildup while we worked to restore normal operations. The Google Cloud issue has since resolved and our systems have recovered. We apologize for the disruption. 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.