Skip to main content
Railway

Increased latency on the EU-West Edge.

Degraded Lasted 2h 42m · started · Railway's page

Level
confirmed
Worst impact
Degraded
Components
EU West (Amsterdam, Netherlands)
Regions
eu

What to do

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

    Anything that failed between 2026-03-26 20:46 UTC and 2026-03-26 23:27 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.

Updates from Railway 3

  1. investigating

    Some users in or around Europe may be experiencing increased latency when accessing their workloads.

    provider

  2. monitoring

    We have made some configuration changes and are seeing improvements.

    provider

  3. resolved

    We have witnessed full recovery, and response times are back to their nominal values.

    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-4a3f2ab4a6

Is Railway still down?

No, this incident was resolved 2026-03-26 23:27 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

2h 42m, from 2026-03-26 20:46 UTC to 2026-03-26 23:27 UTC, by the times Railway posted.

What was affected?

Railway named EU West (Amsterdam, Netherlands) in eu.

What caused it?

Railway hasn't published a root cause. If it does, it shows here.

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.