outages.live
Live
RailwayIncident · 2026-10-20 17:03 UTC

New builds are temporarily paused

ResolvedOfficial update

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

The latest update from Railway.

State

Resolved

Started

12 d ago

2026-10-20 17:03 UTC

Lasted

3 h 52 min

until 2026-10-20 20:56 UTC

Worst impact

Major outage

Timeline

7 updates
17:0318:0118:5919:5720:56
Major outageUpdate postedTimes in UTC

Investigating

15 min 7%

Identified

3 h 1 min 78%

Monitoring

36 min 15%

Updates

Times in UTC

As posted by Railway

Resolved2026-10-20 20:56 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

Monitoring2026-10-20 20:43 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.

Monitoring2026-10-20 20:20 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.

Identified2026-10-20 19:59 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.

Identified2026-10-20 19:10 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.

Identified2026-10-20 17:18 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.

Investigating2026-10-20 17:03 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.

Affected components

1
Builds

Railway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

38

Days with an incident

33

Median duration

1 h 23 min

This incident

2.8× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 1 h 23 min
90 days agoToday

Other Railway incidents

All incidents

Railway·Degraded performance

Railway had degraded performance on the Railway platform. Railway reports that the incident is resolved. The incident lasted 8 hours.

Resolvedresolved 2 h ago

Railway·Elevated Build Failure Rate

The elevated build failure rate has been resolved. Builds are processing normally across all regions. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.

Resolvedresolved 11 h ago

Railway·Deployments stuck in initializing

Builds and deployments are back to normal. An issue in the system that processes builds caused delays, so we briefly paused new deployments to clear the backlog. Everything queued has now been processed. If a deployment failed during this time, please trigger a redeploy. Still seeing issues? Reach us at https://station.railway.com. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.

Resolvedresolved 4 d ago

Railway·Builds failing intermittently in US East and EU West

Build latency occurred due to issues with our upstream storage provider, we have been in touch and this is now resolved.

Resolvedresolved 4 d ago

Railway·Builds failing in US West

The issue causing builds to fail in US West has been resolved. Builds are now completing normally. If a build failed during this incident, redeploying it should now succeed. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Resolvedresolved 4 d ago

Follow Railway

Your coding agent knows when Railway is down, and tells you when a failure is theirs, not yours. You can also get Railway incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "railway" and tell me if Railway has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=railway
Slack
/feed subscribe https://outages.cc/feed.xml?providers=railway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane