# New builds are temporarily paused

- Provider: [Railway](https://down.guide/railway)
- Level: confirmed
- Impact: Major outage
- lasted 3h 52m
- started 2026-10-20 17:03 UTC
- US West (California, USA), US East (Virginia, USA), Southeast Asia (Singapore) +2
- apac, eu, us
- id: DWN-9a2546cf0b
- Official page: https://status.railway.com/incident/JUA1PC5H

## Updates from Railway
### 2026-10-20 17:03 UTC: investigating
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.

### 2026-10-20 17:18 UTC: identified
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.

### 2026-10-20 19:10 UTC: identified
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.

### 2026-10-20 19:59 UTC: identified
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.

### 2026-10-20 20:20 UTC: monitoring
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.

### 2026-10-20 20:43 UTC: monitoring
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.

### 2026-10-20 20:56 UTC: resolved
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

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).