Skip to main content
Railway

Builds failing intermittently in US East and EU West

Partial outage Lasted 8h 42m · started · Railway's page

Level
confirmed
Worst impact
Partial outage
Components
US East (Virginia, USA), EU West (Amsterdam, Netherlands)
Regions
eu, us

What to do

  • Check whether you use Railway US East (Virginia, USA), EU West (Amsterdam, Netherlands) in eu, 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 8h 42m it lasted.

    Anything that failed between 2026-10-28 08:30 UTC and 2026-10-28 17:12 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 and will provide updates as we talk to upstream providers to fix.

Category: Upstream dependency

Read the postmortem

Updates from Railway 3

  1. identified

    We are aware of an issue causing some builds to fail in EU West and US East. Users may experience build failures or builds not completing successfully. We have identified the cause and will provide updates as we talk to upstream providers to fix. Running services are not affected.

    provider

  2. resolved

    The latency issue has abated and things have improved. We are monitoring closely and will update if there's a recurrence.

    provider

  3. postmortem

    Build latency occurred due to issues with our upstream storage provider, we have been in touch and this is now 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-1a0f65eb57

Is Railway still down?

No, this incident was resolved 2026-10-28 17:12 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

8h 42m, from 2026-10-28 08:30 UTC to 2026-10-28 17:12 UTC, by the times Railway posted.

What was affected?

Railway named US East (Virginia, USA), EU West (Amsterdam, Netherlands) in eu, us.

What caused it?

Upstream dependency. Railway wrote: "We have identified the cause and will provide updates as we talk to upstream providers to fix." The postmortem: https://status.railway.com/incident/TX3M5SWF

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.