- Level
- confirmed
- Worst impact
- Partial outage
- Components
- US West (California, USA), US East (Virginia, USA)
- Regions
- us
- Down Index
- 30of 100
What to do
Check whether you use Railway US West (California, USA), US East (Virginia, USA) in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 30m it lasted.
Anything that failed between 2026-10-31 19:37 UTC and 2026-10-31 20:07 UTC may need a replay.Subscribe to Railway's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=railway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
We have identified the cause of the elevated build failure rate.Read the postmortem
Updates from Railway 4
- investigating
We are aware of an issue causing elevated build failure rates across our regions. Users may experience builds failing unexpectedly. We are actively investigating and will provide updates as we learn more. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.
provider
- identified
We have identified the cause of the elevated build failure rate. An upstream storage provider that our build infrastructure depends on is experiencing elevated request timeouts, which is preventing some builds from starting. This affects builds in all regions. We are working with the provider to restore normal service. Builds that failed can be retried; retries may succeed but may also fail until the issue is resolved. We will provide another update as we learn more.
provider
- monitoring
The upstream storage provider has applied a fix, and build failure rates are back to normal as of 20:10 UTC. Builds that failed during this incident can be retried. We are monitoring to confirm full recovery.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-eb4e0564fd
Is Railway still down?
No, this incident was resolved 2026-10-31 20:07 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
30m, from 2026-10-31 19:37 UTC to 2026-10-31 20:07 UTC, by the times Railway posted.
What was affected?
Railway named US West (California, USA), US East (Virginia, USA) in us.
What caused it?
Railway wrote: "We have identified the cause of the elevated build failure rate." The postmortem: https://status.railway.com/incident/II4FTFR6
Where does this come from?
Railway's official status page, https://status.railway.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.