API degradation causing slow or stuck deployments

What to do

• Check whether you use Railway API - backboard.railway.com, Dashboard - railway.com. 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 4h 35m it lasted.

  Anything that failed between 2026-09-29 14:40 UTC and 2026-09-29 19:15 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. investigatingSep 29, 2026, 3:29 PM UTC

   We are aware of an issue affecting our API that is causing slow or stuck deployments for some users. We are actively investigating and working to restore normal operations. We will provide updates as we learn more.

   provider

2. monitoringSep 29, 2026, 6:37 PM UTC

   We are seeing recovery and are monitoring this incident. Hobby deployments have been re-enabled.

   provider

3. resolvedSep 29, 2026, 7:15 PM UTC

   The issue affecting our API and causing slow or stuck deployments has been resolved. A period of elevated load on our API caused a backlog to build in our deployment queue faster than it could drain. We applied several fixes to improve how our deployment system handles backpressure and temporarily paused new deployments for Hobby-tier projects while the queue recovered. All deployments have since resumed and are processing normally. We apologize for any inconvenience. 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.