Slow attached storage for some users in US West
The storage performance issue affecting some users in US West has been resolved. Latency has returned to baseline and storage operations are back to normal levels. We apologize for any inconvenience this caused. If you continue to experience issues, please contact support at https://station.railway.com.
The latest update from Railway.
State
Resolved
Started
28 d ago
2026-10-04 02:47 UTC
Lasted
3 h 36 min
until 2026-10-04 06:23 UTC
Worst impact
Partial outage
Timeline
5 updatesInvestigating
2 h 2 min 57%
Identified
1 h 18 min 36%
Monitoring
15 min 7%
Updates
Times in UTCAs posted by Railway
The storage performance issue affecting some users in US West has been resolved. Latency has returned to baseline and storage operations are back to normal levels. We apologize for any inconvenience this caused. If you continue to experience issues, please contact support at https://station.railway.com.
Storage performance in US West has returned to normal. Latency is back to baseline and write operations have resumed at expected levels. We are continuing to monitor to confirm stability. If you are still experiencing issues, please reach out to support at https://station.railway.com.
Storage performance in US West continues to improve. Latency is gradually decreasing as we work through the remaining remediation steps. We are actively monitoring and will provide another update once we have more to share.
We have identified the cause of the storage performance degradation affecting some users in US West and are actively working to resolve it. We will continue to provide updates as we make progress.
We are aware of an issue affecting attached storage performance for some users in US West. Users may experience slow services and databases, queries taking longer than expected, deploys that are slow to become healthy, or intermittent crash loops. We have identified the cause and are actively working to restore normal performance. 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.6× 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