Railway: Degraded performance for stateful services with volumes

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 1h 12m it lasted.
Anything that failed between 2026-05-04 15:38 UTC and 2026-05-04 16:50 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.

investigatingMay 4, 2026, 3:38 PM UTC
We are investigating degraded performance affecting stateful services (services with attached volumes). Affected services may experience elevated latency or slower disk I/O than expected. Stateless services and new deployments without volumes are not affected.
provider
monitoringMay 4, 2026, 4:14 PM UTC
We have implemented a fix and are monitoring the results. Performance is back to a healthy state.
provider
resolvedMay 4, 2026, 4:50 PM UTC
We have seen consistently healthy stateful service performance. This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Railway still down?

No, this incident was resolved 2026-05-04 16:50 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

1h 12m, from 2026-05-04 15:38 UTC to 2026-05-04 16:50 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.