New builds are temporarily paused

What to do

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

  Anything that failed between 2026-10-20 17:03 UTC and 2026-10-20 20:56 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 7

1. investigatingOct 20, 2026, 5:03 PM UTC

   We are aware of an issue affecting builds and have temporarily paused new builds for most workspaces while we investigate. Deploys triggered during this period will need to be triggered again once we resume builds. Services that are already deployed and running are not affected. We are actively investigating and will provide updates as we learn more.

   provider

2. identifiedOct 20, 2026, 5:18 PM UTC

   We have identified the issue affecting builds and are working on a fix. While we do, new builds are now paused for all workspaces. Deploys triggered during this period will need to be triggered again once we resume builds. Services that are already deployed and running are not affected. We will provide further updates as we make progress.

   provider

3. identifiedOct 20, 2026, 7:10 PM UTC

   We are continuing to work on the issue affecting builds. Builds remain paused for all workspaces while we do, and we will bring them back in stages once we're confident everything is working as expected. Deploys triggered during this period will need to be triggered again once builds resume. Services that are already deployed and running are not affected. We'll share another update as soon as builds begin to resume.

   provider

4. identifiedOct 20, 2026, 7:59 PM UTC

   We have applied a fix and are gradually resuming builds. Builds are now enabled for Enterprise workspaces, and we are working to resume builds for all other workspaces next. Deploys triggered while builds were paused will need to be triggered again once builds are back for your workspace. We'll share another update as we resume builds for more workspaces.

   provider

5. monitoringOct 20, 2026, 8:20 PM UTC

   Builds are now enabled for Pro workspaces, in addition to Enterprise. We are working to resume builds for all remaining workspaces next. Deploys triggered while builds were paused will need to be triggered again once builds are back for your workspace. We'll share another update as we resume builds for the remaining workspaces.

   provider

6. monitoringOct 20, 2026, 8:43 PM UTC

   Builds are now enabled for Hobby workspaces, in addition to Enterprise and Pro. We are working to resume builds for all remaining workspaces next. Deploys triggered while builds were paused will need to be triggered again once builds are back for your workspace. We'll share another update as we resume builds for the remaining workspaces.

   provider

7. resolvedOct 20, 2026, 8:56 PM UTC

   Builds have resumed for all workspaces and are completing normally. This incident is now resolved. If you triggered a deploy, pushed to GitHub, or restarted a service while builds were paused, please trigger it again. Those were not queued during the pause and will not start on their own. Cron jobs scheduled during the pause did not run, and will continue from their next scheduled time. We're sorry for the disruption

   provider

Corrections

None so far.

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