Resolved after 3 hours 52 minutes, affecting US East (Virginia, USA) (Builds (US East)) and US West (California, USA) (Builds (US West)) and 1 more, on October 20, 2026.
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
Affected components
Update timeline
- investigating Oct 20, 2026, 05: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.
- identified Oct 20, 2026, 05: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.
- identified Oct 20, 2026, 07: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.
- identified Oct 20, 2026, 07: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.
- monitoring Oct 20, 2026, 08: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.
- monitoring Oct 20, 2026, 08: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.
- resolved Oct 20, 2026, 08: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
Your product runs on more than Railway
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.