Live

Deployments are failing for some users

0

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 updates
20:0220:0720:1220:1620:21
Partial outageUpdate postedTimes in UTC

Investigating

10 min 52%

Identified

6 min 32%

Monitoring

3 min 16%

Updates

Times in UTC

As posted by Railway

Resolved

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/.

Monitoring

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.

Identified

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.

Investigating

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

4
US East (Virginia, USA)US West (California, USA)EU West (Amsterdam, Netherlands)Southeast Asia (Singapore)

Railway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

59

Days with an incident

38

Median duration

1 h 20 min

This incident

77% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days
median 1 h 20 min
90 days agoToday

Other Railway incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=railway
Slack
/feed subscribe https://outages.live/feed.xml?providers=railway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane