Deployments are failing for some users
Railway deployments failed for services with attached volumes in US East, US West, EU West, and Southeast Asia. Railway reported that the problem is resolved. The outage lasted 19 minutes.
State
Resolved
Started
Lasted
19 min
Worst impact
Partial outage
Timeline
4 updatesInvestigating
10 min 52%
Identified
6 min 32%
Monitoring
3 min 16%
Updates
Times in UTCAs posted by Railway
The issue affecting deployments has been resolved. Error rates have returned to baseline and deployments are completing successfully. Only deployments involving services with attached volumes were affected. Users without volumes were not impacted. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com/.
We have deployed a fix and error rates are recovering. We are monitoring to confirm full resolution. Only deployments involving services with attached volumes were affected. Users without volumes were not impacted.
We have identified the issue causing deployments to fail and are working on a fix. Some users may continue to experience deploys failing or stuck in a queued state while we complete the resolution. We will provide another update once the fix is deployed.
We are aware of an issue causing deployments to fail for some users. Affected users may see deploys stuck in a queued state or failing with errors. We are actively investigating and will provide updates as we learn more.
Affected components
4Railway in the last 90 days
Full historyIncidents in 90 days
59
Days with an incident
38
Median duration
1 h 20 min
This incident
77% shorter than the median
Other Railway incidents
All incidentsRailway·Builds failing in US West & US East
Builds failed in US West and US East for Railway. Railway switched to an alternate DNS resolver and builds recovered. The incident is resolved and lasted 34 minutes.
Railway·GitHub Outage Affecting Builds
Railway reported degraded Auto-Deploys for projects that use GitHub as a source, which caused build failures. Railway resolved this notice on 10 November 2026, after 44 hours and 30 minutes. Manual deployments and CLI deployments were not affected.
Railway·External network blocks affecting access to Railway
Railway reports that users cannot access Railway-hosted applications and railway.com. The Dashboard and the regions US East, US West, EU West, and Southeast Asia were affected. Railway says the incident is resolved and lasted about 5 days.
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.
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