Railway: Deployment Degredation

What to do

Check whether you use Railway EU West (Amsterdam, Netherlands), US East (Virginia, USA), Southeast Asia (Singapore), US West (California, USA) 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 30m it lasted.
Anything that failed between 2026-01-04 21:15 UTC and 2026-01-04 21:45 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.

investigatingJan 4, 2026, 9:15 PM UTC
We are currently investigating this incident.
provider
identifiedJan 4, 2026, 9:25 PM UTC
We've disabled deployments for Trial, Free, and Hobby plans.
provider
monitoringJan 4, 2026, 9:38 PM UTC
We've reenabled deployments on all plans.
provider
resolvedJan 4, 2026, 9:45 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-01-04 21:45 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

30m, from 2026-01-04 21:15 UTC to 2026-01-04 21:45 UTC, by the times Railway posted.

What was affected?

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