Railway: Deployments paused (record added Nov 5)

What to do

Check whether you use Railway US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands), Southeast Asia (Singapore) 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 20m it lasted.
Anything that failed between 2026-10-28 18:20 UTC and 2026-10-28 18:40 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.

identifiedOct 28, 2026, 6:20 PM UTC
Deployments and builds were paused deliberately for twenty minutes inside the October 28 incident. Record added on November 5, 2026 from the incident review that followed the October 21 security incident. This entry corrects the uptime record; no notification was sent for it.
provider
resolvedOct 28, 2026, 6:40 PM UTC
Resolved. This entry was added on November 5, 2026 to correct the record.
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-10-28 18:40 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

20m, from 2026-10-28 18:20 UTC to 2026-10-28 18:40 UTC, by the times Railway posted.

What was affected?

Railway named US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands), Southeast Asia (Singapore) 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.