outages.live
Live
RailwayIncident ·

Deployments limited to Enterprise workspaces (record added Nov 5)

ResolvedOfficial update

Resolved. This entry was added on November 5, 2026 to correct the record.

The latest update from Railway.

State

Resolved

Started

Lasted

3 h 10 min

Worst impact

Partial outage

Timeline

2 updates
03:2004:0704:5505:4206:30
Partial outageUpdate postedTimes in UTC

Identified

3 h 10 min 100%

Updates

Times in UTC

As posted by Railway

Resolved

Resolved. This entry was added on November 5, 2026 to correct the record.

Identified

Only Enterprise workspaces could deploy; the Redeploy feature was unavailable until 04:52 UTC and the pre-deploy stage stalled from 04:39 to 06:12 UTC. 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

1
Deployments

Railway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

63

Days with an incident

37

Median duration

1 h 25 min

This incident

2.2× the median

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

7 days
median 1 h 25 min
90 days agoToday

Other Railway incidents

All incidents

Railway·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.

Partial outage

Railway·US East build failures (record added Nov 5)

Resolved. This entry was added on November 5, 2026 to correct the record.

Resolved

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.

Resolved

Railway·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.

Resolved

Railway·Deployments paused (record added Nov 5)

Resolved. This entry was added on November 5, 2026 to correct the record.

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.

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