US East build failures after the queue was released (record added Nov 5)
Resolved. This entry was added on November 5, 2026 to correct the record.
The latest update from Railway.
State
Resolved
Started
Lasted
1 h 15 min
Worst impact
Partial outage
Timeline
2 updatesIdentified
1 h 15 min 100%
Updates
Times in UTCAs posted by Railway
Resolved. This entry was added on November 5, 2026 to correct the record.
Build failures in US East reached 39% after the deployment queue was released. Record added on November 5, 2026 from the incident review that followed the October 21 security incident. This entry corrects the uptime record; no notification was sent for it.
Affected components
1Railway in the last 90 days
Full historyIncidents in 90 days
63
Days with an incident
37
Median duration
1 h 25 min
This incident
About the median
Other Railway incidents
All incidentsRailway·External network blocks affecting access to Railway
Railway reports that railway.com and Railway-hosted applications do not work for some users. Network providers and security services block Railway IP addresses. Railway identified the problem and continues work with network operators to remove the blocks. Railway gives no estimated time for full recovery.
Railway·US East build failures (record added Nov 5)
Resolved. This entry was added on November 5, 2026 to correct the record.
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 paused (record added Nov 5)
Resolved. This entry was added on November 5, 2026 to correct the record.
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.
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.live/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.live/feed.xml?providers=railway/feed subscribe https://outages.live/feed.xml?providers=railwayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane