Services and databases unavailable for some users in US West

What to do

• Check whether you use Railway US West (California, USA) in 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 12h 15m it lasted.

  Anything that failed between 2026-10-03 11:45 UTC and 2026-10-04 00:00 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. identifiedOct 3, 2026, 11:43 AM UTC

   We have identified an issue causing some hosts in US West to become unresponsive. Services and databases running on those hosts may be unreachable or fail to connect, and redeploys of affected services may stall. We are restarting the affected hosts, and services will come back automatically as each host recovers. Users with affected services will receive an email and an in-app notification. We will provide updates as we learn more.

   provider

2. monitoringOct 3, 2026, 5:21 PM UTC

   All affected hosts in US West have been restarted, and services running on them are recovering. Users with affected services have been notified by email and in-app. If one of your services is still unavailable, redeploy it once from your dashboard. If that doesn't resolve it, please reach out at station.railway.com.

   provider

3. resolvedOct 3, 2026, 7:33 PM UTC

   The issue affecting services and databases in US West has been resolved. We apologize for any disruption. If you continue to experience issues, please contact support at https://station.railway.com.

   provider

Corrections

None so far.

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