Deployments slow to start
Deployment delays have been resolved. Our deployment pipeline has stabilized. The backlog of queued deployments has been cleared, and throughput has fully returned to normal. 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
64 d ago
2026-08-28 23:59 UTC
Lasted
3 h 40 min
until 2026-08-29 03:38 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
3 h 16 min 89%
Monitoring
24 min 11%
Updates
Times in UTCAs posted by Railway
Deployment delays have been resolved. Our deployment pipeline has stabilized. The backlog of queued deployments has been cleared, and throughput has fully returned to normal. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Deployments are continuing to recover. We have stabilized our deployment pipeline and cleared most of the backlog of queued deployments. Throughput has returned to nominal levels and new deployments are progressing through the queue. Some delays may still be experienced as the remaining backlog fully clears. We are actively monitoring and will provide a further update shortly.
We continue to work through a backlog of queued deployments. Our deployment workers have stabilized following configuration changes, and throughput is gradually returning to normal levels. Some deployments may still experience delays as the backlog clears. We are actively working to reduce the remaining queue. We will provide further updates as we make progress.
We are continuing to investigate an issue with deployment initialization. While we identified and removed an affected host from rotation, some of our deployment workers are experiencing instability as they work through the backlog of queued deployments. We are actively working to stabilize the deployment system and clear the backlog. We will provide further updates as we make progress.
We have identified the cause of the delay: a networking issue on a single host in our infrastructure caused a backlog of deployments to queue up. We have removed the affected host from rotation and are scaling additional capacity to work through the backlog. Deployments are beginning to progress again. We will continue to monitor and provide an update once things have fully returned to normal.
We are aware of an issue causing deployments to take longer than normal to initialize. Users may experience delays when starting new deployments. We have identified a potential cause and are actively working to restore normal behavior. We 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
2.7× 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