Builds are taking longer than usual
The issue affecting build times in US West has been resolved. Build times have returned to normal and the queue has cleared. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
The latest update from Railway.
State
Resolved
Started
19 d ago
2026-10-13 16:12 UTC
Lasted
48 min
until 2026-10-13 17:00 UTC
Worst impact
Degraded
Timeline
5 updatesInvestigating
23 min 49%
Identified
10 min 21%
Monitoring
14 min 30%
Updates
Times in UTCAs posted by Railway
The issue affecting build times in US West has been resolved. Build times have returned to normal and the queue has cleared. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Build times in US West are returning to normal. We are monitoring the situation and will mark this incident as resolved once we have confirmed sustained recovery. Users in other regions are not affected. We will provide a further update shortly.
We have identified the root cause of the build slowness in US West and are rolling out a fix. Build times are beginning to improve as the fix is deployed. Users in US West may still experience builds taking longer than usual while the fix propagates. Users in other regions are not affected. We will provide a further update once the fix is fully in place.
We have identified an issue affecting build infrastructure in US West and are investigating a potential cause. Our team is working on a fix and scaling capacity in the region. Users in US West may experience builds taking significantly longer to complete. Users in other regions are not affected. We will provide updates as we learn more.
We are aware of an issue causing builds to take longer than usual. Users may experience extended build times. We are actively investigating and will provide updates as we learn more.
Affected components
1Railway in the last 90 days
Full historyIncidents in 90 days
38
Days with an incident
33
Median duration
1 h 23 min
This incident
42% shorter than the median
Other Railway incidents
All incidentsRailway·Degraded performance
Railway had degraded performance on the Railway platform. Railway reports that the incident is resolved. The incident lasted 8 hours.
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.
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.
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.
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.
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.
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.
https://outages.cc/feed.xml?providers=railway/feed subscribe https://outages.cc/feed.xml?providers=railwayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane