Railway: We're experiencing an elevated error rate in our edge network

What to do

Check whether you use Railway Southeast Asia (Singapore), TCP Proxy (Metal), EU West (Amsterdam, Netherlands), US East (Virginia, USA) and 1 more in apac, 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 1h 11m it lasted.
Anything that failed between 2026-02-26 21:18 UTC and 2026-02-26 22:30 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.

investigatingFeb 26, 2026, 9:18 PM UTC
We are currently investigating this incident.
provider
identifiedFeb 26, 2026, 9:20 PM UTC
We are continuing to work on a fix for this incident.
provider
monitoringFeb 26, 2026, 9:21 PM UTC
We implemented a fix and are currently monitoring the result.
provider
resolvedFeb 26, 2026, 10:30 PM UTC
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-02-26 22:30 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

1h 11m, from 2026-02-26 21:18 UTC to 2026-02-26 22:30 UTC, by the times Railway posted.

What was affected?

Railway named Southeast Asia (Singapore), TCP Proxy (Metal), EU West (Amsterdam, Netherlands), US East (Virginia, USA) and 1 more in apac, eu, us.

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.