Skip to main content
Railway

Elevated error rates on Edge Network

Degraded Lasted 15m · started · Railway's page

Level
confirmed
Worst impact
Degraded
Components
Southeast Asia (Singapore), TCP Proxy (Metal), EU West (Amsterdam, Netherlands), US East (Virginia, USA), US West (California, USA)
Regions
apac, eu, us
Down Index
26of 100

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 15m it lasted.

    Anything that failed between 2026-03-01 20:43 UTC and 2026-03-01 20:59 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

    We are aware of elevated 503 error rates across all regions. Users may experience intermittent failures when accessing their services. We are actively investigating and will provide updates as we learn more.

    provider

  2. monitoring

    We have implemented a fix and are monitoring the results. Error rates are trending down across all regions. Some users may still experience intermittent 503 errors as the fix propagates. We will provide a further update once we confirm full recovery.

    provider

  3. resolved

    The elevated 503 error rates across all regions have been resolved. All traffic is now flowing normally through the edge network. We apologize for any disruption. If you continue to experience issues, please contact support at .

    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-53e876783d

Is Railway still down?

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

How long did it last?

15m, from 2026-03-01 20:43 UTC to 2026-03-01 20:59 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.