Builds failing in US West & US East
Builds fail in US West (California, USA) and US East (Virginia, USA). Railway reports that a Cloudflare DNS resolver was briefly unavailable. Railway switched to an alternate resolver and builds have recovered. Railway monitors for stability.
State
Monitoring
Started
Ongoing for
24 min
Worst impact
Partial outage
Timeline
2 updatesInvestigating
14 min 58%
Monitoring
10 min 42%
Updates
Times in UTCAs posted by Railway
Cloudflare’s DNS resolver was briefly unavailable, causing build failures in US East and US West. We have switched to an alternate resolver, and builds have recovered. We are monitoring for stability.
We are aware of an issue causing build failures in US West and US East. Users in these regions may experience build failures. We are actively investigating and will provide updates as we learn more.
Affected components
2Railway in the last 90 days
Full historyIncidents in 90 days
62
Days with an incident
40
Median duration
1 h 30 min
This incident
73% shorter than the median
Other Railway incidents
All incidentsRailway·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.
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.
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